{"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:2014-04-23\n📝 Original message:On Wed, Apr 23, 2014 at 05:41:26PM +0200, Pieter Wuille wrote:\n\u003e On Wed, Apr 23, 2014 at 5:34 PM, Kevin \u003ckevinsisco61784 at gmail.com\u003e wrote:\n\u003e \u003e I have some questions:\n\u003e \u003e 1.  How can we work towards solving the double-spending problem?\n\u003e \n\u003e We have this awesome technology that solves the double-spending\n\u003e problem. It's called a blockchain. Of course, it only works when\n\u003e transactions are actually in a block.\n\u003e \n\u003e This issue is about double-spending preventing before they're\n\u003e confirmed. This is (and has always been) just a best-effort mechanism\n\u003e in the network.\n\u003e \n\u003e \u003e 2.  Is it possible to \"scan\" for double-spending and correct it?\n\u003e \n\u003e That is what is being proposed here, by introducing a mechanism where\n\u003e miners can vote to penalize other miners if they seem to allow (too\n\u003e many?) double spends.\n\nWorse, it's a mechanism where miners can vote to penalize other miners\nfor any reason at all. Nothing in the mechanism requires any proof that\na double-spend happened, nor can it.  Even if you require the simple\n\"two signatures for same output\" mechanism, that just proves the\nexistance of a second signature, and says nothing at all about whether\nor not that signature was ever broadcast on any network.\n\n-- \n'peter'[:-1]@petertodd.org\n0000000000000000278031f86c71265f6eaf1fe9ce6cc831dc4f956676a7a7f7\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 685 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140423/c189cccd/attachment.sig\u003e"}