summaryrefslogtreecommitdiff
path: root/wownero_libwallet2_api_c
AgeCommit message (Collapse)Author
2024-04-11Revert "add polyseed language options"Czarek Nakamoto
This reverts commit a032a20221579d5fb9445b370eec1b6bd4ff653b.
2024-04-11add polyseed language optionsv0.18.3.3-RC22Czarek Nakamoto
2024-04-05add comments explaining what does the code do?Czarek Nakamoto
2024-04-01un-conflict exported symbols on macosCzarek Nakamoto
2024-04-01fix: wownero and monero wallets in the same processv0.18.3.3-RC12Czarek Nakamoto
ci: cache ~/.ccache directory
2024-03-31feat: split MONERO and WOWNERO prefixed functionsv0.18.3.3-RC11Czarek Nakamoto
So basically: when we open the .so file, we define some symbols, and it appears that if we load something else, with the same symbols, under the same thread we cause some funky behaviour - like calling function a wownero function MONERO_Wallet_address() resulting in a monero address being generated. Needless to say, this is undesired, and a blocker for https://github.com/cypherstack/stack_wallet/pull/818 I'm afraid that this may not solve all of our issues (but will solve some significant roadblocks), because of the "genesis block" issue, as output of nm -gDC release/wownero/x86_64-linux-gnu_libwallet2_api_c.so | grep genesis indicate that these functions may share *something* in common across both WOW and XMR libraries. In a case in which this fix won't be sufficient, I think that the way forward would be to close the dynamic libraries, but before we do that I want to check if maybe there is a change to run multiple wallets at once.