From: jl2012@xbt•hk
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Encouraging mining of the first few big blocks with OP_CSV and BIP68
Date: Sun, 23 Aug 2015 14:08:41 -0400 [thread overview]
Message-ID: <8e1f634bb21c57090351bf02360add12@xbt.hk> (raw)
Someone is going to burn 150BTC to create a backlog of 30-day in
September.
https://www.reddit.com/r/Bitcoin/comments/3hgke4/coinwallet_says_bitcoin_stress_test_in_september/
However, the money could be spent more wisely by encouraging mining of
the first few big blocks
Assumptions:
1. OP_CSV and BIP68 are enabled
2. Max tx size remains 1MB
The donor will create a transaction, with an input of 150BTC, and 10
outputs:
1. 0 BTC to "OP_RETURN <garbage>"
2. 42 BTC to "OP_1 OP_CSV"
3. 21 BTC to "OP_2 OP_CSV"
4. 10.5 BTC to "OP_3 OP_CSV"
5. 5.25 BTC to "OP_4 OP_CSV"
6. 2.625 BTC to "OP_5 OP_CSV"
7. 1.3125 BTC to "OP_6 OP_CSV"
8. 0.65625 BTC to "OP_7 OP_CSV"
9. 0.328125 BTC to "OP_8 OP_CSV"
10. 0.328125 BTC to "OP_9 OP_CSV"
The first output will fill up the size to 1MB.
This tx could not be confirmed by a pre-hardfork miner because the
coinbase tx will consume some block space. The first big block miner
will be able to collect 66BTC of fee. The block confirming the first big
block will collect 42BTC of fee, etc. This will create a long enough
chain to bootstrap the hardfork.
The amount is chosen to make sure the difference is <25BTC, so miners
would have less incentive to create a fork instead of confirming other's
block. However, a miner cartel may launch a 51% attack to collect all
money. Such incentive may be reduced by adjusting the distribution of
donation. (Actually, such cartel may be formed anytime, just for
collecting more block reward)
next reply other threads:[~2015-08-23 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 18:08 jl2012 [this message]
2015-08-23 19:43 ` Hector Chu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e1f634bb21c57090351bf02360add12@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox