Skip to content
This repository has been archived by the owner on Jan 12, 2022. It is now read-only.

chain transactions to avoid mempool conflicts #232

Closed
dashameter opened this issue Feb 14, 2021 · 4 comments
Closed

chain transactions to avoid mempool conflicts #232

dashameter opened this issue Feb 14, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@dashameter
Copy link
Contributor

If the wallet has its entire balance in 1 utxo, then e.g. identity creation will block any other L1 interactions with mempool conflict.

wallet-lib should keep track of that spent utxo that is now in mempool and chain future L1 transactions.

https://discord.com/channels/670271785974890526/670540408593448980/809996041411625020

https://discord.com/channels/670271785974890526/670540408593448980/810207088286367764

@dashameter dashameter added the enhancement New feature or request label Feb 14, 2021
@Alex-Werner
Copy link
Contributor

cc:@dalibran This will be an issue to Developer Experience as they might not understand reason of it failing. I would suggest us to have this on our backlog and assign it a decent priority (I really think we should have this working for mainnet).

@dash-maverick
Copy link

Just as an update - this is being progressed on DCG side and is supposed to be completed soon. The fix should also solve problems described in

@dash-maverick
Copy link

@dashameter @SamKirby22 should be solved from now - please double check

@dashameter
Copy link
Contributor Author

passed retest

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Development

No branches or pull requests

3 participants