Topic: Pulling patches for version 0.6 (Read 3795 times)
Come on people... top up https://bitcointalksearch.org/topic/paidbounty-bip-0011-48215
Multiple signatures for single transaction ?
Simply GENIUS. This is effectively a built-in escrow service ! The ramifications of this will be simply **disastrous** for fiat-money-based economy. Now credit cards & bank accounts "security" looks more like an April's fool joke comparing to Bitcoin.
I have just read about this, and i came here right away.
Excellent work, Gavin & others.
Simply GENIUS. This is effectively a built-in escrow service ! The ramifications of this will be simply **disastrous** for fiat-money-based economy. Now credit cards & bank accounts "security" looks more like an April's fool joke comparing to Bitcoin.
I have just read about this, and i came here right away.
Excellent work, Gavin & others.
Quote from: ThiagoCMC
There are rumors that the Bitcoin network will split in two, one side, people using 0.5.1, 0.4.0.... On the other side, people using 0.6.0...
I've been working hard to make sure there will be no blockchain split, and I've convinced myself I've thought through all the "old/new client sending transactions to an old/new miner" cases.The only case where an old miner could be split off the network is if they are mining non-standard transactions (which means they've modified their mining code) and do not upgrade. If you are in that situation, then you should either stop adding transactions containing OP_NOP1 into your miner's memory pool or upgrade to interpret OP_NOP1 as OP_EVAL.
But I've said it before and I'll say it again: don't trust me. I make mistakes. Two serious bugs in my OP_EVAL/multisignature code have been found (and fixed) in the last week. Version 0.6 will have at least a month of release candidate testing.
I still firmly believe the benefits of the new 0.6 features far outweigh the risks. Please help minimize the risks; review code if you can, run release candidate on the testnet and try to break them, read the BIPS and try to think of ways bad people might use them to do bad things. Review the contingency plans and think about how they could be improved or if you could help when (when, not if) vulnerabilities are found.
Quote from: ThiagoCMC
There are rumors that the Bitcoin network will split in two, one side, people using 0.5.1, 0.4.0.... On the other side, people using 0.6.0...
I've been working hard to make sure there will be no blockchain split, and I've convinced myself I've thought through all the "old/new client sending transactions to an old/new miner" cases.The only case where an old miner could be split off the network is if they are mining non-standard transactions (which means they've modified their mining code) and do not upgrade. If you are in that situation, then you should either stop adding transactions containing OP_NOP1 into your miner's memory pool or upgrade to interpret OP_NOP1 as OP_EVAL.
But I've said it before and I'll say it again: don't trust me. I make mistakes. Two serious bugs in my OP_EVAL/multisignature code have been found (and fixed) in the last week. Version 0.6 will have at least a month of release candidate testing.
I still firmly believe the benefits of the new 0.6 features far outweigh the risks. Please help minimize the risks; review code if you can, run release candidate on the testnet and try to break them, read the BIPS and try to think of ways bad people might use them to do bad things. Review the contingency plans and think about how they could be improved or if you could help when (when, not if) vulnerabilities are found.
Quote from: ThiagoCMC
There are rumors that the Bitcoin network will split in two, one side, people using 0.5.1, 0.4.0.... On the other side, people using 0.6.0...
Could you be a little bit more specific? What about those rumors? Where is that yellow press I should read? 
I see that the "Full URL Support in bitcoin-qt" pull isn't coming, what's wrong with it?
0.6 merging isn't done. At least coinbaser and signmessage-GUI were accepted for 0.6 before it began, and they're still pending. There's some OP_EVAL issues that need to be sorted out as well. Gavin,
The Bitcoin 0.6.0 introduces a LOT of new features.
I just want to ask you guys ONE thing:
One month of testing before the oficial release.
Thank you guys for the hard work!!!
Best,
Thiago
The Bitcoin 0.6.0 introduces a LOT of new features.
I just want to ask you guys ONE thing:
One month of testing before the oficial release.
Thank you guys for the hard work!!!
Best,
Thiago
Hi!
I'll insist. We need to test version 0.6.0 A LOT before the final release.
There are rumors that the Bitcoin network will split in two, one side, people using 0.5.1, 0.4.0.... On the other side, people using 0.6.0...
So, I would like to test the version 0.6.0 for a month before the final release... Just to tranquilize the crowd...
Best!
Thiago
Great. Thanks Gavin. 0.6 has exciting additions I look forward to testing between the holidays.
+1... biggest update ever.
Wow! Impressive stuff. Nice work.
I see that the "Full URL Support in bitcoin-qt" pull isn't coming, what's wrong with it?
Gavin,
The Bitcoin 0.6.0 introduces a LOT of new features.
I just want to ask you guys ONE thing:
One month of testing before the oficial release.
Thank you guys for the hard work!!!
Best,
Thiago
The Bitcoin 0.6.0 introduces a LOT of new features.
I just want to ask you guys ONE thing:
One month of testing before the oficial release.
Thank you guys for the hard work!!!
Best,
Thiago
Is that gavinandresen/bitcoin-git or bitcoin/bitcoin? If I also pull the anon-ish 'coin control' is that likely to interfere with 0.6 testing? How and where would you prefer test feedback?
bitcoin/bitcoin is the 0.6 tree
I haven't done a code review of the anon-ish coin control, so I don't know if it will mess up 0.6 testing; it might interfere with the multisignature transaction changes.
The github issues tracker is the best to report any bugs you find, for general "it sucks" or "I love it" or "can you make this new RPC command to this" the best place is either IRC chat or right here.
Awesome changes, thanks Gavin!
Is that gavinandresen/bitcoin-git or bitcoin/bitcoin? If I also pull the anon-ish 'coin control' is that likely to interfere with 0.6 testing? How and where would you prefer test feedback?
This gonna be huge upgrade.
+1
private key import will convince me to move from 0.4 to 0.6
private key import will convince me to move from 0.4 to 0.6
BIP 11/12/13 support is Core functionality only for 0.6-- the network needs to support the new transaction types BEFORE users start using them.
Is BIP 11 going to be usable (eg, by GUI) by the average person or just some core functionality for some potential future changes?
Very excited
Great. Thanks Gavin. 0.6 has exciting additions I look forward to testing between the holidays.
Jump to: