{"type":"rich","version":"1.0","author_name":"npub1xv3g4rkhj7eyape0cqjhc9g4ljdu5axqkgcdewma854a8r7e0mtsl5j2ga","author_url":"https://nostr.ae/npub1xv3g4rkhj7eyape0cqjhc9g4ljdu5axqkgcdewma854a8r7e0mtsl5j2ga","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-10-14\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nThis (Bitcoin-NG in concept) could be done as a (issue and pull\nrequest process) to Bitcoin Core itself, amirite?  It seems like it\nwould provide an interesting issue to open and have healthy discussion\non both mailing list and github, adding the caveat that it would be at\nthe user's option.  Thus if something like Bitcoin-NG did come to be\nit would be something more like a feature that the user could activate\n/ deactivate from within Core.  I assume it would be default off, but\nwith the option to utilize.  Code would thus be available to others as\nwell.  I am not saying yea or nay on it, just that it seems like this\ncould be done.\n\nSome notes:\n\nOnce a node generates a key block it becomes the leader.  As a leader,\nthe node is allowed to generate  microblocks  at  a  set  rate\nsmaller  than  a  prede\fned  maximum.  A  microblock in Bitcoin-NG\ncontains  ledger  entries  and  a  header.   The  header  contains\nthe  reference  to the  previous  block,  the  current  GMT  time,  a\n cryptographic  hash  of  its  ledger  entries,  and  a cryptographic\n signature  of  the  header.   The  signature  uses  the  private  key\n that  matches  the public key in the latest key block in the chain.\nFor a microblock to be valid, all its entries must be valid according\nto the specification of the state machine, and the signature has to be\nvalid.  However, the microblocks, it is said, don't affect the weight\nof the chain, because they do not contain proof of work.  It is\nassumed by the authors of this model that this situation is critical\nfor maintaining incentives here.\n\nThe questions that then begin to emerge to me are how is this\ninformation managed and protected?  The headers, thus containing\nreference(s) to previous block(s), current GMT time(s), cryptographic\nhash(es) of ledger entries, and cryptographic signature(s) of the\nheaders, so forth, and other information.  Can the Bitcoin-NG scheme\nbe designed or implemented in a manner which supports Stealth sends,\nConfidential Transactions, or similar privacy measures?  Or is this\nsomething which cannot be answered at this time?\n\nEmin Gün Sirer via bitcoin-dev:\n\u003e\u003e So it seems to me that all I need to do is figure out who the\n\u003e\u003e current\n\u003e leader is,\n\u003e\u003e and DDoS him off the network to shut Bitcoin-NG down.\n\u003e \n\u003e Good point. If NG is layered on top of Bitcoin, we'd retain all of\n\u003e Bitcoin as is. This would confer all the benefits of Bitcoin's\n\u003e retrospective blocks, as well as add the ability to mint\n\u003e microblocks with low latency in between. And despite the phrase\n\u003e \"the leader,\" the actual leader in NG is a key, not a specific\n\u003e node. That makes it possible to deter DDoS attacks by dynamically\n\u003e migrating where in the network the leader is operating in response\n\u003e to an attack. Finally, DDoS attacks against miners are already \n\u003e possible, but they seem rare, and I suspect it's at least partly\n\u003e because of the success of Matt Corallo's high speed bitcoin relay\n\u003e network. Similar defenses can apply here.\n\u003e \n\u003e - egs\n\u003e \n\u003e \n\u003e \n\u003e On Wed, Oct 14, 2015 at 2:20 PM, Bob McElrath \u003cbob at mcelrath.org\u003e\n\u003e wrote:\n\u003e \n\u003e\u003e So it seems to me that all I need to do is figure out who the\n\u003e\u003e current leader is, and DDoS him off the network to shut\n\u003e\u003e Bitcoin-NG down.\n\u003e\u003e \n\u003e\u003e This is a significant advantage to bitcoin's ex-post-facto\n\u003e\u003e blocks: no one knows where the next one will come from.  The only\n\u003e\u003e way to shut the network down is to shut all nodes down.\n\u003e\u003e \n\u003e\u003e Emin Gün Sirer via bitcoin-dev\n\u003e\u003e [bitcoin-dev at lists.linuxfoundation.org] wrote:\n\u003e\u003e\u003e Hi everyone,\n\u003e\u003e\u003e \n\u003e\u003e\u003e We just released the whitepaper describing Bitcoin-NG, a new\n\u003e\u003e\u003e technique\n\u003e\u003e for\n\u003e\u003e\u003e addressing some of the scalability challenges faced by\n\u003e\u003e\u003e Bitcoin.\n\u003e\u003e Surprisingly,\n\u003e\u003e\u003e Bitcoin-NG can simultaneously increase throughput while\n\u003e\u003e\u003e reducing\n\u003e\u003e latency, and\n\u003e\u003e\u003e do so without impacting Bitcoin's open architecture or changing\n\u003e\u003e\u003e its trust model. This post illustrates the core technique: \n\u003e\u003e\u003e http://hackingdistributed.com/2015/10/14/bitcoin-ng/ while the\n\u003e\u003e\u003e whitepaper has all the nitty gritty details: \n\u003e\u003e\u003e http://arxiv.org/abs/1510.02037\n\u003e\u003e\u003e \n\u003e\u003e\u003e Fitting NG on top of the current Bitcoin blockchain is future\n\u003e\u003e\u003e work that\n\u003e\u003e we\n\u003e\u003e\u003e think is quite possible. NG is compatible with both Bitcoin as\n\u003e\u003e\u003e is, as\n\u003e\u003e well as\n\u003e\u003e\u003e Blockstream-like sidechains, and we currently are not planning\n\u003e\u003e\u003e to compete commercially with either technology -- we see NG as\n\u003e\u003e\u003e being complementary\n\u003e\u003e to both\n\u003e\u003e\u003e efforts. This is pure science, published and shared with the\n\u003e\u003e\u003e community to advance the state of blockchains and to help them\n\u003e\u003e\u003e reach throughputs and latencies required of cutting edge\n\u003e\u003e\u003e fintech applications. Perhaps it can\n\u003e\u003e be\n\u003e\u003e\u003e adopted, or perhaps it can provide the spark of inspiration for\n\u003e\u003e\u003e someone\n\u003e\u003e else to\n\u003e\u003e\u003e come up with even better solutions.\n\u003e\u003e\u003e \n\u003e\u003e\u003e We would be delighted to hear your feedback. - Ittay Eyal and\n\u003e\u003e\u003e E. Gün Sirer.\n\u003e\u003e\u003e \n\u003e\u003e\u003e !DSPAM:561e98cd301391127216946!\n\u003e\u003e \n\u003e\u003e\u003e _______________________________________________ bitcoin-dev\n\u003e\u003e\u003e mailing list bitcoin-dev at lists.linuxfoundation.org \n\u003e\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e\u003e \n\u003e\u003e\u003e \n\u003e\u003e\u003e !DSPAM:561e98cd301391127216946!\n\u003e\u003e \n\u003e\u003e -- Cheers, Bob McElrath\n\u003e\u003e \n\u003e\u003e \"For every complex problem, there is a solution that is simple,\n\u003e\u003e neat, and wrong.\" -- H. L. Mencken\n\u003e\u003e \n\u003e\u003e \n\u003e \n\u003e \n\u003e \n\u003e _______________________________________________ bitcoin-dev mailing\n\u003e list bitcoin-dev at lists.linuxfoundation.org \n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \n\n- -- \nhttp://abis.io ~\n\"a protocol concept to enable decentralization\nand expansion of a giving economy, and a new social good\"\nhttps://keybase.io/odinn\n-----BEGIN PGP SIGNATURE-----\n\niQEcBAEBCgAGBQJWHtVfAAoJEGxwq/inSG8C85kH/2T07oj/JM+bQcgy2kw9rtUa\nXHkMNn86kVvtaniSKQ2j+SO9q8HkUI9Rv0Pz+qbX1CyAm6Z1FTCtDKornCnxx7FW\nAJyZQSm5n40LUBIc3o2NBJvXKySTO2jpxluw0HAU8BQHSgFWwj1+vocqObDYxRCd\nYDlhGd2ITmF55TlR+9seWqRyW+gABUoS+SaxM2yZaqWFlUGyOhYCJYpIo1nfWCZi\n1F7/j0E92zu5kS5JJuRE91A4Si0LeTQPtPqXMeVm/UicdQB1a/aI0mzp6VRdm3Bo\ngE79r1sKFFgpbQcz68OzPAL3RFTm1Q/C5jcqdy6cQjgp9em/v4uOCS3TKLWlVNQ=\n=Einy\n-----END PGP SIGNATURE-----"}