<oembed><type>rich</type><version>1.0</version><author_name>npub1vtwuk4rjyj6zrq3tv2z9lvdm6a7g8zujf0gz9q2vljlztdaqw36sjjsjpg</author_name><author_url>https://nostr.ae/npub1vtwuk4rjyj6zrq3tv2z9lvdm6a7g8zujf0gz9q2vljlztdaqw36sjjsjpg</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-08-11&#xA;📝 Original message:On Tue, Aug 11, 2015 at 1:46 PM, Michael Naber via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; Note that lightning / hub and spoke do not meet requirements for users&#xA;&gt; wishing to participate in global consensus, because they are not global&#xA;&gt; consensus networks, since all participating nodes are not aware of all&#xA;&gt; transactions.&#xA;&#xA;You don&#39;t need consensus on the lightning network because you are&#xA;using bitcoin consensus anyway. Commitment transactions are deep&#xA;enough in the blockchain history that removing that transaction from&#xA;the history is impractical. The remaining guarantees are ensured by&#xA;the properties of the scripts in the transaction. You don&#39;t need to&#xA;see all the transactions, but you do need to look at the transactions&#xA;you are given and draw conclusions based on the details to see whether&#xA;their commitments are valid or the setup wasn&#39;t broken.&#xA;&#xA;- Bryan&#xA;http://heybryan.org/&#xA;1 512 203 0507</html></oembed>