💡 [IDEA] - Unified, Unambiguous Transport Independent TPN Broadcast Protocol

[ty-everett]

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

• This proposal is relevant to the Bitcoin SV network

[ty-everett]

Unless we align on making this new protocol THE exclusive way to interact with the TPN, we should also account for other, out-of-band interactions.

Broadly, I can conceive of three types of interactions:

• Transaction Ingest Messages (inwards, from the Transacting Parties to the TPN)
• Transaction Responses [success and error] (outwards, from the Transaction Processors to the Transacting Parties)
• Unsolicited Callbacks (again, outwards), for Inclusion Notifications and Double Spend Alerts

[rob-tkn]

A minimal "model client" example would be helpful.