Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Payment error: txn-mempool-conflict (Quick Mode) #264

Open
sondreb opened this issue Oct 17, 2022 · 6 comments
Open

Payment error: txn-mempool-conflict (Quick Mode) #264

sondreb opened this issue Oct 17, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@sondreb
Copy link
Member

sondreb commented Oct 17, 2022

In the wallet quick mode, sending two transactions in a row quickly can result in txn-mempool-conflict:

image
@sondreb sondreb added the bug Something isn't working label Oct 17, 2022
@dangershony
Copy link
Member

This was fixed, is it still occuring?
What indexer version did you use?

@sondreb
Copy link
Member Author

sondreb commented Oct 18, 2022

Not 100% sure, but I think it was blockcore and that runs latest version. It might have been one of the other 3 that is available though...

@sondreb
Copy link
Member Author

sondreb commented Oct 18, 2022

Is this the change? This is not released yet: block-core/blockcore-indexer@26e504b

@dangershony
Copy link
Member

Yes so right we need to release

@sondreb
Copy link
Member Author

sondreb commented Mar 21, 2023

This is still an issue, the client appears to receive utxos from indexer that is in mem-pool and attempting to use that for a new tx.

@dangershony
Copy link
Member

dangershony commented Apr 14, 2023 •
edited
Loading

This is still an issue, the client appears to receive utxos from indexer that is in mem-pool and attempting to use that for a new tx.

Ah so its an indexer issue?
Is that an issue though? or you mean utxos from indexer that is in mem-pool utxo that is spent in the mempool?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sondreb @dangershony