XT 12.7% of Network - No blocks mined

[Xialla]

XT, fork, Gavin, some guy called Mike, blocking Tor exit IPs, node counting..

guys, is there some official announcment or statement done by core developers? I'm getting lost, even I tried to somehow understand it. All this madness is because of block size or there is something else?

[adamstgBit]

What about this https://blockchain.info/block/00000000000000000174419fa2ba5003e123dbd97c6982aff1863f016b04789d

Isn't this a XT block?

There's no way to tell, because someone created a fake and indistinguishable XT client. It could effectively cause a premature fork.

We won't know how much of that "12.7%" is real and how much is spoofed until XT's malicious trigger is (prematurely) activated.

This was mined by Slush so we know it is not fake...

Slush is mining XT version blocks now?

Is there a problem? They let their miners choose which version to mine.

oh thats cool, you'd think they would just make XT blocks for all miners. well done Slush! I think everyone using Slush  should go turn on this XT blocks option, and or Slush could make this a default until turned off.

[Lucko]

XT, fork, Gavin, some guy called Mike, blocking Tor exit IPs, node counting..

guys, is there some official announcment or statement done by core developers? I'm getting lost, even I tried to somehow understand it. All this madness is because of block size or there is something else?

Well they figure out that they were looking at the wrong code by mistake https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010388.html They more or less figure out that they messed up things but still good PR and FUD.

Not sure what you man by node counting. It is happening for all nodes https://getaddr.bitnodes.io/nodes/

Banning TOR? Not really... Just a mistake again. It "blocks" TOR if attacked from TOR(XT nodes are under attack) if by "block" you mean drops some connections for duration of the attack... Before that we had to really block TOR using FW or be DOSed...

And I would say that all this madness in more about money then anything else...

[iCEBREAKER]

What about this https://blockchain.info/block/00000000000000000174419fa2ba5003e123dbd97c6982aff1863f016b04789d

Isn't this a XT block?

There's no way to tell, because someone created a fake and indistinguishable XT client. It could effectively cause a premature fork.

We won't know how much of that "12.7%" is real and how much is spoofed until XT's malicious trigger is (prematurely) activated.

This was mined by Slush so we know it is not fake...

Slush is mining XT version blocks now?

Slush might be using XT.  Or they might be using NotXT.  No way to tell, until someone forces the issue by accepting XTcoins and then finding out if they are actually NotXTcoins.

[not altcoin hitler]

XT, fork, Gavin, some guy called Mike, blocking Tor exit IPs, node counting..

guys, is there some official announcment or statement done by core developers? I'm getting lost, even I tried to somehow understand it. All this madness is because of block size or there is something else?

It's about a hostile takeover and not really about blocksize.

[Lucko]

XT, fork, Gavin, some guy called Mike, blocking Tor exit IPs, node counting..

guys, is there some official announcment or statement done by core developers? I'm getting lost, even I tried to somehow understand it. All this madness is because of block size or there is something else?

Well they figure out that they were looking at the wrong code by mistake https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010388.html They more or less figure out that they messed up things but still good PR and FUD.

Not sure what you man by node counting. It is happening for all nodes https://getaddr.bitnodes.io/nodes/

Banning TOR? Not really... Just a mistake again. It "blocks" TOR if attacked from TOR(XT nodes are under attack) if by "block" you mean drops some connections for duration of the attack... Before that we had to really block TOR using FW or be DOSed...

And I would say that all this madness in more about money then anything else...

I already clarified this for you and you keep spreading misinformation. Who do you work for?

Please do it again... It was fun. You just told me to look at the code. I can't show you that I' right since you cant prove an negative only positive. The only way would be to exclude every part of a code... So copy paste the code? But that doesn't help right? So unless you are ready to post code that do that we can have some fun... But this time please use the one that is part of XT repository...

[Lucko]

XT, fork, Gavin, some guy called Mike, blocking Tor exit IPs, node counting..

guys, is there some official announcment or statement done by core developers? I'm getting lost, even I tried to somehow understand it. All this madness is because of block size or there is something else?

It's about a hostile takeover and not really about blocksize.

So devs will increase blocksize? Grate news. Link please...

[Lucko]

What about this https://blockchain.info/block/00000000000000000174419fa2ba5003e123dbd97c6982aff1863f016b04789d

Isn't this a XT block?

There's no way to tell, because someone created a fake and indistinguishable XT client. It could effectively cause a premature fork.

We won't know how much of that "12.7%" is real and how much is spoofed until XT's malicious trigger is (prematurely) activated.

This was mined by Slush so we know it is not fake...

Slush is mining XT version blocks now?

Slush might be using XT.  Or they might be using NotXT.  No way to tell, until someone forces the issue by accepting XTcoins and then finding out if they are actually NotXTcoins.

Yes slush would really do that. And he supports 8MB if you don't know... https://www.reddit.com/r/Bitcoin/comments/3gryjy/slushs_pool_endorses_8mb_blocks/ But thanks for showing how low will you go...

[Alley]

Core devs don't give 2 shits about XT or blocksize.  They don't even care about core anymore.  They probably prefer XT just take over so they can be done with bitcoin.  Notice how they're silent on what's going on with no statements being made?

[sangaman]

I contribute resources to the bitcoin network by running my home computer as a node. I switched to running an XT node some weeks ago. I think changes from Bitcoin Core not related to a block size increase should be kept to a minimum at least until the dust settles, however. Either way, running an XT node is just my way of signaling to the world that as a longtime Bitcoin user I support block limit increases above the current cap of 1 MB.

[Nagle]

Miners, not nodes, determine block size. Only miners can validate a transaction. If miners don't generate bigger blocks, bigger blocks don't happen.

[coinpr0n]

I contribute resources to the bitcoin network by running my home computer as a node. I switched to running an XT node some weeks ago. I think changes from Bitcoin Core not related to a block size increase should be kept to a minimum at least until the dust settles, however. Either way, running an XT node is just my way of signaling to the world that as a longtime Bitcoin user I support block limit increases above the current cap of 1 MB.

You're also signalling (albeit indirectly) that you support Mike Hearn as "benevolent" dictator and sole commiter of Bitcoin.

[NorrisK]

Miners won't switch to XT yet because they can't afford the downtime of their mining rigs.. What if it doesn't update well? Could mean hours of downtime and a huge loss of income. They will probably be the last to switch. Aren't most miners even on older less secure versiosn of the QT?

[pedrog]

Second block mined with XT https://blockchain.info/pt/block-height/370661

The fork is made in 2016, correct?

[turvarya]

Second block mined with XT https://blockchain.info/pt/block-height/370661

The fork is made in 2016, correct?

It is made earliest in January 2016, depending if the 75% consensus(of hashing power) is reached.

[iCEBREAKER]

Second block mined with XT or NotXT https://blockchain.info/pt/block-height/370661

ftfy

If you could stop pretending anyone is able to tell an XT block from a NotXT block, that would be great.

But I know you won't, because Gavinstas love to mislead the public.

[DooMAD]

Second block mined with XT or NotXT https://blockchain.info/pt/block-height/370661

ftfy

If you could stop pretending anyone is able to tell an XT block from a NotXT block, that would be great.

But I know you won't, because Gavinstas love to mislead the public.

You support the NotXT software that fraudulently manipulates the figures and then have the nerve to accuse others of misleading people.  Duplicitous much?  You can't engage in vote-rigging and then whine about people not being able to tell what the figures are when you are one of the trolls helping to obfuscate them.  You're the one being dishonest, pedrog is simply a victim of your dishonesty.

[iCEBREAKER]

Second block mined with XT or NotXT https://blockchain.info/pt/block-height/370661

ftfy

If you could stop pretending anyone is able to tell an XT block from a NotXT block, that would be great.

But I know you won't, because Gavinstas love to mislead the public.

You support the NotXT software that fraudulently manipulates the figures and then have the nerve to accuse others of misleading people.  Duplicitous much?  You can't engage in vote-rigging and then whine about people not being able to tell what the figures are when you are one of the trolls helping to obfuscate them.  You're the one being dishonest, pedrog is simply a victim of your dishonesty.

Oh great, you've finally realized why it's misleading to report XT nodes/blocks without mentioning they could just as easily be NotXT spoofs.   

Heam says XT, we say sabotage.  We say NotXT, you say sabotage.

NotXT simply forks Heam's XT fork.  Don't dish it out if you can't take it.