Topic: New SegWit stats? - page 3. (Read 5549 times)

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

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).

No.

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

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.

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


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.

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.

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.

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.

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

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

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?

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.

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

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.


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.

http://api.qbit.ninja/versionstats

Posting here to see if I've got all this right ...

From the stats I see:
1) the difficulty period started about 13 hours ago.
2) 12 blocks signalled segwit, 78 blocks have not
3) in a few more hours at that same segwit signalliing rate, we'll have failed to activate in this difficulty period and next chance starts in about 13 days.

I say we will fail in a few hours because once there are 100 blocks not signalling segwit, we have the 5% (100/2016) which guarantees we can't reach the 95% required.

Delving into the blocks, I see that pools are not signalling correctly. For example bitfury advertises segwit support in their coinbase string, yet they are not setting the bip 9 bit for segwit. BTCC supports segwit (I believed), but is not signalling it. Obviously these guys didn't regard getting segwit activated asap to be much of a priority.

Am I on track with all the above?

While I've got your attention, is there a way for me to get all the voting info used above from my bitcoin node? I can't see rpc commands that yield the right stats.

edit: changed 'miners' to pools. spelling...
edit2: I see btcc started signalling correctly at block 43 (7 hours into the voting period). Too late tho ...
edit3: It's only 20 hours into the segwit voting, and we've failed. 100 non-segwit blocks cf 21 segwit.
Pools like bitfury now have 13 days or so to get their act together before the next period. Earliest segwit activation is now mid december.

Correct. Ver & co are trying to spin the story that the pools are actually in control, which is entirely different from the reality. Currently the majority of nodes are Bitcoin Core, and the number of Segwit nodes is also quite high (29%).

To expand on this Wind_FURY, look at the article that I've just read. They have found 3 *bugs* to list 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.

---

Update: The article was refuted by several people who got heavily downvoted.

It doesn't matter whats the opinion of a pool is.
The miner can decide. When they decide that the pool isn't representing their opinion, they will switch to another pool.
Easy as that.

Also full node could decide to not forward found blocks of mentioned pool.

In other words: It doesn't count whats a pool says. The dont have any might.

No, not really. I have not read a single valid argument from them. Unless you think that switching to an implementation with almost zero QA and peer review is a *valid argument*.

That is not true. Nobody has to stop anything.

That is if it gets activated. News are still swirled around that ViaBTC has 10% of all hashing power and that they are highly motivated to block Segregated Witness. They have valid arguments for doing so like the change in Bitcoin address requiring them to start with a "3". This will be an inconvenience to everyone and the Bitcoin economy has to literally stop for some time to update and audit everything.

No. Segwit signaling will start after the first re-targeting after 15/11 (which is today). The first re-targeting should happen around the 18th of November. Anyhow, soft forks take time to activate so don't expect everyone on board in the first few days.

---

I'm pretty confident that a successful activation is going to have a positive effect on the price, especially after >1MB blocks start getting mined.

Sorry for reviving this topic but afaik today a segwit vote starts, am I right?
Are there any stats now?