Topic: ★ ZEIT ★ [COMMUNITY & KNIGHTS] [ULTRA LOW INFLATION] [MICRO-PAYMENTS] - page 811. (Read 1009334 times)
March 01, 2014, 03:13:00 AM
is hash.so working or not?
March 01, 2014, 03:12:12 AM
March 01, 2014, 03:10:50 AM
We apologize for the stuck at 500 it is fixed and everything is running smooth again stay tuned for windows .qt updated source already has been on github
March 01, 2014, 03:10:30 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...
[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 ;(
These are the peers I'm connected to that are currently showing blocks >500:
184.82.131.93
107.170.26.155
203.20.114.252
37.187.138.76
Try deleting peers.dat again, and adding those to your config. You are restarting the client each time, right?
March 01, 2014, 03:10:19 AM
is there any working pool plz?
March 01, 2014, 03:10:11 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! This debacle has inspired a movie "Block 500"... coming soon to a miner near you
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!
Oh I know, dude... I lost almost 7 Kg of weight for 3 months... and probably became alcoholic, wasted all my 2 month crypto income for sluts and whiskey...
March 01, 2014, 03:09:16 AM
March 01, 2014, 03:08:55 AM
Can we vote on this coin NEVER GETTING on Cryptsy and Coinwarz? Is that even possible?
Also, can we scrub the bribery-exchange mintpal.com from OP? This is just bad reputation that ZEIT is involved with a bribery exchange site.
Also, can we scrub the bribery-exchange mintpal.com from OP? This is just bad reputation that ZEIT is involved with a bribery exchange site.
March 01, 2014, 03: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...
[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
March 01, 2014, 03: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...
[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
March 01, 2014, 03:06:46 AM
https://zeit.poolers.org is updated and at block 587, bring your miners.
March 01, 2014, 03: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...
[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 ;(
March 01, 2014, 03:04:25 AM
HashFever
http://zeit.hashfever.com
PROP payout system
Fast payouts - 1 - 5 min
1% pool fee
FIXED and running ! !!!
http://zeit.hashfever.com
PROP payout system
Fast payouts - 1 - 5 min
1% pool fee
FIXED and running ! !!!
March 01, 2014, 03: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! This debacle has inspired a movie "Block 500"... coming soon to a miner near you
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!
March 01, 2014, 03: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.
March 01, 2014, 03: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!
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!
March 01, 2014, 03: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!
March 01, 2014, 03: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.
March 01, 2014, 03:01:09 AM
Looks like HashStrike might be fixing their issue. I would give them a few minutes.
March 01, 2014, 03: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
Jump to: