- Dec 16, 2015
- 2,806
- 6,088
During the blocktorrent discussion, @theZerg made several noteworthy proposals, one of which I would like to focus in this CFI:
Before I raise a BUIP on this, I'd like to ask for input from the community and hear your opinions here.
To make it easier to respond I will break this up into several questions - please feel free to respond only to some!
Keen to hear your thoughts & opinions.
I would strongly support this, and have had thoughts along those lines before (particularly about bypassing censorship systems).Create a transport "plugin" layer so new transports can be easily added. And I don't mean just TCP, UDP, etc. You could eventually even add transports like "fake web" that masquerade as http requests/responses in order to bypass censorship, etc.
Before I raise a BUIP on this, I'd like to ask for input from the community and hear your opinions here.
To make it easier to respond I will break this up into several questions - please feel free to respond only to some!
- Q1: Do you know of any prior discussion about this specific topic? (other projects, not strictly only Bitcoin, would also be useful)
- Q2: Any pointers to Bitcoin forum threads / mailing list threads / email exchanges that may be able to share?
- Q3: Do you think this should be done before Bitcoin Unlimited makes any other feature additions to the network code (e.g. BUIP006)?
- Q4: Any recommendations on existing C/C++ plugin frameworks that could be used for such a network transport abstraction? (as a fallback, suggestions about frameworks in other languages that could be used as inspiration are also welcome as long as you feel they are particularly clean / well-implemented)
- Q5: what do you think about implementing the interaction with peers as an entirely separate process which communicates with bitcoind via IPC?
Keen to hear your thoughts & opinions.
Last edited: