New SegWit stats?

[harrymmmm]

Code:

Current SegWit signal percentage
2.93% (last 2016 blocks)
18.75% (last 144 blocks)
Source: https://bitcoincore.org/en/segwit_adoption/

Signalling hasn't stopped, of course, so the average rate is interesting. But right now, lockin has failed and the only relevant signalling will be in the next difficulty retarget period starting in about 13 days.

http://api.qbit.ninja/versionstats

Yep. This is what I was using. Together with coin.dance and blockchain.info to look inside the blocks to see who was signalling incorrectly.

[talkbitcoin]

Code:

Current SegWit signal percentage
2.93% (last 2016 blocks)
18.75% (last 144 blocks)
Source: https://bitcoincore.org/en/segwit_adoption/

Signalling hasn't stopped, of course, so the average rate is interesting. But right now, lockin has failed and the only relevant signalling will be in the next difficulty retarget period starting in about 13 days.

http://api.qbit.ninja/versionstats

Yep. This is what I was using. Together with coin.dance and blockchain.info to look inside the blocks to see who was signalling incorrectly.

are you sure about what you are saying because according to bitcoincore.org the signalling does not start until 20th which is tomorrow.

although looking at the site https://bitcoincore.org/en/segwit_adoption/ they seem to have removed the date which was in the first line!

edit: yeap it is on 19th afternoon: http://bitcoin.stackexchange.com/questions/49447/when-does-signaling-for-segwit-start-exactly

[harrymmmm]

Code:

Current SegWit signal percentage
2.93% (last 2016 blocks)
18.75% (last 144 blocks)
Source: https://bitcoincore.org/en/segwit_adoption/

Signalling hasn't stopped, of course, so the average rate is interesting. But right now, lockin has failed and the only relevant signalling will be in the next difficulty retarget period starting in about 13 days.

http://api.qbit.ninja/versionstats

Yep. This is what I was using. Together with coin.dance and blockchain.info to look inside the blocks to see who was signalling incorrectly.

are you sure about what you are saying because according to bitcoincore.org the signalling does not start until 20th which is tomorrow.

although looking at the site https://bitcoincore.org/en/segwit_adoption/ they seem to have removed the date which was in the first line!

edit: yeap it is on 19th afternoon: http://bitcoin.stackexchange.com/questions/49447/when-does-signaling-for-segwit-start-exactly

Nope. It's started (and finished already)

That post you're quoting was made 2 weeks ago, and was the best guess at the time for when the signalling would start.
The defining criterion for the difficulty retarget and therefore the start of the signalling is when the block number mod 2016 is 0
That happened yesterday.
The lockin succeeds if 95% of the blocks in that difficulty epoch signal segwit support; it fails if more than 5% of the blocks do not signal segwit. 5% of the 2016 blocks is just 100 blocks. That happened about 20 hours after the start.

[DaRude]

Anyone keeping track of the pool's official position on segwit? Like AntPool, F2Pool, BTCC Pool etc..? Are they just waiting to implement it or do they oppose segwit?

[talks_cheep]

Anyone keeping track of the pool's official position on segwit? Like AntPool, F2Pool, BTCC Pool etc..? Are they just waiting to implement it or do they oppose segwit?

The Chinese pools don't care. They are working on their own China-made solution. You're all gonna be so fawked.

[pooya87]

Anyone keeping track of the pool's official position on segwit? Like AntPool, F2Pool, BTCC Pool etc..? Are they just waiting to implement it or do they oppose segwit?

I could not find any good resources on the internet listing mining pools and their stance (like the hashrate they own table) but there is this: https://www.blocktrail.com/BTC/blocks/1 which has tags about which proposal they are supporting and you have to do the chart thing yourself.
these are pools that seems to be supporting SegWit:
https://www.blocktrail.com/BTC/blockversion/segwit
BitClub Network
Slush
BTCC

[harrymmmm]

Anyone keeping track of the pool's official position on segwit? Like AntPool, F2Pool, BTCC Pool etc..? Are they just waiting to implement it or do they oppose segwit?

I could not find any good resources on the internet listing mining pools and their stance (like the hashrate they own table) but there is this: https://www.blocktrail.com/BTC/blocks/1 which has tags about which proposal they are supporting and you have to do the chart thing yourself.
these are pools that seems to be supporting SegWit:
https://www.blocktrail.com/BTC/blockversion/segwit
BitClub Network
Slush
BTCC

Bitfury is advertising segwit support in the coinbase string, but last time I checked (yesterday) they still weren't correctly signalling that support.
No hurry tho ... as long as they start before next week.

[harrymmmm]

Anyone keeping track of the pool's official position on segwit? Like AntPool, F2Pool, BTCC Pool etc..? Are they just waiting to implement it or do they oppose segwit?

Does pool support mean they will also contribute to signalling or does it simply mean they will not get in line with the (planned) alternatives?

Just seems a bit quiet on the western side.

I could not find any good resources on the internet listing mining pools and their stance (like the hashrate they own table) but there is this: https://www.blocktrail.com/BTC/blocks/1 which has tags about which proposal they are supporting and you have to do the chart thing yourself.
these are pools that seems to be supporting SegWit:
https://www.blocktrail.com/BTC/blockversion/segwit
BitClub Network
Slush
BTCC

Fixed your quotes

What follows is my guess; I have little knowledge of miner/pool incentives:

A miner who politically supports segwit can get more fees (when segwit activates). That should mean incentives for him to move to a pool that signals segwit support in advance if his existing pool does not.
We're seeing this move away from ViaBTC already.

A miner who politically rejects segwit or (same thing) just doesn't know what's happening is making a statement. Most of these guys probably plan to switch to segwit just before activation.
Some diehards will, no doubt, remain on a non-segwit client (mostly that means old core, or BU) and forgo the extra fees.

So, hash support is what really matters, but pools need to go along with the hashers or lose customers.

[maku]

Anyone keeping track of the pool's official position on segwit? Like AntPool, F2Pool, BTCC Pool etc..? Are they just waiting to implement it or do they oppose segwit?

The Chinese pools don't care. They are working on their own China-made solution. You're all gonna be so fawked.

Are you talking to some other bitcoin update or version like Bitcoin Unlimited. Or you have on mind completly different project, a new coin Chinese government announced recently?
Either way if Chinese miners will try do to something ridiculous and strange they would suffer the most as they invested more than anyone in bitcoin.

[jbreher]

and the number of Segwit nodes is also quite high (29%).

While it may just be variance, last 1000 blocks says SegWit support is under 19%.

To expand on this Wind_FURY, look at the article that I've just read. They find 3 *bug* to list in a post to make it seem like BU team is competent and whatnot, while they are actually still running on a code base that is very far behind.

Well, no. It is not 'very far behind'. It is bereft of the cruft that core has added that the BU community does not accept.

Spin it whatever way you want, you epically missed the point of the post.

[quake313]

No doubt the Chinese are flexing on the core devs. I don't like where this is going. We may end up with at least 2 chains, a China chain backed by Chinese Devs and a US chain backed by Core Devs.

[Lauda]

and the number of Segwit nodes is also quite high (29%).

While it may just be variance, last 1000 blocks says SegWit support is under 19%.

I was talking about nodes here, not blocks. They are currently at 31.45%.

Well, no. It is not 'very far behind'. It is bereft of the cruft that core has added that the BU community does not accept.

Yes, it is very far behind. There have been plenty of bugfixed and improvements between 0.12.1 and 0.13.1 (excluding those that 'BU community' does not accept).

Spin it whatever way you want, you epically missed the point of the post.

No.

No doubt the Chinese are flexing on the core devs. I don't like where this is going. We may end up with at least 2 chains, a China chain backed by Chinese Devs and a US chain backed by Core Devs.

This is false FUD. Who are these "Chinese Devs"?

[Paashaas]

Segwit support at 25% for the last 144 blocks.

[Meuh6879]

source of this graph : http://bitcoin.sipa.be/versions.html

[jbreher]

Well, no. It is not 'very far behind'. It is bereft of the cruft that core has added that the BU community does not accept.

Yes, it is very far behind. There have been plenty of bugfixed and improvements between 0.12.1 and 0.13.1 (excluding those that 'BU community' does not accept).

Spin it whatever way you want, you epically missed the point of the post.

[Killerpotleaf]

Well, no. It is not 'very far behind'. It is bereft of the cruft that core has added that the BU community does not accept.

Yes, it is very far behind. There have been plenty of bugfixed and improvements between 0.12.1 and 0.13.1 (excluding those that 'BU community' does not accept).

Spin it whatever way you want, you epically missed the point of the post.

your crufty post is bereft
Lol!

[afbitcoins]

Can someone explain this in easy terms? If you run a bitcoin node to are supposed to signal segwit support? how do you do that?

edit: Why would you not support or not support it? I thought it was a no brainer. Increased capacity more efficient etc. What am I missing?

[Lauda]

Can someone explain this in easy terms? If you run a bitcoin node to are supposed to signal segwit support? how do you do that?

Upgrade to Bitcoin Core 0.13.1 and your node will automatically follow Segwit rules after(if) it activates.

[afbitcoins]

Can someone explain this in easy terms? If you run a bitcoin node to are supposed to signal segwit support? how do you do that?

Upgrade to Bitcoin Core 0.13.1 and your node will automatically follow Segwit rules after(if) it activates.

Ah ok, thanks

[redsn0w]

I found this http://segwit.co/

Can someone explain this in easy terms? If you run a bitcoin node to are supposed to signal segwit support? how do you do that?

edit: Why would you not support or not support it? I thought it was a no brainer. Increased capacity more efficient etc. What am I missing?

Only the miners can signal segwit through the mined blocks, your node will be counted only as a segwit node (0.13.1 bitcoin-core).