|
trout (OP)
|
 |
February 16, 2015, 07:43:08 PM
Last edit: May 25, 2015, 04:04:46 PM by gmaxwell |
|
is there already a tool to monitor BIP 66 acceptance status? (the number of bloks that say they are v3.0) as per https://bitcoin.org/en/release/v0.10.0 |
|
|
|
|
|
|
|
It is a common myth that Bitcoin is ruled by a majority of miners. This is not true. Bitcoin miners "vote" on the ordering of transactions, but that's all they do. They can't vote to change the network rules.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
vertoe
|
|
February 16, 2015, 08:26:19 PM |
|
just checked some blocks and all are v2. no idea on tools yet. should be trivial though, +1 subscribing to this thread.
i wonder if there will be a 0.9.4 release which includes bip66.
|
|
|
|
|
|
keystroke
|
|
February 20, 2015, 08:09:44 PM |
|
Following.
Is there a page which lists what % of the network has upgraded to 0.10.0?
|
"The difference between a castle and a prison is only a question of who holds the keys."
|
|
|
|
|
PRab
Member
 Offline
Activity: 98
Merit: 10
|
|
February 20, 2015, 10:14:09 PM |
|
Thats fine for monitoring nodes, but for the soft fork what matters is hash power. https://blockchain.info/pools shows that if the right 6 pools upgrade, then that will trigger the soft fork. |
|
|
|
|
PRab
Member
Offline
Activity: 98
Merit: 10
|
|
February 20, 2015, 11:12:17 PM
Last edit: February 21, 2015, 03:03:18 AM by PRab |
|
Not exactly "a tool to monitor BIP 66 acceptance status", but closest thing that I have seen. bitcoin.sipa.be/ver-ever.png |
|
|
|
|
|
trout (OP)
|
|
February 20, 2015, 11:43:42 PM |
|
want is interesting to monitor is how many of the latest 1001 blocks have v3 mark. here's the voting scheme: when 751 out of a sequence of 1001 blocks have version number 3 or higher, the new consensus rule becomes active for those blocks. When 951 out of a sequence of 1001 blocks have version number 3 or higher, it becomes mandatory for all blocks
|
|
|
|
|
DeathAndTaxes
Donator
Legendary
Offline
Activity: 1218
Merit: 1079
Gerald Davis
|
|
February 21, 2015, 03:16:09 AM |
|
I am not sure of an online tool but it is reported in the debug.log for bitcoind 2015-02-21 02:05:16 UpdateTip: new best=000000000000000015c21c962191ad91590c08cc1d07cf42ecc09a0d61907dfa height=344455 log2_work=82.280443 tx=60263298 date=2015-02-21 02:04:57 progress=1.000000
2015-02-21 02:05:16 SetBestChain: 3 of last 100 blocks above version 2
2015-02-21 02:05:16 ProcessBlock: ACCEPTED |
|
|
|
|
domob
Legendary
Offline
Activity: 1135
Merit: 1161
|
|
February 21, 2015, 07:57:59 PM |
|
Current status: 11 out of 1000 blocks with version 3. My script is at https://github.com/domob1812/namecore/blob/master/contrib/bip34-monitor/scanBip34.py. (Is this interesting as a pull request to Bitcoin, or not?) EDIT: Note that this script is initially for Namecoin. So you have to change also the RPC port to use it. |
Use your Namecoin identity as OpenID: https://nameid.org/Donations: 1 domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NC domobcmcmVdxC5yxMitojQ4tvAtv99pY BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS | GPG 0xA7330737 |
|
|
|
|
domob
Legendary
Offline
Activity: 1135
Merit: 1161
|
|
February 22, 2015, 09:42:14 AM |
|
Nice, I didn't know about them! |
Use your Namecoin identity as OpenID: https://nameid.org/Donations: 1 domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NC domobcmcmVdxC5yxMitojQ4tvAtv99pY BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS | GPG 0xA7330737 |
|
|
|
trout (OP)
|
|
March 29, 2015, 12:12:11 PM |
|
nice tools, thanks! notable pools/farms that upgraded so far: BTCChina Pool (currently 7% of the network hashrate), KNCMiner (6%) Bitcoin Affiliate Network (2%), BitMinter (1%) |
|
|
|
|
TierNolan
Legendary
Offline
Activity: 1232
Merit: 1083
|
|
May 17, 2015, 09:58:39 PM |
|
Looks like there was a spike in the last few days. If that is maintained, it means the vote is around 57% - 43%. I guess a pool must have upgraded. The 1 year graph shows a slope due to initial release then level then a step and level again and now another step. |
1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
|
|
|
|
trout (OP)
|
|
May 18, 2015, 06:01:55 AM |
|
I guess a pool must have upgraded.
yep, it's AntPool |
|
|
|
|
Peter Todd
Legendary
Offline
Activity: 1120
Merit: 1149
|
|
May 19, 2015, 03:10:38 AM |
|
I guess a pool must have upgraded.
yep, it's AntPool It's my buddies at FinalHash. |
|
|
|
FinalHash
Member
Offline
Activity: 108
Merit: 10
|
|
May 19, 2015, 03:17:47 AM |
|
Doing my boy Petey A solid of course!
|
|
|
|
|
FinalHash
Member
Offline
Activity: 108
Merit: 10
|
|
May 21, 2015, 01:16:18 PM |
|
I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.
|
|
|
|
|
TierNolan
Legendary
Offline
Activity: 1232
Merit: 1083
|
|
May 21, 2015, 02:34:19 PM |
|
I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.
There was a version of 0.9 released which can handle version 3 blocks. This allows nodes running older versions of the software to vote/accept version 3 blocks. http://sourceforge.net/p/bitcoin/mailman/message/34124466/https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.mdOnce 75% of the network starts enforcing the rules, legacy nodes could end up accepting invalid version 3 blocks. That is an expensive DOS attack though, since it requires spending POW on invalid blocks. |
1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
|
|
|
jl2012
Legendary
Offline
Activity: 1792
Merit: 1092
|
|
May 21, 2015, 05:59:50 PM |
|
I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.
There was a version of 0.9 released which can handle version 3 blocks. This allows nodes running older versions of the software to vote/accept version 3 blocks. http://sourceforge.net/p/bitcoin/mailman/message/34124466/https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.mdOnce 75% of the network starts enforcing the rules, legacy nodes could end up accepting invalid version 3 blocks. That is an expensive DOS attack though, since it requires spending POW on invalid blocks. And the attack like this would not be very effective because 75% of the network is mining a more restrictive chain. |
Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY)
LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC)
PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
|
|
|
|
altcoinex
|
|
May 21, 2015, 07:37:04 PM |
|
I talked to f2pool last night. Asked him to switch over as well. He will be hopefully switching over soon. That should get us alot closer.
There was a version of 0.9 released which can handle version 3 blocks. This allows nodes running older versions of the software to vote/accept version 3 blocks. http://sourceforge.net/p/bitcoin/mailman/message/34124466/https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.mdOnce 75% of the network starts enforcing the rules, legacy nodes could end up accepting invalid version 3 blocks. That is an expensive DOS attack though, since it requires spending POW on invalid blocks. And the attack like this would not be very effective because 75% of the network is mining a more restrictive chain. I think the more common theorized attack vector with this situation is double spending. --edit--: It has happened prior : https://bitcointalk.org/index.php?topic=152348.0 |
╓╢╬╣╣╖
┌║██████║∩
]█████████
╜██████╝`
╙╜╜╜`
╓╥@@@@@@╥╓
╓╖@@╖, ,@║██████████╢@, ,╓@@╖╓
╓╢██████╢. ╓╢███████████████╖ ║╢█████║╓
║█████████ ,,╓╓,, ┌║█████████████████┐ ,,╓╓,, ]█████████
└╢██████║` ╓╢║██████╢║∩``╙╙╙╙╙╙╙╙╙╙╙╙╙╙╙╙╙`»╢╢██████╢║╖ ║███████╜
"╜╜╜╜` ╖╢█████████╣╜ └╢██████████@ `╜╜╜╜╜
║██████████╜ ╙╢██████████
┌█████████╜ ╙╢█████████
└███████╨` ╜████████
║████╨╜ `╢█████
╙╢╣╜ └╢█╜
,, ,,
╓@║██┐ ┌██║@╓
╢██████ ]█████H
╢███████∩ ┌████████
╓@@@@╓ █████████ ║████████` ╓@@@@╖
╓╢██████║. █████████∩ ┌█████████ ,║███████╖
██████████ └█████████ ██████████ ]█████████
`║██████╜` └╢████████ ┌███████╣╜ ╙██████╨`
`╙╜╜╙` `╙╨╢████ █████╝╜` `╙╜╜`
]@╓ ╓╖H
███╢║@╓, ,╓@╢╢███`
████████╢@╖╓. ╓╖@║████████`
]███████████╢║@╓, ,╓@╢╢████████████
╙╢█████████████╨` ╜██████████████╜
╙╝╢███████║╜` `╜║████████╝╜`
,╓@@@╓ `²╙`` `╙²` ╓@@@╖,
║╢█████╢H ╓╢██████H
█████████ █████████`
╙╢██████╜ ╙╢██████╜
└╨╩╝┘ └╨╩╝╜ | WINFLOW | . |
██
██
██
██
██
██
██
██
██
██
██
██
██
| . | | . |
██
██
██
██
██
██
██
██
██
██
██
██
██
| . | |
|
|
|
|
