{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-11-06\n📝 Original message:On Wed, Nov 01, 2017 at 05:48:27AM +0000, Devrandom via bitcoin-dev wrote:\n\nSome quick thoughts...\n\n\u003e Hi all,\n\u003e \n\u003e Feedback is welcome on the draft below.  In particular, I want to see if\n\u003e there is interest in further development of the idea and also interested in\n\u003e any attack vectors or undesirable dynamics.\n\u003e \n\u003e (Formatted version available here:\n\u003e https://github.com/devrandom/btc-papers/blob/master/aux-pow.md )\n\u003e \n\u003e # Soft-fork Introduction of a New POW\n\nFirst of all, I don't think you can really call this a soft-fork; I'd call it a\n\"pseudo-soft-fork\"\n\nMy reasoning being that after implementation, a chain with less total work than\nthe main chain - but more total SHA256^2 work than the main chain - might be\nfollowed by non-supporting clients. It's got some properties of a soft-fork,\nbut it's security model is definitely different.\n\n\u003e ### Aux POW intermediate block\n\u003e \n\u003e Auxiliary POW blocks are introduced between normal blocks - i.e. the chain\n\u003e alternates between the two POWs.\n\u003e Each aux-POW block points to the previous normal block and contains\n\u003e transactions just like a normal block.\n\u003e Each normal block points to the previous aux-POW block and must contain all\n\u003e transactions from the aux-POW block.\n\nNote how you're basically proposing for the block interval to be decreased,\nwhich has security implications due to increased orphan rates.\n\n\u003e ### Heaviest chain rule change\n\u003e \n\u003e This is a semi-hard change, because non-upgraded nodes can get on the wrong\n\u003e chain in case of attack.  However,\n\nExactly! Not really a soft-fork.\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 488 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171106/daf2333b/attachment-0001.sig\u003e"}