MinermanNC
Legendary
 Offline
Activity: 2198
Merit: 1000
|
 |
March 01, 2014, 07:55:14 AM |
|
Hats off to the devs.. That was one QUICK fix. For everyone complaining,, Please by all means go mine a different coins. I've got plenty flowing in my wallet now and the more people that leave just means more coins for me  Explain: ? |
*BTC: 1DiR25SPo84sThzTATr27EZEQZLt6hv6tG
|
|
|
|
|
|
|
|
|
|
|
|
The Bitcoin network protocol was designed to be extremely flexible. It can be used to create timed transactions, escrow transactions, multi-signature transactions, etc. The current features of the client only hint at what will be possible in the future.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
March 01, 2014, 07:55:27 AM |
|
<@Devianttwo> ATTENTION: POOL OWNERS! [08:31] <@Devianttwo> http://pastebin.com/9vjU2vRi[08:31] <@Devianttwo> REMOVE THE CHECKPOINTS OF 501 801 1011 and 1263 [08:31] <@Devianttwo> AND THEN RECOMPILE! [08:31] <@Devianttwo> THIS WILL FIX THE BLOCKCHAIN not sure why zeit.hash.so is talking about right fork instead of doing this... what do you mean? comment out this lines??? // ( 501, 0x30e19ec7u ) // ( 801, 0xa892a5b5u ) // ( 1011, 0x3f00c478u ) // ( 1263, 0xf597ad39u ) Yes. They're checkpoints for blocks that don't yet exist, so the hashes will never match. I fixed my client but it was still not interested in syncing; I had to remove peers.dat and addnode= the one peer that had a block number >500. I'm not sure if others will have to do this too. |
|
|
|
|
|
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
March 01, 2014, 07:56:06 AM |
|
Pool is fixed. What about the wallet then? It stuck block 500 and cannot step any more.
The fix requires a recompile (removal of mystery checkpoints), so you will need to install a new version of the wallet. |
|
|
|
|
silidons
Newbie
Offline
Activity: 42
Merit: 0
|
|
March 01, 2014, 07:56:15 AM |
|
when the shit is zeit.hash.so gonna come up  |
|
|
|
|
ozman911
Newbie
Offline
Activity: 36
Merit: 0
|
|
March 01, 2014, 07:56:38 AM |
|
Damm it,,,, Hashstrike down now. Looks like too many people jumped to it....
|
|
|
|
|
MinermanNC
Legendary
Offline
Activity: 2198
Merit: 1000
|
|
March 01, 2014, 07:58:07 AM |
|
Are you POSITIVE your not mining on a fork? |
*BTC: 1DiR25SPo84sThzTATr27EZEQZLt6hv6tG
|
|
|
|
embraer
|
|
March 01, 2014, 07:58:39 AM |
|
Hmm, i think it is still not fixed. The wallet stuck at block 500!!! Do we have to expect wallet update? What the debs are going to do to fix this!!! The community need more information about what's happened.  |
|
|
|
|
MinermanNC
Legendary
Offline
Activity: 2198
Merit: 1000
|
|
March 01, 2014, 08:00:51 AM |
|
Hmm, i think it is still not fixed. The wallet stuck at block 500!!! Do we have to expect wallet update? What the debs are going to do to fix this!!! The community need more information about what's happened. Agreed. Going to bed |
*BTC: 1DiR25SPo84sThzTATr27EZEQZLt6hv6tG
|
|
|
bwcainmay
Newbie
Offline
Activity: 56
Merit: 0
|
|
March 01, 2014, 08:01:09 AM |
|
Looks like HashStrike might be fixing their issue. I would give them a few minutes.
|
|
|
|
|
ozman911
Newbie
Offline
Activity: 36
Merit: 0
|
|
March 01, 2014, 08:02:02 AM |
|
Hats off to the devs.. That was one QUICK fix. For everyone complaining,, Please by all means go mine a different coins. I've got plenty flowing in my wallet now and the more people that leave just means more coins for me Explain: ? Explain what? My rigs are running, with the exception of the pool going down here and there, they are submitting shares. I havnt upgraded my wallet,, and Im getting regular deposits from pool. Because of this little bug my daily estimate has went up substantially. I just opened the wallet and let it keep running. I had 3 pools set as fail-overs way before the release. Ive had to many new coin pools bomb on me in the past at release time. |
|
|
|
|
jasemoney
Legendary
Offline
Activity: 1610
Merit: 1008
Forget-about-it
|
|
March 01, 2014, 08:02:12 AM |
|
Hmm, i think it is still not fixed. The wallet stuck at block 500!!! Do we have to expect wallet update? What the debs are going to do to fix this!!! The community need more information about what's happened. the pool operators can change their wallet compilation to fix it, anyone on a pool thats fixed it for themselves is good. anyone with a competent pool and a bad wallet will be fine once the windows fix is released. if your solo mining your SOL unless you can compile yourself, and obv if your on a mac you were screwed anyways so forget it! |
$MAID & $BTC other than that some short hodls and some long held garbage.
|
|
|
|
hoju2k
|
|
March 01, 2014, 08:02:54 AM |
|
From CR:
Zeit Blockchain Halt
ATTENTION: ZeitCoin Patch released! No Windows Update yet! Be very careful transfering coins until windows client is released!
Internal Trades are Unaffected!
|
|
|
|
|
tylerderden
Copper Member
Legendary
Offline
Activity: 1162
Merit: 1025
|
|
March 01, 2014, 08:04:02 AM |
|
Hats off to the devs.. That was one QUICK fix. For everyone complaining,, Please by all means go mine a different coins. I've got plenty flowing in my wallet now and the more people that leave just means more coins for me thats funny after your last post...plus i dont know what the fuck your talking about my pool is still down, cryptorush still says negative put the pipe down bro. |
|
|
|
|
bvault
Member
Offline
Activity: 112
Merit: 10
|
|
March 01, 2014, 08:04:17 AM |
|
WHAT A GONG SHOW! I HAVE SEEN IT ALL IN THE CRYPTO WORLD MY FRIEND!
This debacle has inspired a movie "Block 500"... coming soon to a miner near you
Better yet The "ZEIT 500" nascar race! LOL. Listen... this drama is funny man. BTW I am sure some of you experience this with your wives/gfs/friends>>>> Most of my buddies are not into crypto, so when they sees me excited or reacting to goings-on in the crypto world, I usually dont even know where to start... the pump and dumps, pools getting hacked, +/-100%-type price swings, new coins being released daily, scams, scrypt asic rumours and pre-orders, crypto-is-dead worries, mt gox problems, paypal problems, wolong..... and now block 500!  |
---------------
BTC - 13WkfueYZzx7d9VLXgkf9TtDBPhUVHizCh
|
|
|
hashfever
Member
Offline
Activity: 84
Merit: 10
|
|
March 01, 2014, 08:04:25 AM |
|
|
|
|
|
|
|
matoy
|
|
March 01, 2014, 08:05:07 AM |
|
<@Devianttwo> ATTENTION: POOL OWNERS! [08:31] <@Devianttwo> http://pastebin.com/9vjU2vRi[08:31] <@Devianttwo> REMOVE THE CHECKPOINTS OF 501 801 1011 and 1263 [08:31] <@Devianttwo> AND THEN RECOMPILE! [08:31] <@Devianttwo> THIS WILL FIX THE BLOCKCHAIN not sure why zeit.hash.so is talking about right fork instead of doing this... what do you mean? comment out this lines??? // ( 501, 0x30e19ec7u ) // ( 801, 0xa892a5b5u ) // ( 1011, 0x3f00c478u ) // ( 1263, 0xf597ad39u ) Yes. They're checkpoints for blocks that don't yet exist, so the hashes will never match. I fixed my client but it was still not interested in syncing; I had to remove peers.dat and addnode= the one peer that had a block number >500. I'm not sure if others will have to do this too. ok but i did that; i did update the github source (with kernel.cpp and net.cpp), recompiled, deleted blockchain, peers.dat and addnodes in the conf but still stucked on block #500 ;( |
|
|
|
|
|
bwcainmay
Newbie
Offline
Activity: 56
Merit: 0
|
|
March 01, 2014, 08:07:19 AM |
|
<@Devianttwo> ATTENTION: POOL OWNERS! [08:31] <@Devianttwo> http://pastebin.com/9vjU2vRi[08:31] <@Devianttwo> REMOVE THE CHECKPOINTS OF 501 801 1011 and 1263 [08:31] <@Devianttwo> AND THEN RECOMPILE! [08:31] <@Devianttwo> THIS WILL FIX THE BLOCKCHAIN not sure why zeit.hash.so is talking about right fork instead of doing this... what do you mean? comment out this lines??? // ( 501, 0x30e19ec7u ) // ( 801, 0xa892a5b5u ) // ( 1011, 0x3f00c478u ) // ( 1263, 0xf597ad39u ) Yes. They're checkpoints for blocks that don't yet exist, so the hashes will never match. I fixed my client but it was still not interested in syncing; I had to remove peers.dat and addnode= the one peer that had a block number >500. I'm not sure if others will have to do this too. ok but i did that; i did update the github source (with kernel.cpp and net.cpp), recompiled, deleted blockchain, peers.dat and addnodes in the conf but still stucked on block #500 ;( reboot |
|
|
|
|
|
matoy
|
|
March 01, 2014, 08:08:44 AM |
|
<@Devianttwo> ATTENTION: POOL OWNERS! [08:31] <@Devianttwo> http://pastebin.com/9vjU2vRi[08:31] <@Devianttwo> REMOVE THE CHECKPOINTS OF 501 801 1011 and 1263 [08:31] <@Devianttwo> AND THEN RECOMPILE! [08:31] <@Devianttwo> THIS WILL FIX THE BLOCKCHAIN not sure why zeit.hash.so is talking about right fork instead of doing this... what do you mean? comment out this lines??? // ( 501, 0x30e19ec7u ) // ( 801, 0xa892a5b5u ) // ( 1011, 0x3f00c478u ) // ( 1263, 0xf597ad39u ) Yes. They're checkpoints for blocks that don't yet exist, so the hashes will never match. I fixed my client but it was still not interested in syncing; I had to remove peers.dat and addnode= the one peer that had a block number >500. I'm not sure if others will have to do this too. ok but i did that; i did update the github source (with kernel.cpp and net.cpp), recompiled, deleted blockchain, peers.dat and addnodes in the conf but still stucked on block #500 ;( reboot lol you're funny |
|
|
|
|
Poll
