<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-04-23&#xA;📝 Original message:On Wed, Apr 23, 2014 at 10:44 PM, Adam Ritter &lt;aritter at gmail.com&gt; wrote:&#xA;&#xA;&gt; Isn&#39;t a faster blockchain for transactions (maybe as a sidechain) solving&#xA;&gt; the problem? If there would be a safe way for 0-confirmation transactions,&#xA;&gt; the Bitcoin blockchain wouldn&#39;t even be needed.&#xA;&gt;&#xA;&#xA;The 10 minute average comes from a desire to balance wasted work due to&#xA;natural chain splits with latency. With a very fast block interval you end&#xA;up with lots of forks and things take longer to converge, also, it can make&#xA;attacks easier because an attacker is building on his own blocks so he&#xA;doesn&#39;t suffer propagation delays and the attendant splits.&#xA;&#xA;It&#39;s not clear you can just make a faster block chain. 10 minutes is&#xA;somewhat arbitrary, it could be 5 minutes and the system would still work,&#xA;but it probably can&#39;t be 5 seconds.&#xA;&#xA;Unfortunately for best physical-world usability you really need very fast&#xA;payments. A few seconds is competitive with modern credit cards. The new&#xA;contactless cards seem to be able to reliably manage &lt;1 sec which is&#xA;impressive. Waiting for blocks in a block chain can&#39;t really work. Waiting&#xA;for propagation can work and has been working so far. Hence, the question&#xA;of how that mechanism can be kept working in the face of malicious miners,&#xA;before you end up having to fall back to trusted third parties and&#xA;recentralisation.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140423/642547fe/attachment.html&gt;</html></oembed>