|
Title: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 04:24:28 PM And it's begin ... at the end of every lines = 23 of last 100 blocks have unexpected version
Code: 2017-07-17 15:37:02 UpdateTip: new best=000000000000000000eac4304c025e2e0edfab5ac1f95d92cc17b11dd1da4e6e height=476233 version=0x20000010 log2_work=86.774567 tx=239865845 date='2017-07-17 15:33:54' progress=0.999997 cache=12.8MiB(7346tx) warning='23 of last 100 blocks have unexpected version' http://imagizer.imageshack.us/a/img924/2964/VoGuD8.gif Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 04:43:51 PM Always in progress ... 35 of last 100 blocks have unexpected version
Code: 2017-07-17 16:39:04 UpdateTip: new best=000000000000000000a0f7de1b907655d02b3341606873c59ac89cc56cc8906e height=476242 version=0x20000012 log2_work=86.774906 tx=239880369 date='2017-07-17 16:36:26' progress=0.999998 cache=115.6MiB(65969tx) warning='31 of last 100 blocks have unexpected version' http://imagizer.imageshack.us/a/img923/3550/qogM1F.gif Title: Re: FORK in progress ... now ! Post by: Variogam on July 17, 2017, 04:57:24 PM You are expected to update to btc1 client, so do what your log says if you want your node to be compatible with Bitcoin ;)
Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 04:58:27 PM http://imagizer.imageshack.us/a/img922/9351/JDpbWs.gif Good joke, bro ...
Title: Re: FORK in progress ... now ! Post by: cr1776 on July 17, 2017, 04:58:48 PM It just means some miners have mined blocks with a version number that is unknown to whatever software you are using - presumably Bitcoin Core.
Not a fork, just FUD? Title: Re: FORK in progress ... now ! Post by: Minecache on July 17, 2017, 05:03:25 PM The FUD is strong with this one.
Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 05:10:44 PM At 50 unexpected block version, the Bitcoin Core Client ask to the owner to (search for an) upgrade solution at every startup ... that why it's dangerous (or not if you run an old version of Bitcoin Core).
Title: Re: FORK in progress ... now ! Post by: hv_ on July 17, 2017, 05:23:32 PM Do you see blocks from F2Pool?
Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 05:24:57 PM https://insight.bitpay.com/blocks
https://tradeblock.com/bitcoin/ (tip on table) Code: 2017-07-17 17:24:47 UpdateTip: new best=000000000000000000cbc68c7c20bc68167de6a33d1316252792450a27adfce5 height=476248 version=0x20000010 log2_work=86.775132 tx=239890960 date='2017-07-17 17:21:07' progress=0.999997 cache=160.4MiB(98248tx) warning='36 of last 100 blocks have unexpected version' 36% ... :P Title: Re: FORK in progress ... now ! Post by: stompix on July 17, 2017, 06:02:30 PM Can we have a title change?
Like FUD in progress? 37% > 45% > 78% FUD I'm bored , it's Monday so I decided to troll the forum? Let's me show you some cool gifs? Choose one Title: Re: FORK in progress ... now ! Post by: crazyivan on July 17, 2017, 06:04:37 PM Pls tell me you have actually purchased your legendary account, pls let me have faith in people.....
Title: Re: FORK in progress ... now ! Post by: stompix on July 17, 2017, 06:08:21 PM Pls tell me you have actually purchased your legendary account, pls let me have faith in people..... It will take me probably less than 15 minute to give you 10 quotes from "legendary" members that will leave you listening to faithless for the rest of your life. And you'll get "insomania" also :))))))) Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 07:35:59 PM Code: 2017-07-17 19:36:18 UpdateTip: new best=000000000000000000551076fe4e06f0f58ed9c0c445f31b379a9d8444fba1ed height=476264 version=0x20000010 log2_work=86.775734 tx=239919333 date='2017-07-17 19:33:46' progress=0.999998 cache=155.2MiB(75736tx) warning='47 of last 100 blocks have unexpected version' 47% of the total Hashrate mining power build blocks with an other version number. It's more clear like that ... ? http://imagizer.imageshack.us/a/img922/5761/OhNT1z.gif They need 2 blocks to evolve at +1% every time now. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 07:38:01 PM Pls tell me you have actually purchased your legendary account, pls let me have faith in people..... remember when blockchain.info display a marvelous 57% hashrate on 1 pool ... ? no ? ::) You're too young. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 07:47:29 PM Code: 2017-07-17 19:48:22 UpdateTip: new best=0000000000000000013ba01219bc01f3508f92d163bd3ed2232999fb5f7c0da0 height=476266 version=0x20000000 log2_work=86.77581 tx=239923846 date='2017-07-17 19:46:07' progress=0.999998 cache=168.3MiB(83054tx) warning='48 of last 100 blocks have unexpected version' 49%. News : http://www.coindesk.com/bip91-begins-bitcoins-miners-signal-segwit2x-scaling-proposal-early/ Title: Re: FORK in progress ... now ! Post by: Snorek on July 17, 2017, 08:00:27 PM News : http://www.coindesk.com/bip91-begins-bitcoins-miners-signal-segwit2x-scaling-proposal-early/ Also I love this little disclaimer from Coindesk on how CoinDesk is always a subsidiary of something, someone, whatever and they are linked to everything in cryptocurrency ecosystem. For example, they're part of Digital Currency Group, which helped organize the Segwit2x agreement. Sick. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 17, 2017, 08:26:08 PM 51% of the hashrate mining power is, now, allocated to a new version of blocks.
Code: 2017-07-17 20:24:49 UpdateTip: new best=0000000000000000007df6d6851fd8b104b02ed9173cb14202aee5fa66c96443 height=476271 version=0x20000010 log2_work=86.775998 tx=239933248 date='2017-07-17 20:22:23' progress=0.999998 cache=86.8MiB(19448tx) warning='51 of last 100 blocks have unexpected version' Now, Pool mining software (like P2Pool server) and Bitcoin Core demand to the owner to upgrade the software (if needed). It's an automated alert when more than 50% of the last 100 blocks are mined with an other version of Block. Be prepared to the newbies questions when they start her wallets ... :-* Code: 2017-07-17 20:38:41 UpdateTip: new best=00000000000000000151077e3d4e0601354286a3cbe4d67dedde7d26e1b317d3 height=476272 version=0x20000010 log2_work=86.776035 tx=239935204 date='2017-07-17 20:35:40' progress=0.999998 cache=21.2MiB(7067tx) warning='52 of last 100 blocks have unexpected version' 52% Title: Re: FORK in progress ... now ! Post by: Looarn on July 18, 2017, 06:21:36 AM Any news of BitFury ?
The only hashpower to under balance it no ? BTC.COM was neutral so far, they switched to SegWit2x (NYA) yesterday, so now it's all BitMain plus allies minus Bitfury hashpower, so more than 50%. :( Title: Re: FORK in progress ... now ! Post by: qiwoman2 on July 18, 2017, 06:25:29 AM Even if there was a Bitcoin hard fork it wouldn't phase me. There might be just a little price instability in the markets but then having two Bitcoin Coins would make the developers and miners take more notice and work harder for the greater good and get off their high horses. ;D ;D ;D
Title: Re: FORK in progress ... now ! Post by: blo8i on July 18, 2017, 06:39:51 AM Is this topic a joke? I read some replies here and as I am seeing this is a spam topic.
Why did you chose this name? Fork? What? ..... Are you serious? Title: Re: FORK in progress ... now ! Post by: pooya87 on July 18, 2017, 06:51:26 AM Is this topic a joke? I read some replies here and as I am seeing this is a spam topic. Why did you chose this name? Fork? What? ..... Are you serious? this is the first of many FUD to come. as the price rises in a sharp move, people get desperate and make silly topics like this. and OP is not a newbie to say he didn't know... this is not a fork in progress and there is no reason for posting in red saying "unexpected version" without additional information with that silly "Mr Smith" meme. This is just his node being silly and not recognize BIP91 version bit signalling Segregated Witness. Title: Re: FORK in progress ... now ! Post by: DooMAD on July 18, 2017, 07:03:41 AM If anyone is still confused or alarmed by this rather dumb thread, one of the forum mods has posted a far more sensible one here to explain what's happening (https://bitcointalk.org/index.php?topic=2027513.0). It's not a cause for concern, with the possible exception that one might expect better behaviour from longstanding forum members. Stop scaring the newbies, Meuh6879.
See the sensible explanation below: 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. (bolded emphasis mine) Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 07:20:31 AM Stop scaring the newbies, Meuh6879. Stable at 61% of mining power. Code: 2017-07-18 07:02:09 UpdateTip: new best=000000000000000000fb89db8f91845067e0b5864e1620c7a0698c25ebb0e3bf height=476341 version=0x20000012 log2_work=86.778629 tx=240039240 date='2017-07-18 06:59:49' progress=0.999998 cache=154.2MiB(68076tx) warning='61 of last 100 blocks have unexpected version' If you don't recognize a threat, you have a problem ... not me. That's why BIP148 must stop this 61% mining power of no-standard blocks. This 61% don't mean that they "want" accept any Segwit of others "bitcoin core" policies. Segwit, it's this way, no an other magical vote on block version : http://bitcoin.sipa.be/versions.html http://imagizer.imageshack.us/a/img923/7900/KRnQB5.png Title: Re: FORK in progress ... now ! Post by: Looarn on July 18, 2017, 07:24:46 AM I just switch my miner to SlushPool, back on mining Version x20000002 (SegWit), and not this SegWitx2 New York Agreement bullshit.
61% OMG, where is BitFury ? :S Title: Re: FORK in progress ... now ! Post by: NeuroticFish on July 18, 2017, 07:27:23 AM FUD or lack of knowledge? Hard to tell.
It's not a fork. All this is already explained here: https://bitcointalk.org/index.php?topic=2027513 If this is not intended as FUD, then OP should lock this thread and redirect to the explanation thread. Title: Re: FORK in progress ... now ! Post by: Minecache on July 18, 2017, 07:28:41 AM If anyone is still confused or alarmed by this rather dumb thread, one of the forum mods has posted a far more sensible one here to explain what's happening (https://bitcointalk.org/index.php?topic=2027513.0). It's not a cause for concern, with the possible exception that one might expect better behaviour from longstanding forum members. Stop scaring the newbies, Meuh6879. See the sensible explanation below: 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. (bolded emphasis mine) Thread should be locked and the fudder who started it banned. Title: Re: FORK in progress ... now ! Post by: DooMAD on July 18, 2017, 07:34:05 AM Stop scaring the newbies, Meuh6879. If you don't recognize a threat, you have a problem ... not me. That's why BIP148 must stop this 61% mining power of no-standard blocks. Segwit, it's this way, no an other magical vote on block version : http://bitcoin.sipa.be/versions.html I see, you're another one of those people who think miners and other users have to blindly follow along and can't make their own decisions about the software they choose to run. I assure you, it's definitely you who has a problem. Why do you think Bitcoin is some form of dictatorship? Why do you honestly believe developers get to make every single last decision and no one has any option but to obey? It's not a "magical vote" at all, it's called consensus and I don't know why you seem to despise it so much if you've decided to stick around for this long. It's an integral part of how Bitcoin works. If you don't like how Bitcoin works, I understand that bankster crapcoin Ripple functions in a way you'd find more favourable. Devs make all the decisions there and no one has any other option but to run that code and only that code. Maybe go play with that and leave the people who like freedom alone. Both UASF and SegWit2x have every right to do what they're doing. You run whatever code you want, they can run whatever code they want. No one is putting a gun to your head and forcing you to stay if you can't deal with other people having a different view to the one you're desperately clinging onto. Title: Re: FORK in progress ... now ! Post by: Looarn on July 18, 2017, 08:15:44 AM Stop scaring the newbies, Meuh6879. Stable at 61% of mining power. Code: 2017-07-18 07:02:09 UpdateTip: new best=000000000000000000fb89db8f91845067e0b5864e1620c7a0698c25ebb0e3bf height=476341 version=0x20000012 log2_work=86.778629 tx=240039240 date='2017-07-18 06:59:49' progress=0.999998 cache=154.2MiB(68076tx) warning='61 of last 100 blocks have unexpected version' If you don't recognize a threat, you have a problem ... not me. That's why BIP148 must stop this 61% mining power of no-standard blocks. Segwit, it's this way, no an other magical vote on block version : http://bitcoin.sipa.be/versions.html I see, you're another one of those people who think miners and other users have to blindly follow along and can't make their own decisions about the software they choose to run. I assure you, it's definitely you who has a problem. Why do you think Bitcoin is some form of dictatorship? Why do you honestly believe developers get to make every single last decision and no one has any option but to obey? It's not a "magical vote" at all, it's called consensus and I don't know why you seem to despise it so much if you've decided to stick around for this long. It's an integral part of how Bitcoin works. If you don't like how Bitcoin works, I understand that bankster crapcoin Ripple functions in a way you'd find more favourable. Devs make all the decisions there and no one has any other option but to run that code and only that code. Maybe go play with that and leave the people who like freedom alone. Both UASF and SegWit2x have every right to do what they're doing. You run whatever code you want, they can run whatever code they want. No one is putting a gun to your head and forcing you to stay if you can't deal with other people having a different view to the one you're desperately clinging onto. Looks like you rewrite the history. :) First the BU side refuse SegWit activation, by supporting BU, then they push for block expantion anyway if SegWit activate their way (i.e. BIP91). So in other word, they are OK for SegWit but only if they activate it with some other stuff in it (2x and some other easter eggs). If BitMain was an honest supporter of SegWit then we would have a nice BIP9 activation with 95% consensus. Please stop shitting yourself, and I invite you to read all the BIP91 proposal, and what's really inside. EDIT : And you should also have notice that the Old BU team is signaling 0x20000010 version so withoutSegWit readyness. ;) (Not the case of BitFury which signaling : 0x20000012 so readyness for BIP91 and SegWit ) Title: Re: FORK in progress ... now ! Post by: Looarn on July 18, 2017, 10:37:14 AM So yes I believe also that after SegWit lock-in, we will see the old BU team go HardFork signaling non SegWit blocks as they are currently.
Wait and see. Anyway, I mine 0x20000002 with my little hash power. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 12:35:26 PM Code: 2017-07-18 12:27:32 UpdateTip: new best=0000000000000000003b2a27d6ec46ca572cd7ae8f403a2c148cb22b6b769265 height=476378 version=0x20000010 log2_work=86.780018 tx=240096566 date='2017-07-18 12:24:36' progress=0.999998 cache=132.4MiB(49371tx) warning='60 of last 100 blocks have unexpected version' Stable between 60 & 61%. Can make the 51% attack (refuse segwit for example) but not the 2Mb block size (97% nodes refuse this) ... :P So BIP148 is needed to force this mining sector (the 61% in less than 12h from monday to thuesday) to follow the rules of the SegWit signaling. :-\ Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 12:40:42 PM I see, you're another one of those people who think miners and other users have to blindly follow along and can't make their own decisions about the software they choose to run. I assure you, it's definitely you who has a problem. so, this day, we are : - a 61% of mining power (yes, all the mining power of the Bitcoin network) building blocks with a unknown version - a 39% of mining power (the "rest") that mine Regular Blocks (and perhaps SegWit blocks when the time commes). Yes, it's a problem for me. A BIG one. We have identified a mining sector that it can do an 51% attack if they want. Remember the 57% of a 1 pool in 2014-2015 ? No ? ::) Title: Re: FORK in progress ... now ! Post by: buwaytress on July 18, 2017, 12:57:49 PM Pls tell me you have actually purchased your legendary account, pls let me have faith in people..... It will take me probably less than 15 minute to give you 10 quotes from "legendary" members that will leave you listening to faithless for the rest of your life. And you'll get "insomania" also :))))))) I think I'm beginning to understand now what legendary comments can also mean. Perhaps it's time to recognise those who go beyond legendary, honouring their "epic" comments. *note to self* read the comments, not the member levels. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 12:57:53 PM I just switch my miner to SlushPool, back on mining Version x20000002 (SegWit), and not this SegWitx2 New York Agreement bullshit. Perfect quote. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 01:03:51 PM Both UASF and SegWit2x have every right to do what they're doing. You run whatever code you want, they can run whatever code they want. don't compare a UASF real modified & verified Bitcoin Core version only with a BIP0148 identified strategy ... and a dark version launched by a mining sector (with 61% of the mining power of the whole Bitcoin network). Segwit2x is not a BIP. BIP0091 is not a BIP recognize by Bitcoin Core (find BIP91 here ? https://bitcoincore.org/en/bips/ = NO). We have, now, a Ethereum Split possibility : ETH & ETC possibility. A tangible Fork possibility. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 01:54:21 PM Better article than Coindesk : http://bitcoinist.com/mining-pool-signal-bitcoin-whole/
Quote SegWit2x has been identified by Luke-Jr, amongst others, as essentially a power grab by large Bitcoin mining operations, primarily Bitmain, allowing them potential control of the whole Bitcoin network. “By promoting BIP91 and Segwit2x as an alternative to BIP148, what miners are really doing is another power grab to try to take back their veto, which has no purpose other than to be used by Bitmain to block the whole thing at the last minute…,” warns Luke-Jr. Title: Re: FORK in progress ... now ! Post by: BrewMaster on July 18, 2017, 02:01:34 PM Both UASF and SegWit2x have every right to do what they're doing. You run whatever code you want, they can run whatever code they want. don't compare a UASF real modified & verified Bitcoin Core version only with a BIP0148 identified strategy ... and a dark version launched by a mining sector (with 61% of the mining power of the whole Bitcoin network). Segwit2x is not a BIP. BIP0091 is not a BIP recognize by Bitcoin Core (find BIP91 here ? https://bitcoincore.org/en/bips/ = NO). We have, now, a Ethereum Split possibility : ETH & ETC possibility. A tangible Fork possibility. NO there will be NO split. stop spreading FUD BIP91 is not activating a weird unknown or new thing. the SegWit that will be activated via BIP91 will be the same SegWit that other BIPs you have in mind will activate. if you take time and read the BIP instead of spamming nonsense here you will understand that this BIP is only changing the variables needed fro activation like lowering the 95% to 80% for instance. Title: Re: FORK in progress ... now ! Post by: just_Alice on July 18, 2017, 02:03:28 PM But why the bitcoin price is rising then? No one is seeing the threat? Or maybe, just maybe, there is no threat at all? :)
Being not a big expert in the subject, I trust other people who are experts. And it looks like they are pretty optimistic at the moment. Title: Re: FORK in progress ... now ! Post by: Minecache on July 18, 2017, 02:04:02 PM Both UASF and SegWit2x have every right to do what they're doing. You run whatever code you want, they can run whatever code they want. don't compare a UASF real modified & verified Bitcoin Core version only with a BIP0148 identified strategy ... and a dark version launched by a mining sector (with 61% of the mining power of the whole Bitcoin network). Segwit2x is not a BIP. BIP0091 is not a BIP recognize by Bitcoin Core (find BIP91 here ? https://bitcoincore.org/en/bips/ = NO). We have, now, a Ethereum Split possibility : ETH & ETC possibility. A tangible Fork possibility. NO there will be NO split. stop spreading FUD BIP91 is not activating a weird unknown or new thing. the SegWit that will be activated via BIP91 will be the same SegWit that other BIPs you have in mind will activate. if you take time and read the BIP instead of spamming nonsense here you will understand that this BIP is only changing the variables needed fro activation like lowering the 95% to 80% for instance. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 03:05:37 PM if you take time and read the BIP instead of spamming nonsense ... BIP148 is not in Bitcoin Core. BIP91 is not in Bitcoin Core. SegWit only activate when Blocks have the good version integrated. Bitcoin Core (the 79% of the network) only recognize the BIP9 block version (2x....02, not 2x....10 and not 2x....12). Title: Re: FORK in progress ... now ! Post by: hv_ on July 18, 2017, 03:11:07 PM .. if there is about 90% miners in line - who cares ?
Title: Re: FORK in progress ... now ! Post by: pereira4 on July 18, 2017, 03:17:02 PM This could turn out to be ok as long as segwit2x manages to not crash during activation period which would be a massive disaster. Once segwit locks in and we avoid BIP148, then miners can go back to running core software and we will be safe until November when delusional hardforkers pretend to fork bitcoin again.
Title: Re: FORK in progress ... now ! Post by: naughty1 on July 18, 2017, 03:18:19 PM .. if there is about 90% miners in line - who cares ? Everyone is interested, look at the current bitcoin, it affects the entire virtual currency market, any change from it has a direct impact on all other currencies. So, people always care about it. Title: Re: FORK in progress ... now ! Post by: hv_ on July 18, 2017, 03:22:03 PM This could turn out to be ok as long as segwit2x manages to not crash during activation period which would be a massive disaster. Once segwit locks in and we avoid BIP148, then miners can go back to running core software and we will be safe until November when delusional hardforkers pretend to fork bitcoin again. Yeah - cool. Put war fork and war spoon down for a while and get us some pipe n beers. ;D Title: Re: FORK in progress ... now ! Post by: BrewMaster on July 18, 2017, 03:37:59 PM if you take time and read the BIP instead of spamming nonsense ... BIP148 is not in Bitcoin Core. BIP91 is not in Bitcoin Core. SegWit only activate when Blocks have the good version integrated. Bitcoin Core (the 79% of the network) only recognize the BIP9 block version (2x....02, not 2x....10 and not 2x....12). what the hell does any of these mean :D there is no Bitcoin Core, there is only Bitcoin. there is no Good Version, there is only block version. and these versions are used to "vote" exactly like last time for previous soft fork to activate P2SH (or you may know it as multisig). these versions show support for proposals. all these different BIP numbers are all activating the same thing. which is Segregated Witness none of them are different in the end result the only difference is in the route they take to reach that end result. bitcoin core is not the network, Bitcoin is the 100% of the network. what you see as bitcoin core and all the different names are only clients you can make one yourself too and call it Meuh. i am running my own client and call it CustomClient 0.9.0 :D none of them are different, they are all enforcing the same consensus rules we know as bitcoin. with little modification to other stuff. and this has nothing to do with activating SegWit! because core is compatible with SegWit! Title: Re: FORK in progress ... now ! Post by: Looarn on July 18, 2017, 03:42:11 PM So the question is : Is BTC1 compatible with SegWit ? Has he appear that BTC1 resolve the warning issue. ;)
Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 04:23:14 PM Once segwit locks in and we avoid BIP148, then miners can go back to running core software and we will be safe until November. Like this, it's ok. Title: Re: FORK in progress ... now ! Post by: chinapeople on July 18, 2017, 04:39:46 PM We will know it soon. I read 75% already favors
Title: Re: FORK in progress ... now ! Post by: DooMAD on July 18, 2017, 05:23:53 PM Both UASF and SegWit2x have every right to do what they're doing. You run whatever code you want, they can run whatever code they want. don't compare a UASF real modified & verified Bitcoin Core version only with a BIP0148 identified strategy ... and a dark version launched by a mining sector (with 61% of the mining power of the whole Bitcoin network). Segwit2x is not a BIP. BIP0091 is not a BIP recognize by Bitcoin Core (find BIP91 here ? https://bitcoincore.org/en/bips/ = NO). So. Much. Arrogance. First off, I'll compare whatever the hell I like, you oppressive little despot. Secondly, just because you think one of those two is "valid", it doesn't mean everyone else does and it certainly doesn't mean you get to tell people what they're doing isn't valid just because Core haven't given it their seal of approval (and for the record, I think you'll find some of the Core developers said UASF was "reckless", but I'm sure you're happy to gloss over that little fact). The difference between us, is that even though I'm not fond of UASF and find it to be a far more radical departure in terms of network governance than any hard fork could ever be, I fully defend their right to do what they're doing. For the record, I personally think what they're doing is stupid, but I'll defend to the death their right to do it in a permissionless system. You or I don't get to decide what is or isn't valid. Nor do any developers. That's not how this works at all. All we get to decide is what code we run and so does everyone else. You have no say whatsoever in what code other people choose to run. End of. If you can't handle that, tough shit. Permissionless. You can play totalitarian anywhere else you like, but that shit doesn't fly here. I see, you're another one of those people who think miners and other users have to blindly follow along and can't make their own decisions about the software they choose to run. I assure you, it's definitely you who has a problem. Yes, it's a problem for me. A BIG one. We have identified a mining sector that it can do an 51% attack if they want. Remember the 57% of a 1 pool in 2014-2015 ? No ? ::) Ah, yes, the old "everyone who disagrees with me must be under the direct influence of one person because my tinfoil hat says so and that means I can disregard their opinion" argument. Yeah, that's not getting boring at all. Again, are you really so arrogant as to think that every single miner supporting SegWit2x is some sort of mindless drone doing what the boss says? You sound like some demented religious fanatic. Cry moar. Title: Re: FORK in progress ... now ! Post by: Meuh6879 on July 18, 2017, 05:26:52 PM We will know it soon. I read 75% already favors Only 63% ;) Code: 2017-07-18 17:18:43 UpdateTip: new best=0000000000000000001def621c5bc90d1f0be86e2c84a955d8b0f94864090a1c height=476403 version=0x20000000 log2_work=86.780956 tx=240142243 date='2017-07-18 17:15:40' progress=0.999998 cache=162.4MiB(84920tx) warning='63 of last 100 blocks have unexpected version' Title: Re: FORK in progress ... now ! Post by: CryptoWiz420 on July 20, 2017, 01:47:54 AM And it's begin ... at the end of every lines = 23 of last 100 blocks have unexpected version Code: 2017-07-17 15:37:02 UpdateTip: new best=000000000000000000eac4304c025e2e0edfab5ac1f95d92cc17b11dd1da4e6e height=476233 version=0x20000010 log2_work=86.774567 tx=239865845 date='2017-07-17 15:33:54' progress=0.999997 cache=12.8MiB(7346tx) warning='23 of last 100 blocks have unexpected version' http://imagizer.imageshack.us/a/img924/2964/VoGuD8.gif "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." Your welcome. Bitcoin Tips: 1E1bAuCkFUVeyz9YWZWRtHpS4D6999n4ET Send all bitcoins to above address to test for forks. Ill let you know if they are fork coins. Title: Re: FORK in progress ... now ! Post by: CryptoWiz420 on July 20, 2017, 01:49:35 AM We will know it soon. I read 75% already favors Only 63% ;) Code: 2017-07-18 17:18:43 UpdateTip: new best=0000000000000000001def621c5bc90d1f0be86e2c84a955d8b0f94864090a1c height=476403 version=0x20000000 log2_work=86.780956 tx=240142243 date='2017-07-18 17:15:40' progress=0.999998 cache=162.4MiB(84920tx) warning='63 of last 100 blocks have unexpected version' Its 88% remember: 1E1bAuCkFUVeyz9YWZWRtHpS4D6999n4ET Free fork tester Title: Re: FORK in progress ... now ! Post by: harimauagam on September 07, 2017, 10:24:55 AM That's great when FORK is underway let's see together do not look at it when it's ready for those who know.
|
