BRCs
BRCs copied to clipboard
💡 [IDEA] - Unified, Unambiguous Transport Independent TPN Broadcast Protocol
Summary
We need to align the ecosystem onto a single, unified, transport-independent protocol for transaction broadcast to the Transaction Processing Network, including proof acquisition, double-spend handling, and clear procedures [such as retrying or dropping] for all parties in case of all possible errors.
Currently, the ARC API is the closest we have. But having ANY ambiguity whatsoever when engaging with the Transaction Processing Network is fundamentally problematic.
Example
Sending transactions to the Transaction Processing Network is currently an ambiguous process, with both undefined failure modes and undefined partial and full success cases. This alignment would mitigate these issues.
Other information
No response
Relevance to BSV
- [X] This proposal is relevant to the Bitcoin SV network