From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Reconsidering block version number use
Date: Sun, 22 Jul 2012 20:52:25 +0000 [thread overview]
Message-ID: <201207222052.28579.luke@dashjr.org> (raw)
It just occurred to me that the block version number could easily be used as a
cheap "extra nonce" right now. Considering that we will probably see lots of
ASIC miners running at 1 TH/s per rig before the end of 2012, it might be
desirable to save the block version for this purpose.
The current block height in coinbase addition currently proposes to use block
version 2. However, the protocol change is in fact to the coinbase
transaction, not the block itself (which really doesn't have any extensibility
without a hardfork anyway). Perhaps we should consider bumping the coinbase
transaction version number to 2 for this instead?
Also, Jeff noticed that block 190192 has version==2 without a valid block
height in the coinbase. I suspect this may be the result of combining the
current blockheight-in-coinbase pullreq with P2Pool. This means that if we go
forward with the version==2 marker, we will forever need to make an exception
for that block. Moving the version==2 to the coinbase transaction version also
means whoever makes that transaction (thus deciding whether to put the height
in it or not) also sets the version number - instead of the block version
coming from bitcoind and the coinbase transaction coming from P2Pool or other
software.
Thoughts?
Luke
next reply other threads:[~2012-07-22 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 20:52 Luke-Jr [this message]
2012-07-23 0:41 ` Gavin Andresen
2012-07-23 0:57 ` Luke-Jr
2012-07-24 7:58 ` Mike Hearn
2012-07-24 8:01 ` Peter Vessenes
2012-07-24 8:22 ` Mike Hearn
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=201207222052.28579.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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