<oembed><type>rich</type><version>1.0</version><author_name>npub1aslmpzentw224n3s6yccru4dq2qdlx7rfudfnqevfck637cjt6esswfqmx</author_name><author_url>https://nostr.ae/npub1aslmpzentw224n3s6yccru4dq2qdlx7rfudfnqevfck637cjt6esswfqmx</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2023-05-23&#xA;🗒️ Summary of this message: A proposed alternative relay mechanism for Bitcoin transactions, called Nostr, could address limitations in the current P2P system and support non-standard transactions. Miners would listen for broadcasted transaction packages and insert them into their local mempool, potentially boosting the system&#39;s resilience and democratizing access to miner mempools. Nostr could also delegate responsibility for dealing with DoS threats to relays and introduce more flexibility in the system. A prototype has been developed and demonstrated in a video.&#xA;📝 Original message:Hi,&#xA;&#xA;&#xA;I write to get your thoughts on an alternative approach for Bitcoin&#xA;transaction relay, addressing some of the limitations in the current&#xA;peer-to-peer transaction relay system. To the best of my knowledge, the&#xA;credit for the original concept goes to Ben Carman. I felt it would be&#xA;beneficial to share the idea on this list to garner wider perspectives and&#xA;feedback.&#xA;&#xA;&#xA;The existing peer-to-peer (P2P) transaction relay system comes with a set&#xA;of limitations that may negatively impact applications, notably those like&#xA;Lightning that make extensive use of pre-signed transactions. A key&#xA;limitation lies in the system&#39;s inability to relay transaction packages.&#xA;This constraint can lead to HTLCs expiring before being swept, thereby&#xA;risking fund losses. In addition, the P2P system falls short in supporting&#xA;non-standard transactions, despite an established demand for such&#xA;transactions in the marketplace.&#xA;&#xA;&#xA;Nostr, an open and decentralized network of relays for public and ephemeral&#xA;messages between pseudonymous entities, could help address these&#xA;shortcomings. With the standards defined in NIP-89 [1], it becomes possible&#xA;to broadcast arbitrary Bitcoin transaction packages, overcoming one of the&#xA;key hurdles in the current relay system.&#xA;&#xA;&#xA;In this proposed alternative relay mechanism, miners would listen for these&#xA;broadcasted transaction packages and insert the packages into their local&#xA;mempool. They can take advantage of the `submitpackage` RPC, limited to&#xA;safe topologies only - specifically child and direct parents, tree only&#xA;[2]. This feature could serve as an interim solution for package relay&#xA;until it becomes available through the traditional P2P method.&#xA;&#xA;&#xA;A notable advantage of this approach is that it delegates the&#xA;responsibility of dealing with Denial-of-Service (DoS) threats to the&#xA;relays themselves. They could, for example, require a payment to mitigate&#xA;such concerns. There are in fact paid nostr relays already in operation.&#xA;This partitioning would result in a clear separation between the Bitcoin&#xA;transaction layer and DoS protection, introducing more flexibility in the&#xA;system and potentially boosting its resilience.&#xA;&#xA;&#xA;Implementing Nostr as a relay mechanism also has the potential to&#xA;democratize access to miner mempools, thus leveling the playing field in&#xA;the Bitcoin network. In the current state, those with direct connections or&#xA;certain privileges can more readily submit transactions to miners, perhaps&#xA;even through means as informal as email.&#xA;&#xA;&#xA;I have been working on a prototype of this concept (based on [3]) and have&#xA;captured its workings in a demonstration video [4].&#xA;&#xA;&#xA;Joost&#xA;&#xA;&#xA;[1] https://github.com/nostr-protocol/nips/pull/476&#xA;&#xA;[2] https://github.com/bitcoin/bitcoin/pull/27609#issuecomment-1544414801&#xA;&#xA;[3] https://github.com/benthecarman/nostr-tx-broadcast&#xA;&#xA;[4] https://twitter.com/joostjgr/status/1658487013237211155&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230523/6866548f/attachment.html&gt;</html></oembed>