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

Already on GitHub? Sign in to your account

Content request: zero-conf transactions #1216

Open
kanzure opened this Issue Jan 21, 2016 · 3 comments

Comments

Projects
None yet
4 participants
Contributor

kanzure commented Jan 21, 2016 edited by wbnns

Bounty: 20,000 bits / ~$75 USD

There is a brief section here that mentions zero-confirmation transactions, but it may not sufficiently cover the topic: https://bitcoin.org/en/developer-guide#verifying-payment and https://bitcoin.org/en/you-need-to-know#instant

I would expect the content to cover topics like: mempools and their relevance to zero-conf transactions, how there is no mempool consensus, chain-committed double spends versus zero-conf double spending, "stuck transactions", risks associated with zero-conf transactions, benefits from CLTV and CSV that can constrain the permissible behavior of some subset of zero-conf transactions, impossibility of instantaneous consensus, ...

... I am sure that I am missing a bunch of topics in this list.

@harding harding added the Dev Docs label Jan 21, 2016

Contributor

harding commented Jan 21, 2016

I like this idea, but I want to explain why it's not here now and why it probably won't be part of the documentation for a while: the Bitcoin.org developer documentation was originally written for application developers. We've been pretty successful there---I've seen application code that has comments that link to our descriptions of various things.

On the other hand, a lot of the people reviewing the documentation have been Core developers and they've quite reasonably requested more things like this that go into theory so that people can understand the fundamental limitations that influence various design decisions. I love writing that stuff, but I increasingly feel like the existing Bitcoin.org developer documentation doesn't provide the right framework to hold that documentation. I have a better framework in mind, but I haven't had time to start populating it with content (and if I did, it'll take at least 3 months before I had something usable).

Contributor

luke-jr commented Jan 22, 2016

Note that unconfirmed transactions are unconfirmed, not "zero-conf[irmed]". That being said, I agree it would be nice to have more information on off-chain transactions (including both unconfirmed and Lightning instant-confirmed).

@wbnns wbnns self-assigned this Dec 9, 2016

@wbnns wbnns added the Under Review label Jan 31, 2017

@wbnns wbnns added Help Needed and removed Under Review labels Feb 8, 2017

@wbnns wbnns added Bounty Bounty and removed Bounty labels May 21, 2017

Contributor

wbnns commented May 21, 2017 edited

Bounty: 20,000 bits / ~$50 USD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment