While writing the script engine for pynode, I ran a test to validate
my script tokenizer -- a python script which does nothing more than
split up scriptPubKey and scriptSig into component opcodes and data
elements. No execution, just tokenization of the script's data
stream.
Scanning the entire b
On Monday, July 23, 2012 12:41:15 AM Gavin Andresen wrote:
> > 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
> 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
Given a testbed: Pentium 4 1.8GHz single core, 2GB ram, FreeBSD 8,
disk is geli aes-128 + zfs sha-256, bitcoin 0.6.3, Tor proxy,
An estimate is made that by the end of the year bitcoin will
completely overrun the capabilities of this reasonable class of
machines.
It already takes a month to build a
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
Github URL: https://github.com/jgarzik/pynode
pynode is a simple bitcoin P2P client, based on ArtForz' half-a-node,
which maintains a blockchain database and TX memory pool.
It is intended to be a useful base for another projects, such as
network monitoring nodes.
At present, it is mainly for de
6 matches
Mail list logo
