Avant c'était explicitement BTC1 maintenant c'est satoshi:1.14.4 ^^ sont malins.   vu ! 2017-07-17 23:06:21 receive version message: /Satoshi:1.14.4(2x)/: version 70015, blocks=471344, us=xxx, peer=275
2017-07-18 13:09:56 receive version message: /Satoshi:1.14.4(2x)/: version 70015, blocks=473649, us=xxx, peer=1810
En plus, ils sont tout récent (le premier dans la liste ... est le seul depuis le début du mois) |
|
|
|
@Meuh un peu hors sujet, mais tu vois des noeuds BTC1 ? Au début, oui (genre pendant 3 jours, j'en avais un ou 2 ... comme les Classic et les BU ... qui s’accrochaient à mes slots). Depuis plus. Par contre, ceux-là, ils sont réguliers : 2017-07-07 18:53:00 receive version message: /Bitcoin ABC:0.14.1(EB8.0)/: version 70015, blocks=474675, us=xxx, peer=13153
2017-07-16 09:38:42 receive version message: /Bitcoin ABC:0.14.2(EB8.0)/: version 70015, blocks=368661, us=xxx, peer=13228
2017-07-18 05:25:10 receive version message: /Bitcoin ABC:0.14.3(EB8.0)/: version 70015, blocks=476328, us=xxx, peer=900
|
|
|
|
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). |
|
|
|
Normalement tu seras remboursé sous 48h car la banque doit logiquement faire l'avance à son client... J'ai bien dit normalement car dans les faits, ça dépend un peu des établissements mdr...
ouais, chez moi, c'est 2 mois. |
|
|
|
C'est la merde, hein, pour comprendre ?  C'est fait pour. Si un bloc de mineurs (les 61% BIP91) voulaient vraiment passer le SegWit, ils mineraient depuis JANVIER, des blocks avec une version marquée SegWit. Hors, ils ne l'ont pas fait ... et ne LE FONT TOUJOURS PAS depuis hier ! Ils préfèrent miner leurs propres blocks avec une version spéciale non-reconnue par Bitcoin Core. Bitcoin Core ne reconnaît que ceux-là : https://bitcoincore.org/en/bips/ |
|
|
|
Non, ce qui me pose un problème est qu'en moins de 12h, on est passé de 0% de BIP91 à 61%. ça s'appelle une attaque déploiement coordonnée. On appelle aussi cela une blitzkrieg = guerre-éclair. ça n'a rien à voir avec une volonté communautaire et poser d'adopter une solution ... qui, dans la majortié des cas, évolue lentement mais surement en 3 mois sur le réseau Bitcoin. Les 61% sont un bloc dangereux à surveiller. Pour ceux qui ne l'ont peut-être pas encore compris, je suis un supporter et mineur BIP148. Je veux du SegWit et suit les rêgles d'activation de Bitcoin Core mais en forçant le 1er Août (on a laissé 2 mois au gens pour le comprendre). Les gars en BIP91, ils laissent 2 semaines.  et on sait pas ce qu'ils vont faire après jusqu'en novembre. et je serais même tenter de dire que les 35% de Segwit BIP9 ne sont justement pas les 61% BIP91 actuel.  |
|
|
|
Tu as plus de 380 jours de protection sur une CB. En revanche, on ne peut plus te piquer les BTC livrés ... Donc, c'est pour ça que je n'utilises que des vendeurs à CB reconnus sur le forum (donc avec au moins 7% de frais). |
|
|
|
Better article than Coindesk : http://bitcoinist.com/mining-pool-signal-bitcoin-whole/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. |
|
|
|
|
Mon problème est la durée de minage qui a débouché sur l'octroit de 61% de la puissance de minage du réseau Bitcoin.
Sur la section anglaise, ils ne comprennent pas que c'est une attaque 51%.
Ils pensent qu'ils sont tous gentils, les mineurs à vouloir voter entre eux sur la version des blocks (02 = segwit, 10 = un truc, 12 = un autre).
Hors, moi qui ait un full node, je vois totalement la différence.
Surtout quand cette "démonstration" de minage de blocks à version différente (de ceux planifiés) a été réalisée en moins de 12h de temps.
Qui dit que dans le même temps, ils peuvent pas passer sur une version "fermée" de bitcoin core modifiée à leur sauce et faire un SPLIT définitif comme avec ETH et ETC ?
Rien.
Absolument rien ne les empêche de faire cela ... justement.
Les opérateurs de pool l'ont aussi compris (ce matin) ... comme Kano (qui fait tourné sa propre version du P2Pool).
SegWit ne peut être activé que par la version 2x...02 à travers le réseau (les nodes le voient).
Ce que font les 61% de puissance de minage actuellement, ce n'est pas SegWit.
C'est une entente pour voir combien ils sont ... si cela permet de faire du SPLIT profitable ou pas.
SegWit n'est pas l'objectif (c'est une façade pour vendre le SegWit2x actuel aux mineurs).
|
|
|
|
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_supportHypocrites 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. |
|
|
|
It does activate Segwit. You have a fundamental misunderstanding if you think that it does not. BIP91 will start orphaning non-SW signalling blocks after it has 80% of the blocks for 72 hours (IIRC). This means that the traditional activation mechanism will see a spike to 95% (BIP9) which requires 2 weeks to lock in Segwit, and then another 2 weeks to activate it.
my problem is the time, the interval of the rise of the 61% of "this" Segwit2x blocks versions. in less than 12h, they have switch from produce Bitcoin Core Official version block ... to "here" specific version. in less than that, they can switch from Segwit2x commented code ... to a closed one (BU style). they already fail to do this with Bitcoin XT (38%). that's why i warn the community to stay & watch this evolution closesly because of this mining sector (the 61%). I would believe of the "trust" of the mining sector (the 61%) ... but they did not prove they were trustworthy in following the basic rules. They want to create their own coin each time by forcing the nodes to use their client with the more than 51% mining power. It's not new. And that's why i survey the BIP9 only ... Interesting times. I hope that lock-in period will succeed the first time but considering these two big pools and several small pools aren't signalling BIP91 yet, it may take some time for it to happen.
Agree. |
|
|
|
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. |
|
|
|
I just switch my miner to SlushPool, back on mining Version x20000002 (SegWit), and not this SegWitx2 New York Agreement bullshit. Perfect quote. |
|
|
|
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 ? |
|
|
|
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) ...  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.  |
|
|
|
Scaling debat is reaching it's climax, Segwit lock-in incoming soon.
hint : BIP91 is not a bitcoin core feature or policy. It doesn't provide a way to activate SegWit. Officials BIPS of Bitcoin Core are here : https://bitcoincore.org/en/bips/ |
|
|
|
Stop scaring the newbies, Meuh6879.
Stable at 61% of mining power.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 |
|
|
|
SegWit only activate "on the whole Bitcoin Network" (and miners) with BIP141, BIP143, BIP144 and BIP145 ... because Bitcoin Core only support this activation method. https://bitcoincore.org/en/bips/BIP91 is not supported by the whole network. It's only a "mod" of Bitcoin Core for Miners vote mecanism on blocks. A bad one ... Bitcoin XT have doing the same thing in the past. |
|
|
|
|
Show Posts
