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

Reassess 0conf aspects #8

Open
BitcoinErrorLog opened this issue Nov 11, 2022 · 0 comments
Open

Reassess 0conf aspects #8

BitcoinErrorLog opened this issue Nov 11, 2022 · 0 comments

Comments

@BitcoinErrorLog
Copy link
Collaborator

In light of Core adding a new fullRBF mempool feature, we may need to reassess specs, UX, and best practices arounf 0conf acceptance.

The worst (and most likely) case is that 0conf will become outright unmanageable for merchants this Winter. There are some ideas about ways to accept 0conf RBF txns, but more discussion is needed, and it gets ... complicated.
@BitcoinErrorLog BitcoinErrorLog changed the title Reasses 0conf aspects Reassess 0conf aspects Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BitcoinErrorLog