{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-09-16\n📝 Original message:During Scaling Bitcoin, Bitcoin Core committers and notable contributors\ngot together and chatted about where a \"greatest common denominator\" type\nconsensus might be.  The following is a without-attribution (Chatham House)\nsummary.  This is my own personal summary of the chat; any errors are my\nown; this is _not_ a consensus statement or anything formal.\n\n- Background (pre-conference, was on public IRC): \"net-utxo\", calculating\ntransaction size within block by applying a delta to transaction size based\non the amount of data added, or removed, from the UTXO set.  Fee is then\nevaluated after the delta is applied.  This aligns user incentives with\nUTXO resource usage/cost.  Original idea by gmaxwell (and others??).\n\n- Many interested or at least willing to accept a \"short term bump\", a hard\nfork to modify block size limit regime to be cost-based via \"net-utxo\"\nrather than a simple static hard limit.  2-4-8 and 17%/year were debated\nand seemed \"in range\" with what might work as a short term bump - net after\napplying the new cost metric.\n\n- Hard fork method:  Leaning towards \"if (timestamp \u003e X)\" flag day hard\nfork Y months in the future.  Set high bit in version, resulting in a\nnegative number, to more cleanly fork away.  \"miner advisement\" - miners,\nas they've done recently, signal non-binding (Bitcoin Core does not examine\nthe value) engineering readiness for a hard fork via coinbase moniker.\nSome fork cancellation method is useful, if unsuccessful after Z time\nelapses.\n\n- As discussed publicly elsewhere, other forks may be signaled via setting\na bit in version, and then triggering a fork'ing change once a threshold is\nreached.\n\nChat participants are invited to reply to this message with their own\ncorrections and comments and summary in their view.\n\nFor the wider community, take this as one of many \"inputs\" described at\nScaling Bitcoin.  Over the next few months developers and the community\nshould evaluate everything discussed and work towards some concrete\nproposal(s) that are implemented, tested and simulated in December in Hong\nKong.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150916/b53805a1/attachment.html\u003e"}