Topic: [ANN][SegWit2X] Together we will see a business through. - page 65. (Read 53373 times)
One thing is for sure, our dear Donna is more (in)famous now than she ever could had been with her dancer career.
Unfortunately we had to cancel the hardfork
The next hardfork is scheduled on january 11
Keep your wallets open and follow us on twitter
The next hardfork is scheduled on january 11
Keep your wallets open and follow us on twitter
Unfortunately we had to cancel the hardfork
The next hardfork is scheduled on january 11
Keep your wallets open and follow us on twitter
The next hardfork is scheduled on january 11
Keep your wallets open and follow us on twitter
ATTENTION! ATTENTION!
THIS NEWS JUST IN!!
The BITCOIN CORE DEVELOPERS are trying TO F**K US!!
They've been coding non-stop these last 4 days in order to skip block 501451!!
They've been coding non-stop these last 4 days in order to skip block 501451!!
I've been talking to a friend of mine who's a CORE DEVELOPER and he said and I quote
"We'll SKIP block 501451. From block 501450 we'll JUMP directly to block 501452. This way we'll f**k Jaap and Donna! Ha! They want to fork us!?? NEVERRR!!!"
"We'll SKIP block 501451. From block 501450 we'll JUMP directly to block 501452. This way we'll f**k Jaap and Donna! Ha! They want to fork us!?? NEVERRR!!!"
I've also been trying to get in touch with my good friend Rog Ver, but the prick is trolling yobit, dumping his B*trash and desperately grabbing B2X futures.
So, ppl, pay attention: that's why bitcoin is slightly crashing now. It's just a network realignment in order to SKIP block 501451. Nothing to worry about.
I think this is one of the best comments so far.
So if there is no fork why bother making a false annoucement? How do they earn any money if there's no coins at all? 
That must be the offline code feature.
So there is no actually working node? Mainnet doesn't exist? The fork failed to materialize then.
yes.. but I closed it now. but the result should be the same for all on the same block
same when i start stratum it is disconnectingyes.. but I closed it now. but the result should be the same for all on the same block
same when i start stratum it is disconnecting
yes.. but I closed it now. but the result should be the same for all on the same block
me too stuck @501450
Same here, maybe we are actually on the right chain? Where do you see diff 1.00?
Code:
22:28:08

getmininginfo
22:28:08

{
"blocks": 501450,
"currentblockweight": 0,
"currentblocktx": 0,
"difficulty": 1873105475221.611,
"errors": "",
"networkhashps": 1.37030310266546e+019,
"pooledtx": 0,
"chain": "main"
}
"version": 150100,
"protocolversion": 70015,
"walletversion": 139900,
"balance": 0.00000000,
"blocks": 501450,
"timeoffset": 31,
"connections": 8,
"proxy": "",
"difficulty": 1873105475221.611,
"testnet": false,
"keypoololdest": 1514374034,
"keypoolsize": 2000,
"paytxfee": 0.00000000,
"relayfee": 0.00001000,
"errors": ""
}
under x11 pools there is B2X - segwit2x the diff there we calculate from our stratum next block target, next block would be diff 1
Someone just told me that the channel in fact is not private, only my account was manually banned by the channel admin. But that makes no sense because my account is only a few days old and I have never been to that channel. That's really messed up 
Either way, based on what those individuals demonstrated so far this is clearly another fork that I am going to dump as soon as I can.
Either way, based on what those individuals demonstrated so far this is clearly another fork that I am going to dump as soon as I can.
What tools you are using for mining?
All X11 tools return rejected blocks
[2017-12-28 21:39:53] accepted: 0/1 (diff 0.064), 102.36 MH/s booooo
[2017-12-28 21:39:53] reject reason: low difficulty share of 2.886600873641242e-10
[2017-12-28 21:39:54] accepted: 0/2 (diff 0.074), 117.55 MH/s booooo
[2017-12-28 21:39:54] reject reason: low difficulty share of 3.458714888012202e-10
All X11 tools return rejected blocks
[2017-12-28 21:39:53] accepted: 0/1 (diff 0.064), 102.36 MH/s booooo
[2017-12-28 21:39:53] reject reason: low difficulty share of 2.886600873641242e-10
[2017-12-28 21:39:54] accepted: 0/2 (diff 0.074), 117.55 MH/s booooo
[2017-12-28 21:39:54] reject reason: low difficulty share of 3.458714888012202e-10
me too stuck @501450
Same here, maybe we are actually on the right chain? Where do you see diff 1.00?
Code:
22:28:08

getmininginfo
22:28:08

{
"blocks": 501450,
"currentblockweight": 0,
"currentblocktx": 0,
"difficulty": 1873105475221.611,
"errors": "",
"networkhashps": 1.37030310266546e+019,
"pooledtx": 0,
"chain": "main"
}
"version": 150100,
"protocolversion": 70015,
"walletversion": 139900,
"balance": 0.00000000,
"blocks": 501450,
"timeoffset": 31,
"connections": 8,
"proxy": "",
"difficulty": 1873105475221.611,
"testnet": false,
"keypoololdest": 1514374034,
"keypoolsize": 2000,
"paytxfee": 0.00000000,
"relayfee": 0.00001000,
"errors": ""
}
under x11 pools there is B2X - segwit2x the diff there we calculate from our stratum next block target, next block would be diff 1
Can you please tell me what's the second telegram channel? On their website I see only 2 telegram links: Seg_wit2X, which is read-only, and Segwit2Xfork, which is private and not accessible:
https://i.imgur.com/lzErPt4.png
This might answer your question:
the admins disappeared from both their telegram channels
I wouldn't be surprised if we will never hear anything again from them.
me too stuck @501450
Same here, maybe we are actually on the right chain? Where do you see diff 1.00?
Code:
22:28:08

getmininginfo
22:28:08

{
"blocks": 501450,
"currentblockweight": 0,
"currentblocktx": 0,
"difficulty": 1873105475221.611,
"errors": "",
"networkhashps": 1.37030310266546e+019,
"pooledtx": 0,
"chain": "main"
}
"version": 150100,
"protocolversion": 70015,
"walletversion": 139900,
"balance": 0.00000000,
"blocks": 501450,
"timeoffset": 31,
"connections": 8,
"proxy": "",
"difficulty": 1873105475221.611,
"testnet": false,
"keypoololdest": 1514374034,
"keypoolsize": 2000,
"paytxfee": 0.00000000,
"relayfee": 0.00001000,
"errors": ""
}
me too stuck @501450
Same here, maybe we are actually on the right chain? Where do you see diff 1.00?
Code:
22:28:08

getmininginfo
22:28:08

{
"blocks": 501450,
"currentblockweight": 0,
"currentblocktx": 0,
"difficulty": 1873105475221.611,
"errors": "",
"networkhashps": 1.37030310266546e+019,
"pooledtx": 0,
"chain": "main"
}
me too stuck @501450
Same here, maybe we are actually on the right chain? when i try wallet disconnecting
me too stuck @501450
Same here, maybe we are actually on the right chain?
I would reserve German Translation if you need
Jump to: