Pieter Wuille

Belgium

bitcoin.sipa.be

Age: 30

10h
comment Wallet.dat (<0.4.0) format: retrieving Bitcoin, possible security concerns
No need to use the false flag, as explained above. And having txindex=1 doesn't help one bit.
1d
comment Wallet.dat (<0.4.0) format: retrieving Bitcoin, possible security concerns
@George importwallet imports all keys at once already, and only rescans the necessary part intelligently.
1d
comment Wallet.dat (<0.4.0) format: retrieving Bitcoin, possible security concerns
@ChristopherGurnee yes, it will happen automatically.
1d
revised Wallet.dat (<0.4.0) format: retrieving Bitcoin, possible security concerns
deleted 2 characters in body
1d
answered Wallet.dat (<0.4.0) format: retrieving Bitcoin, possible security concerns
1d
comment Stopping Hash field in GetBlocks Message
No, not how many. Just the one after which the sender can stop.
1d
answered Stopping Hash field in GetBlocks Message
1d
comment What alternatives are there to hardcoding checkpoints into the Bitcoin client?
If checkpoints ever prevent a large reorganization, they would 1) prove that the PoW consensus mechanism has utterly failed 2) cause a fork in the networj between those who have that checkpoint and don't.
2d
answered Who issues bitcoins and how?
2d
comment Regtest: One node nullifying other node's balance
You are misunderstanding. In step 11, node1 generates block number 103. This is the 100th block on top of block number 3, whose coinbase matures at that point. This makes block number 3's generated coin (which belongs to node0, not node1), spendable.
2d
comment Transaction inclusion into block
In case there is not sufficient space in a block to encode the entire memory pool, the transactions with the highest fee per byte are included first.
2d
comment Generating blocks in regtest: "hash doesn't match nBits"
Of every two candidate block you try, one will be valid.
May
3
revised Alternatives to OP_RETURN to store data in Bitcoin blockchain
added 279 characters in body
May
3
revised Generating blocks in regtest: "hash doesn't match nBits"
added 2 characters in body
May
3
answered Alternatives to OP_RETURN to store data in Bitcoin blockchain
May
2
answered Generating blocks in regtest: "hash doesn't match nBits"
May
1
answered Transaction inclusion into block
May
1
answered Regtest: One node nullifying other node's balance
Apr
30
comment Transaction too large error
Priority is proportional to age, not inversely. And every output spent has its own scriptSig in the txin, which is around 105 bytes total per output spent.
Apr
30
comment Transaction too large error
@WizardOfOzzie The older ones are the better ones.
1 2 3 4 5