|
Title: About the "Unknown block versions being mined!" warning Post by: achow101 on July 17, 2017, 10:20:29 PM If you are using Bitcoin Core and derivative software, then you may have noticed that there is now a warning that states:
Quote Warning: Unknown block versions being mined! It's possible unknown rules are in effect This warning will appear at the top of the Bitcoin Core GUI and reported in the errors or warnings field of the getinfo, getnetworkinfo, and getmininginfo RPC commands. This warning is triggered when more than 50 of the last 100 blocks have a version number that Bitcoin Core does not expect. Currently that is being triggered by miners mining for BIP 91 (aka the first half of segwit2x). These miners are setting bit 4 of the block version field, and Bitcoin Core does not expect this to be set. The version numbers that Bitcoin Core expects are 0x20000000 (536870912) and 0x20000002 (536870914). The unexpected version numbers currently are 0x20000012 (536870930) and 0x20000010 (536870928). Currently this warning is benign as there is no fork and no new network rules have activated. Your coins are not at risk. Title: Re: About the "Unknown block versions being mined!" warning Post by: Mad7Scientist on July 17, 2017, 10:43:44 PM I'm glad the developers thought to put that warning in. So basically this means that we're getting SegWit2x, or at least the first phase of it since it's still 4 days away from July 21st when SegWit2x activates and that warning indicates that 50% or more of miners are SegWit2x which is enough to win the soft fork. I guess whether the hard fork stays or not remains to be seen.
Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 17, 2017, 11:03:21 PM I'm glad the developers thought to put that warning in. So basically this means that we're getting SegWit2x, No, that is not a guarantee that we will be getting segwit2x.or at least the first phase of it since it's still 4 days away from July 21st when SegWit2x activates Segwit2x is not guaranteed to activate on July 21st. It is not activated via flag day, rather it is activated via miner signalling. July 21st is the day that those who signed the New York Agreement for Segwit2x are supposed to begin signalling and running segwit2x nodes. But that is not a guarantee that activation will happen that day nor is it a guarantee that everyone will actually do so.and that warning indicates that 50% or more of miners are SegWit2x which is enough to win the soft fork. No, that is completely incorrect. The threshold for BIP 91 (the first half of segwit2x) is 80%, not 50%. Secondly, a 100 block period is much too short to determine anything. It can be highly affected by variance and luck. You need to much longer timespan to determine how much support there actually is. Even the 336 block window for BIP 91 is very short and could be affected by variance so there could actually be less than 80% hash rate support and BIP 91 would still activate.Title: Re: About the "Unknown block versions being mined!" warning Post by: Mad7Scientist on July 17, 2017, 11:20:46 PM 80% of exactly what must be present in the blockchain for SegWit2x to activate?
Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 17, 2017, 11:46:05 PM 80% of exactly what must be present in the blockchain for SegWit2x to activate? 269 of the last 336 blocks (~80% of the last 336 blocks) must set bit 4 of the version number field in order for BIP 91 (first half of segwit2x) to activate. Title: Re: About the "Unknown block versions being mined!" warning Post by: Icon on July 18, 2017, 01:37:11 AM well if segwit goes active will it work with our core 14.x version ? or are we screwed?
Icon Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 18, 2017, 02:07:26 AM well if segwit goes active will it work with our core 14.x version ? or are we screwed? Yes, it will work with Bitcoin Core 0.13.1+Icon Title: Re: About the "Unknown block versions being mined!" warning Post by: Mad7Scientist on July 18, 2017, 02:11:45 AM It shouldn't matter for non miners right?
Title: Re: About the "Unknown block versions being mined!" warning Post by: Icon on July 18, 2017, 02:12:50 AM O ok, well thought they were implementing a different version of segwit, seeing i read core's version needed 95% signaling for it to go active, but segwit2x is doing it with ~ 80%? Anyways as long as its the same as core version shouldn't have any forks, i guess until they start the hard fork to 2mb block size right?
Icon Title: Re: About the "Unknown block versions being mined!" warning Post by: Icon on July 18, 2017, 02:14:50 AM It shouldn't matter for non miners right? Only if you hold your own private keys to your coins.. If a website/smart phone does then it doesn't matter for non miners. Icon Title: Re: About the "Unknown block versions being mined!" warning Post by: CreditM8 on July 18, 2017, 02:24:37 AM Thanks for the warning. Haven't started mining just yet, but better to know than not.
Title: Re: About the "Unknown block versions being mined!" warning Post by: Amph on July 18, 2017, 05:45:30 AM so even in a remote case of an hard fork, which could be imminent, we just leave our coins there on core, and we should be safe from my understanding, as long as we don't move those coins right?
Title: Re: About the "Unknown block versions being mined!" warning Post by: freedomno1 on July 18, 2017, 06:42:04 AM Thanks Achow for the clarification for those who are not keeping track of the forking issues, this would scare a few individuals since it has not been seen before even if they are running core and know the fork is coming how it impacts the nodes isn't really defined.
On a sidenote what versions of Bitcoin Core should a person utilize considered safest for segwit2x or does it matter as long as it ain't QT ^^. Title: Re: About the "Unknown block versions being mined!" warning Post by: orio on July 18, 2017, 06:45:55 AM Hello
If I see that message in my Core wallet, is it safe to send coins somewhere now ? Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 18, 2017, 07:01:32 AM O ok, well thought they were implementing a different version of segwit, seeing i read core's version needed 95% signaling for it to go active, but segwit2x is doing it with ~ 80%? Segwit2x is using BIP 91. BIP 91 specifies that 269 of the last 336 blocks (~80% of the last 336 blocks) must signal for BIP 91 on bit 4. Once there is enough signalling, it will be locked in for a short grace period of 336 blocks. Then it will activate. Once BIP 91 activates, all blocks must signal for segwit on bit 1. This means that segwit will then activate via its original deployment on bit 1. Segwit2x is not actually activating a different segwit, they are activating something else which will force the activation of segwit.Anyways as long as its the same as core version shouldn't have any forks, i guess until they start the hard fork to 2mb block size right? There may be forks since 20% of the hash rate won't be support BIP 91 and thus will likely not be signalling bit 1 for segwit. With some luck and spy mining, forks could be made from miners extending a chain off of a block which does not signal bit 1. However Bitcoin Core will allow you to choose the chain to use (via the invalidateblock RPC command) and any of the forks will be valid to Core.If BIP 91 activates successfully and everyone who claims they will enforce it actually enforces it, then there shouldn't be a fork. so even in a remote case of an hard fork, which could be imminent, we just leave our coins there on core, and we should be safe from my understanding, as logn as we don't move those coins right? Yes. Coins at rest are not at risk.On a sidenote what versions of Bitcoin Core should a person utilize considered safest for segwit2x or does it matter as long as it ain't QT ^^. Any recent version of Core should be fine, even ones that don't have segwit support.If I see that message in my Core wallet, is it safe to send coins somewhere now ? Yes. There currently is no fork, so you can safely send your coins.Title: Re: About the "Unknown block versions being mined!" warning Post by: Minecache on July 18, 2017, 07:32:23 AM If you are using Bitcoin Core and derivative software, then you may have noticed that there is now a warning that states: Quote Warning: Unknown block versions being mined! It's possible unknown rules are in effect This warning will appear at the top of the Bitcoin Core GUI and reported in the errors or warnings field of the getinfo, getnetworkinfo, and getmininginfo RPC commands. This warning is triggered when more than 50 of the last 100 blocks have a version number that Bitcoin Core does not expect. Currently that is being triggered by miners mining for BIP 91 (aka the first half of segwit2x). These miners are setting bit 4 of the block version field, and Bitcoin Core does not expect this to be set. The version numbers that Bitcoin Core expects are 0x20000000 (536870912) and 0x20000002 (536870914). The unexpected version numbers currently are 0x20000012 (536870930) and 0x20000010 (536870928). Currently this warning is benign as there is no fork and no new network rules have activated. Your coins are not at risk. Maybe you could pin this and lock the thread where the member is intentially fudding over this? https://bitcointalk.org/index.php?topic=2027108.0 Title: Re: About the "Unknown block versions being mined!" warning Post by: J.Socal on July 18, 2017, 08:49:29 AM So what day should we stop buying or selling btc?And for how long?
Title: Re: About the "Unknown block versions being mined!" warning Post by: kano on July 18, 2017, 10:18:06 AM It seems a little bazaar that achow101 is complaining about an 80% acceptance for SegWit with BIP91
when MOST of Core is going for BIP148/BIP149 that requires NO signalling for SegWit at all - the 95% activation has long been discarded by MOST of Core. https://en.bitcoin.it/wiki/Segwit_support Hypocrites all over the place ... So your now predicting the future also? How did you manage to determine that "since 20% of the hash rate won't be support BIP 91" ... There may be forks since 20% of the hash rate won't be support BIP 91 and thus will likely not be signalling bit 1 for segwit. With some luck and spy mining, forks could be made from miners extending a chain off of a block which does not signal bit 1. However Bitcoin Core will allow you to choose the chain to use (via the invalidateblock RPC command) and any of the forks will be valid to Core. ... BIP91 is built off Bitcoin Core code - so even BIP91 will "allow you to choose the chain to use" since that function is old. Title: Re: About the "Unknown block versions being mined!" warning Post by: JayJuanGee on July 18, 2017, 12:57:31 PM So what day should we stop buying or selling btc?And for how long? I had been considering this too, and I thought that between about July 30 until mid to late August, but we have to continue to monitor whether it might be o.k. to continue with our trades and transfers. I imagine that there are members who have much more solid understandings than me. Title: Re: About the "Unknown block versions being mined!" warning Post by: Meuh6879 on July 18, 2017, 01:18:32 PM It seems a little bazaar that achow101 is complaining about an 80% acceptance for SegWit with BIP91 when MOST of Core is going for BIP148/BIP149 that requires NO signalling for SegWit at all - the 95% activation has long been discarded by MOST of Core. https://en.bitcoin.it/wiki/Segwit_support Hypocrites all over the place ... So your now predicting the future also? How did you manage to determine that "since 20% of the hash rate won't be support BIP 91" ... There may be forks since 20% of the hash rate won't be support BIP 91 and thus will likely not be signalling bit 1 for segwit. With some luck and spy mining, forks could be made from miners extending a chain off of a block which does not signal bit 1. However Bitcoin Core will allow you to choose the chain to use (via the invalidateblock RPC command) and any of the forks will be valid to Core. ... BIP91 is built off Bitcoin Core code - so even BIP91 will "allow you to choose the chain to use" since that function is old. Perfect Explanation. Title: Re: About the "Unknown block versions being mined!" warning Post by: JayJuanGee on July 18, 2017, 01:47:44 PM O ok, well thought they were implementing a different version of segwit, seeing i read core's version needed 95% signaling for it to go active, but segwit2x is doing it with ~ 80%? Segwit2x is using BIP 91. BIP 91 specifies that 269 of the last 336 blocks (~80% of the last 336 blocks) must signal for BIP 91 on bit 4. Once there is enough signalling, it will be locked in for a short grace period of 336 blocks. Then it will activate. Once BIP 91 activates, all blocks must signal for segwit on bit 1. This means that segwit will then activate via its original deployment on bit 1. Segwit2x is not actually activating a different segwit, they are activating something else which will force the activation of segwit.Is there a website where we could watch specifically this dynamic? the 269 of the last 336 blocks? I have been watching coin.dance, but that is not very specific since it has one category that is looking at the past 144 blocks. https://coin.dance/blocks Title: Re: About the "Unknown block versions being mined!" warning Post by: xbiv2 on July 18, 2017, 01:52:40 PM Just setup bitcoin-core 2014 https://github.com/bitcoin/bitcoin/releases/tag/v0.9.1 while it is available for download.
Bitcoin-core developers not trustable anymore, too many political interests, money and speculations. Title: Re: About the "Unknown block versions being mined!" warning Post by: panju1 on July 18, 2017, 02:07:12 PM It is a relief to know that this message can be safely ignored. Too much FUD is going around these days.
People tend to try and exploit the panic around the hard fork. Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 18, 2017, 05:20:28 PM It seems a little bazaar that achow101 is complaining about an 80% acceptance for SegWit with BIP91 Where am I complaining about the 80% activation threshold? The purpose of this thread is to inform people about the warning that they will see in Core, not complaining about BIP 91.when MOST of Core is going for BIP148/BIP149 that requires NO signalling for SegWit at all - the 95% activation has long been discarded by MOST of Core. The table does not explain any nuance and conditions under which people find BIPs 148 or 149 as preferred.https://en.bitcoin.it/wiki/Segwit_support If the majority of Core actually supported BIPs 148 and 149, then BIP 148 support would have been merged into Core, but it has not. BIP91 is built off Bitcoin Core code - so even BIP91 will "allow you to choose the chain to use" since that function is old. btc1 is the client, not BIP 91. BIP 91 is the proposal. Anyways, by Core, I mean any derivative of Core.Title: Re: About the "Unknown block versions being mined!" warning Post by: Meuh6879 on July 18, 2017, 05:25:15 PM If the majority of Core actually supported BIPs 148 and 149, then BIP 148 support would have been merged into Core, but it has not. BIP148 have been introduce to late to be accepted with simple developper time line (min. 3 months, better = 6 months). BIP149 will be merged depend of what append on november (and before ...). Developpers are agree with the UASF when MASF fail. Title: Re: About the "Unknown block versions being mined!" warning Post by: NLNico on July 19, 2017, 04:27:06 AM Is there a website where we could watch specifically this dynamic? the 269 of the last 336 blocks? Yes, don't use coin.dance, use https://www.xbt.eu instead. It is not "last 336 blocks", but a "336 blocks lock-in period", if we don't succeed in these 336 blocks, we have to wait for them to finish and try again next 336 blocks, etc. Title: Re: About the "Unknown block versions being mined!" warning Post by: kano on July 19, 2017, 07:07:01 AM ... So you're somehow saying that when the majority of core, themselves, puts there name down there for BIP148 or BIP149 saying either:when MOST of Core is going for BIP148/BIP149 that requires NO signalling for SegWit at all - the 95% activation has long been discarded by MOST of Core. The table does not explain any nuance and conditions under which people find BIPs 148 or 149 as preferred.https://en.bitcoin.it/wiki/Segwit_support If the majority of Core actually supported BIPs 148 and 149, then BIP 148 support would have been merged into Core, but it has not. ... "Acceptable" it is a workable solution "Prefer" it is what he would choose if it was only up to him and no outside influences They are somehow NOT claiming that they are happy with the NO signalling in BIP148/BIP149? Yet 80% signalling for BIP91 is somehow considered unacceptable? Seriously are you that confused about the meaning of written English? Or are you just brainwashed by Core propaganda? Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 19, 2017, 07:20:45 AM So you're somehow saying that when the majority of core, themselves, puts there name down there for BIP148 or BIP149 saying either: You are completely missing the nuance. Very few of the Core developers have said that they support BIPs 148/149 with the current political situation. Re-read what those statements say: "Prefer" it is what he would choose if it was only up to him and no outside influences. That means that if BIP 148/149 existed in a vacuum with no outside influence (e.g. from miners) and everyone went along with it, they would prefer that as it is an activation via flag day. Are you seriously that confused about the meaning of written English? Are you seriously misconstruing "prefer" and "acceptable" as meaning "want it now as it is now" even when the definition on the page says otherwise?"Acceptable" it is a workable solution "Prefer" it is what he would choose if it was only up to him and no outside influences They are somehow NOT claiming that they are happy with the NO signalling in BIP148/BIP149? Yet 80% signalling for BIP91 is somehow considered unacceptable? Since BIP 148/149 do not exist in a vacuum and they are not the proposals accepted by everyone, nearly all Core developers do not endorse it. There have been three attempts to merge BIP 148 into Core, and all of them have been rejected by the very same people you claim are endorsing BIP 148. Those Core developers are not saying that they are happy with BIP 148/149 as they are now, only that if those were the only two proposals and existed in a vacuum and without any contentiousness that they would then support them. Title: Re: About the "Unknown block versions being mined!" warning Post by: kano on July 19, 2017, 08:11:24 AM So you're somehow saying that when the majority of core, themselves, puts there name down there for BIP148 or BIP149 saying either: You are completely missing the nuance. Very few of the Core developers have said that they support BIPs 148/149 with the current political situation. Re-read what those statements say: "Prefer" it is what he would choose if it was only up to him and no outside influences. That means that if BIP 148/149 existed in a vacuum with no outside influence (e.g. from miners) and everyone went along with it, they would prefer that as it is an activation via flag day. Are you seriously that confused about the meaning of written English? Are you seriously misconstruing "prefer" and "acceptable" as meaning "want it now as it is now" even when the definition on the page says otherwise?"Acceptable" it is a workable solution "Prefer" it is what he would choose if it was only up to him and no outside influences They are somehow NOT claiming that they are happy with the NO signalling in BIP148/BIP149? Yet 80% signalling for BIP91 is somehow considered unacceptable? Since BIP 148/149 do not exist in a vacuum and they are not the proposals accepted by everyone, nearly all Core developers do not endorse it. There have been three attempts to merge BIP 148 into Core, and all of them have been rejected by the very same people you claim are endorsing BIP 148. Those Core developers are not saying that they are happy with BIP 148/149 as they are now, only that if those were the only two proposals and existed in a vacuum and without any contentiousness that they would then support them. It's all pointless in a vacuum not relevant to any reality? OK get someone to delete it since there's no point to it ... ... yet you still seem to have skipped over: "Acceptable" it is a workable solution in your reply ... ... ... ... Title: Re: About the "Unknown block versions being mined!" warning Post by: Xester on July 19, 2017, 08:14:43 AM If you are using Bitcoin Core and derivative software, then you may have noticed that there is now a warning that states: Quote Warning: Unknown block versions being mined! It's possible unknown rules are in effect This warning will appear at the top of the Bitcoin Core GUI and reported in the errors or warnings field of the getinfo, getnetworkinfo, and getmininginfo RPC commands. This warning is triggered when more than 50 of the last 100 blocks have a version number that Bitcoin Core does not expect. Currently that is being triggered by miners mining for BIP 91 (aka the first half of segwit2x). These miners are setting bit 4 of the block version field, and Bitcoin Core does not expect this to be set. The version numbers that Bitcoin Core expects are 0x20000000 (536870912) and 0x20000002 (536870914). The unexpected version numbers currently are 0x20000012 (536870930) and 0x20000010 (536870928). Currently this warning is benign as there is no fork and no new network rules have activated. Your coins are not at risk. I thought we will be in trouble again. I read your post and I thought that another problem has risen that will again cause bitcoin to fall in price. But when I finished your comment and I read the line " your coins are not at risk" my mind became at ease again. I just hope that the core developers will also agree to BIP 91 so that there will be no more bitcoin split that will occur in the coming days. Title: Re: About the "Unknown block versions being mined!" warning Post by: B3dr0ck on July 19, 2017, 06:35:36 PM I see this error as well - that is why I'm on this thread, reading through it ....
I'm trying to reconcile this thread with Coinbase's recent email. Are we talking about here the User Activated Soft Fork (UASF) that Coinbase is referring to? Coinbase also refers to User Activated Hard Fork (UAHF) that is scheduled for Aug, 1st. They are not supporting this fork. This error is related to the UASF - which does not require a software upgrade on wallets of core 14+ (or some 13s versions), and Coinbase is supporting? Title: Re: About the "Unknown block versions being mined!" warning Post by: tspacepilot on July 19, 2017, 07:01:13 PM I see this error as well - that is why I'm on this thread, reading through it .... I'm trying to reconcile this thread with Coinbase's recent email. Are we talking about here the User Activated Soft Fork (UASF) that Coinbase is referring to? Coinbase also refers to User Activated Hard Fork (UAHF) that is scheduled for Aug, 1st. They are not supporting this fork. This error is related to the UASF - which does not require a software upgrade on wallets of core 14+ (or some 13s versions), and Coinbase is supporting? Is this coinbase message since we started seeing the BIP 91 signaling? What is coinbase saying in their message? Some of us on the thread aren't coinbase customers. Title: Re: About the "Unknown block versions being mined!" warning Post by: B3dr0ck on July 20, 2017, 05:52:57 AM I see this error as well - that is why I'm on this thread, reading through it .... I'm trying to reconcile this thread with Coinbase's recent email. Are we talking about here the User Activated Soft Fork (UASF) that Coinbase is referring to? Coinbase also refers to User Activated Hard Fork (UAHF) that is scheduled for Aug, 1st. They are not supporting this fork. This error is related to the UASF - which does not require a software upgrade on wallets of core 14+ (or some 13s versions), and Coinbase is supporting? Is this coinbase message since we started seeing the BIP 91 signaling? What is coinbase saying in their message? Some of us on the thread aren't coinbase customers. First I saw the email was yesterday. Here's the email: "The User Activated Hard Fork (UAHF) is a proposal to increase the Bitcoin block size scheduled to activate on August 1. The UAHF is incompatible with the current Bitcoin ruleset and will create a separate blockchain. Should UAHF activate on August 1, Coinbase will not support the new blockchain or its associated coin. The User Activated Soft Fork (UASF) is a proposal to adopt Segregated Witness on the Bitcoin blockchain and could result in network instability. It is scheduled to activate at the same time as the UAHF. To ensure the safety of customers funds, we will temporarily suspend bitcoin deposits, withdrawals, and buy/sell starting approximately 4 hours before activation of either fork." Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 20, 2017, 06:04:46 AM I see this error as well - that is why I'm on this thread, reading through it .... This thread is talking about neither of those things. BIP 91 is unrelated to UASF or UAHF. Neither the UASF or the UAHF will trigger the warning that you see here as they do not do miner signaling; rather they activate via flag day. However BIP 91 activates via miner signaling, so we get the warning here about that.I'm trying to reconcile this thread with Coinbase's recent email. Are we talking about here the User Activated Soft Fork (UASF) that Coinbase is referring to? Coinbase also refers to User Activated Hard Fork (UAHF) that is scheduled for Aug, 1st. They are not supporting this fork. This error is related to the UASF - which does not require a software upgrade on wallets of core 14+ (or some 13s versions), and Coinbase is supporting? Title: Re: About the "Unknown block versions being mined!" warning Post by: yg10 on July 20, 2017, 07:50:49 AM Hmm..
I started to get this message @ 40 of 100 blocks. Code: 2017-07-15 18:54:41 UpdateTip: 47 of last 100 blocks have unexpected version and the number of such blocks is growing: Code: 2017-07-20 07:07:26 UpdateTip: 94 of last 100 blocks have unexpected version Title: Re: About the "Unknown block versions being mined!" warning Post by: Meuh6879 on July 20, 2017, 08:51:13 AM You has an old Bitcoin Core (without Segwit recognize).
Only 80 blocks are with an exotic version ... https://www.xbt.eu/ (144 Blocks) http://imagizer.imageshack.us/a/img924/8840/iqunLG.png Code: 2017-07-20 08:45:34 UpdateTip: new best=0000000000000000007a3eed0bbf2bc517760e19aedc235fca12738ea089f2bd height=476675 version=0x20000002 log2_work=86.79112 tx=240559896 date='2017-07-20 08:42:36' progress=0.999998 cache=215.0MiB(103467tx) warning='83 of last 100 blocks have unexpected version' Title: Re: About the "Unknown block versions being mined!" warning Post by: yg10 on July 20, 2017, 10:16:46 AM You has an old Bitcoin Core (without Segwit recognize). Only 80 blocks are with an exotic version ... https://www.xbt.eu/ (144 Blocks) http://imagize[Suspicious link removed]ageshack.us/a/img924/8840/iqunLG.png Code: 2017-07-20 08:45:34 UpdateTip: new best=0000000000000000007a3eed0bbf2bc517760e19aedc235fca12738ea089f2bd height=476675 version=0x20000002 log2_work=86.79112 tx=240559896 date='2017-07-20 08:42:36' progress=0.999998 cache=215.0MiB(103467tx) warning='83 of last 100 blocks have unexpected version' Yes. I am running v0.12.1.0. Compiling 0.14.2 on FreeBSD is a headache. Title: Re: About the "Unknown block versions being mined!" warning Post by: benjamin07 on July 20, 2017, 01:55:08 PM ty achow101 for the explanation. Very concise, complete and straight to the point explaining the Warning message. You should probably append with: Minimum IQ>0 required lol
Title: Re: About the "Unknown block versions being mined!" warning Post by: tspacepilot on July 20, 2017, 04:28:06 PM Anyone know what that small percentage of blocks signaling with a 30000000 is about? I saw one or two blocks with that version number yesterday and I couldn't find any BIPs or docs referencing that number.
Title: Re: About the "Unknown block versions being mined!" warning Post by: xyzzy099 on July 20, 2017, 04:39:59 PM Anyone know what that small percentage of blocks signaling with a 30000000 is about? I saw one or two blocks with that version number yesterday and I couldn't find any BIPs or docs referencing that number. "Bitcoin Classic" nodes mine blocks with version 0x30000000 by default, if I am not mistaken. Title: Re: About the "Unknown block versions being mined!" warning Post by: abilger on July 21, 2017, 09:00:06 AM The following sentences are written at xbt.eu
BIP91 LOCKED-IN 292 blocks until rejecting non-SegWit blocks. It seems that many pools are supporting BIP91. https://i.imgur.com/otnoXUe.jpg Title: Re: About the "Unknown block versions being mined!" warning Post by: Bitcoinero_GB on July 21, 2017, 04:50:28 PM Ok, We have BIP91 locked in.
The message of the Core shouldn't be dangeous. But my Core wallet is not working well. The syncro works fine. But when send a payment there is no connection, and the movement is not broadcasting to the network. What I'm doing wrong? I was thinking that Core users donīt need to change anything (using 0.14.2) Title: Re: About the "Unknown block versions being mined!" warning Post by: Meuh6879 on July 21, 2017, 04:54:52 PM You can not emit with 0-fee ...
https://bitcoincore.org/en/releases/0.14.0/ Quote Minimum Fee Rate Policies Since the changes in 0.12 to automatically limit the size of the mempool and improve the performance of block creation in mining code it has not been important for relay nodes or miners to set -minrelaytxfee. With this release the following concepts that were tied to this option have been separated out: - incremental relay fee used for calculating BIP 125 replacement and mempool limiting. (1000 satoshis/kB) - calculation of threshold for a dust output. (effectively 3 * 1000 satoshis/kB) - minimum fee rate of a package of transactions to be included in a block created by the mining code. If miners wish to set this minimum they can use the new -blockmintxfee option. (defaults to 1000 satoshis/kB) standard transaction weight 224B ... 0,00005 BTC of fees (25sat/B). and now, we have 13600 transactions in mempool (65Mb). Title: Re: About the "Unknown block versions being mined!" warning Post by: xbiv2 on July 21, 2017, 05:48:15 PM The following sentences are written at xbt.eu Fake newsBIP91 LOCKED-IN 292 blocks until rejecting non-SegWit blocks. It seems that many pools are supporting BIP91. https://blockchain.info/charts/bip-9-segwit https://blockchain.info/charts/bitcoin-unlimited-share Title: Re: About the "Unknown block versions being mined!" warning Post by: tspacepilot on July 21, 2017, 07:03:49 PM Fake news https://blockchain.info/charts/bip-9-segwit I guess the confusion here comes from the fact that you can signal BIP9 without signaling SegWit. BIP9 signals on bit 4 and we definitely have like 80ish% of blocks in the last day or so signaling on bit 4. SegWit readiness is signaled on bit 1 and I think that's what bc.i is tracking there. As far as I know, in a couple hundred more blocks, the miners who signaled BIP9 are supposed to start rejecting blocks that don't signal segwit on bit 1. We'll have to see whether all the folks who signaled BIP9 start putting bit1 and whether or not those who signaled BIP9 (bit4) actually do start orphaning blocks that don't signal bit1. Disclaimer: this topic is confusing, I may be wrong. EDIT: see next post by achow101: everywhere above that I said BIP9, I should have said BIP91. Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 22, 2017, 01:21:24 AM Fake news https://blockchain.info/charts/bip-9-segwit I guess the confusion here comes from the fact that you can signal BIP9 without signaling SegWit. BIP9 signals on bit 4 and we definitely have like 80ish% of blocks in the last day or so signaling on bit 4. SegWit readiness is signaled on bit 1 and I think that's what bc.i is tracking there. As far as I know, in a couple hundred more blocks, the miners who signaled BIP9 are supposed to start rejecting blocks that don't signal segwit on bit 1. We'll have to see whether all the folks who signaled BIP9 start putting bit1 and whether or not those who signaled BIP9 (bit4) actually do start orphaning blocks that don't signal bit1. Disclaimer: this topic is confusing, I may be wrong. Title: Re: About the "Unknown block versions being mined!" warning Post by: junan1 on July 22, 2017, 03:12:04 AM Fake news https://blockchain.info/charts/bip-9-segwit I guess the confusion here comes from the fact that you can signal BIP9 without signaling SegWit. BIP9 signals on bit 4 and we definitely have like 80ish% of blocks in the last day or so signaling on bit 4. SegWit readiness is signaled on bit 1 and I think that's what bc.i is tracking there. As far as I know, in a couple hundred more blocks, the miners who signaled BIP9 are supposed to start rejecting blocks that don't signal segwit on bit 1. We'll have to see whether all the folks who signaled BIP9 start putting bit1 and whether or not those who signaled BIP9 (bit4) actually do start orphaning blocks that don't signal bit1. Disclaimer: this topic is confusing, I may be wrong.
By modifying the version field in the block header, miners can "signal" their support for any combination of deployments. Bit 1 of the version field corresponds to SegWit and bit 4 corresponds to SegSignal. https://blockchain.info/charts/bip-9-segwit (https://blockchain.info/charts/bip-9-segwit) charts the signalling of SegWit (bit 1) where each datapoint is in fact the average signalling rate of the prior 2016 blocks (~ 2 weeks). However, as you rightly observe, there has been a recent increase in SegWit signalling. Of the last 144 blocks (~ 1 day), 131 have signaled for SegWit (~ 91%). If the 2016-block moving average chart is at 95% or higher at a difficulty change then SegWit will "lock in". SegSignal is already locked in and all nodes following SegSignal will consider invalid any blocks at height 477120 or greater (~ 2017-07-23, 8:00am UTC) (edit) which do not signal SegWit. Note again that Bitcoin Core does not include code for this deployment (hence the warnings) and so Bitcoin Core nodes will not reject blocks as SegSignal requires. Title: Re: About the "Unknown block versions being mined!" warning Post by: tspacepilot on July 22, 2017, 06:38:21 AM
By modifying the version field in the block header, miners can "signal" their support for any combination of deployments. Bit 1 of the version field corresponds to SegWit and bit 4 corresponds to SegSignal. https://blockchain.info/charts/bip-9-segwit (https://blockchain.info/charts/bip-9-segwit) charts the signalling of SegWit (bit 1) where each datapoint is in fact the average signalling rate of the prior 2016 blocks (~ 2 weeks). However, as you rightly observe, there has been a recent increase in SegWit signalling. Of the last 144 blocks (~ 1 day), 131 have signaled for SegWit (~ 91%). If the 2016-block moving average chart is at 95% or higher at a difficulty change then SegWit will "lock in". Quote SegSignal is already locked in and all nodes following SegSignal will consider invalid any blocks at height 477120 or greater (~ 2017-07-23, 8:00am UTC). Note again that Bitcoin Core does not include code for this deployment (hence the warnings) and so Bitcoin Core will not reject blocks as SegSignal requires. I understand that it's also a theoretical possibility that those who are currently sending SegSignal may not actually follow through and orphan non-segwit blocks. But I understand that we expect them to do so.Title: Re: About the "Unknown block versions being mined!" warning Post by: junan1 on July 22, 2017, 08:35:21 AM
By modifying the version field in the block header, miners can "signal" their support for any combination of deployments. Bit 1 of the version field corresponds to SegWit and bit 4 corresponds to SegSignal. https://blockchain.info/charts/bip-9-segwit (https://blockchain.info/charts/bip-9-segwit) charts the signalling of SegWit (bit 1) where each datapoint is in fact the average signalling rate of the prior 2016 blocks (~ 2 weeks). However, as you rightly observe, there has been a recent increase in SegWit signalling. Of the last 144 blocks (~ 1 day), 131 have signaled for SegWit (~ 91%). If the 2016-block moving average chart is at 95% or higher at a difficulty change then SegWit will "lock in". Thank you tspacepilot. Note: "segsignal" is the name given to this deployment by the author of BIP 91, James Hilliard. Quote SegSignal is already locked in and all nodes following SegSignal will consider invalid any blocks at height 477120 or greater (~ 2017-07-23, 8:00am UTC). Note again that Bitcoin Core does not include code for this deployment (hence the warnings) and so Bitcoin Core will not reject blocks as SegSignal requires. I understand that it's also a theoretical possibility that those who are currently sending SegSignal may not actually follow through and orphan non-segwit blocks. But I understand that we expect them to do so.Yes, I wasn't too clear here. All nodes (miners or otherwise) following the rules of BIP 91 (adopting SegSignal) will consider invalid any blocks which do not signal SegWit when this deployment becomes active. However, there's nothing preventing nodes from giving up on SegSignal at any time. Additionally, there's nothing preventing miners from setting bit 4 whether or not they intend to adopt SegSignal. Technically, the same applies to SegWit itself. Title: Re: About the "Unknown block versions being mined!" warning Post by: Meuh6879 on July 22, 2017, 11:26:17 AM Title: Re: About the "Unknown block versions being mined!" warning Post by: Bitcoinero_GB on July 22, 2017, 11:28:17 AM Ok, We have BIP91 locked in. The message of the Core shouldn't be dangeous. But my Core wallet is not working well. The syncro works fine. But when send a payment there is no connection, and the movement is not broadcasting to the network. What I'm doing wrong? I was thinking that Core users donīt need to change anything (using 0.14.2) But Why I cannot send funds with bitcoin qt wallet? Title: Re: About the "Unknown block versions being mined!" warning Post by: achow101 on July 22, 2017, 04:29:36 PM Ok, We have BIP91 locked in. The message of the Core shouldn't be dangeous. But my Core wallet is not working well. The syncro works fine. But when send a payment there is no connection, and the movement is not broadcasting to the network. What I'm doing wrong? I was thinking that Core users donīt need to change anything (using 0.14.2) But Why I cannot send funds with bitcoin qt wallet? Title: Re: About the "Unknown block versions being mined!" warning Post by: xbiv2 on July 22, 2017, 04:44:23 PM Not trust to bitcoin-core developers and use bitcoin-core of 2014 https://github.com/bitcoin/bitcoin/releases/tag/v0.9.1
"Unknown block versions being mined!" warning have only in new versions Title: Re: About the "Unknown block versions being mined!" warning Post by: simbo on July 22, 2017, 05:53:57 PM achow, thank you for the explanation! I was wondering, what this means
Title: Re: About the "Unknown block versions being mined!" warning Post by: Crystaleyes on August 25, 2017, 11:41:02 AM So, it's the 25th August and this message just popped up in my Bitcoin Core.
Is it still benign? |
![http://imagize[Suspicious link removed]ageshack.us/a/img924/8840/iqunLG.png](http://imagize[Suspicious link removed]ageshack.us/a/img924/8840/iqunLG.png){kind=link}
