Sometimes (fairly frequently, but not in most cases), used Elysium-layer lelantus mints are not marked as used. This may or may not be related to transactions being rejected from the mempool due to reusing base layer Lelantus inputs (see #1140). You can see the used Lelantus inputs in elysium_listlelantusmints, where they should not be.
Hints:
This may cause mints to be put into transactions twice, though I have not seen conflict reports in the debug.log. (Search for the string duplicates a serial from transaction in the debug.log, or an Elysium transaction rejected with error -85918.) This error would only happen after both transactions are mined however, which might not be happening if the base layer transactions are unconfirmed.
When this happens, firo-client may show negative balances. This is due to it subtracting the joinmintAmount of unconfirmed transactions from the (private) balance for a token.
Work on this and other Elysium issues is currently being done in the client-api-elysium branch. Relevant commits should later be cherry-picked and merged to the elysium-lelantus branch after work is done. I recommend testing with the functionality in firo-client's elysium branch, as it greatly simplifies the usage of Elysium functionality and is what will ultimately be what users interact with.
Sometimes (fairly frequently, but not in most cases), used Elysium-layer lelantus mints are not marked as used. This may or may not be related to transactions being rejected from the mempool due to reusing base layer Lelantus inputs (see #1140). You can see the used Lelantus inputs in
elysium_listlelantusmints, where they should not be.Hints:
duplicates a serial from transactionin the debug.log, or an Elysium transaction rejected with error-85918.) This error would only happen after both transactions are mined however, which might not be happening if the base layer transactions are unconfirmed.joinmintAmountof unconfirmed transactions from the (private) balance for a token.Work on this and other Elysium issues is currently being done in the
client-api-elysiumbranch. Relevant commits should later be cherry-picked and merged to theelysium-lelantusbranch after work is done. I recommend testing with the functionality in firo-client'selysiumbranch, as it greatly simplifies the usage of Elysium functionality and is what will ultimately be what users interact with.