Commit Graph

8 Commits

Author SHA1 Message Date
Czarek Nakamoto
fdd5c6848b sync changes to wownero. Wow. 2024-04-22 15:33:09 +02:00
Czarek Nakamoto
7e49b4ad69 add missing functionality from for cake's polyseed implementation 2024-04-22 12:49:17 +02:00
Czarek Nakamoto
b003970d7f Revert "add polyseed language options"
This reverts commit a032a20221.
2024-04-11 17:15:42 +02:00
Czarek Nakamoto
a032a20221 add polyseed language options 2024-04-11 08:53:29 +02:00
Czarek Nakamoto
95728838ee add comments explaining what does the code do? 2024-04-05 16:51:15 +02:00
Czarek Nakamoto
f6ca8ee9fb un-conflict exported symbols on macos 2024-04-01 14:00:33 +02:00
Czarek Nakamoto
f2057a2363 fix: wownero and monero wallets in the same process
ci: cache ~/.ccache directory
2024-04-01 06:54:50 +02:00
Czarek Nakamoto
b72d2dff62 feat: split MONERO and WOWNERO prefixed functions
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.
2024-03-31 09:19:47 +02:00