On Thu, Jul 26, 2012 at 1:50 AM, Jeff Garzik jgar...@exmulti.com wrote:
Just run a query over the entire blockchain, looking at script opcode
use. I counted the number of times each opcode was used, in total:
https://gist.github.com/3180470
And here is the testnet3 data:
Just run a query over the entire blockchain, looking at script opcode
use. I counted the number of times each opcode was used, in total:
https://gist.github.com/3180470
(data in full)
OP_0 104
OP_1 27
OP_2 12
OP_2OVER 182
OP_2SWAP 182
OP_3 16
OP_4 1
OP_CHECKMULTISIG 22
OP_CHECKSIG 12188693
OP_CODESEPARATOR 14
OP_DEPTH 182
I'm interested to see what scripts were using OP_DEPTH and
OP_CODESEPARATOR, as the latter appears to be useless to my eyes.
Could you give some tx ids which use unusual opcodes?
--
Meh, probably harmless, but...
As best I can tell, OP_RESERVED does absolutely nothing (a NOP).
CScript::IsPushOnly(...) counts this as a push operation.
--
Live Security Virtual Conference
Exclusive live event will
Update: this class of machine just became useless for bitcoin.
When blk0002.dat was created to store more blocks, all forward
progress processing blocks turned into losing ground by 20 or so
a day. Guessing both datfiles were being accessed at once resulting
in disk based overload. I've not seen
On Fri, Jul 27, 2012 at 12:20 AM, grarpamp grarp...@gmail.com wrote:
Update: this class of machine just became useless for bitcoin.
When blk0002.dat was created to store more blocks, all forward
progress processing blocks turned into losing ground by 20 or so
a day. Guessing both datfiles were
I now have an 1.8 ghz p3 celeron (128k cache) which should be
substantially slower than your machine, running vintage 2.6.20 linux.
Unfortunately I forgot to turn on timestamp logging so I don't know
how long it took to sync the chain, but it was less than two days as
that was the span
7 matches
Mail list logo
