[ANN] 1337 [MANDATORY UPDATE] 41.78% APR| POS ONLY

[wakhidNkcom]

Remember remember the 25th of november..

Will thgere be another hard fork next year on the 25th of november

[1714998120]

1714998120

[1714998120]

1714998120

[1714998120]

1714998120

[1714998120]

1714998120

[1714998120]

1714998120

[bredsaal]

Stuck syncing again.. This time at block 609242..

I have configured my client to only connect to Velvet78's node, still no luck.

of course no luck if you are already on the wrong fork,
step back to your earlier chain backup (or kiklo's snapshot) and resync

That's exactly what I did, I got an additional 20k blocks or so from Velvel78's node, so I'm guessing I'm not on a fork..

./1337d getbestblockhash
328fab55032da98664d46af1eba4e7264225d5861b6673a941f442399fb3be3c

http://www.presstab.pw/phpexplorer/1337/block.php?blockhash=328fab55032da98664d46af1eba4e7264225d5861b6673a941f442399fb3be3c

As you can see, I'm on the same chain as the block explorer as well..

[bredsaal]

Stuck syncing again.. This time at block 609242..

I have configured my client to only connect to Velvet78's node, still no luck.

of course no luck if you are already on the wrong fork,
step back to your earlier chain backup (or kiklo's snapshot) and resync

That's exactly what I did, I got an additional 20k blocks or so from Velvel78's node, so I'm guessing I'm not on a fork..

./1337d getbestblockhash
328fab55032da98664d46af1eba4e7264225d5861b6673a941f442399fb3be3c

http://www.presstab.pw/phpexplorer/1337/block.php?blockhash=328fab55032da98664d46af1eba4e7264225d5861b6673a941f442399fb3be3c

As you can see, I'm on the same chain as the block explorer as well..

ok, now if you permit all addnodes back again ?
i never had such problems in win7.
of course your wallet is v1.6.0.2 and is not open to stake, right ?

Yes my wallet is 1.6.0.2-g and I've disabled staking. I tried allowing more than one connection, currently I have  16 connections, but I'm still stuck on the same block. :-/ I'll let it run overnight to see if it syncs, otherwise I'll try to get the wallet to sync on a windows computer tomorrow.

[CryptoWiz420]

Stuck syncing again.. This time at block 609242..

I have configured my client to only connect to Velvet78's node, still no luck.

of course no luck if you are already on the wrong fork,
step back to your earlier chain backup (or kiklo's snapshot) and resync

That's exactly what I did, I got an additional 20k blocks or so from Velvel78's node, so I'm guessing I'm not on a fork..

./1337d getbestblockhash
328fab55032da98664d46af1eba4e7264225d5861b6673a941f442399fb3be3c

http://www.presstab.pw/phpexplorer/1337/block.php?blockhash=328fab55032da98664d46af1eba4e7264225d5861b6673a941f442399fb3be3c

As you can see, I'm on the same chain as the block explorer as well..

did you try 'repairwallet' in the console?

[bredsaal]

Yes my wallet is 1.6.0.2-g and I've disabled staking. I tried allowing more than one connection, currently I have  16 connections, but I'm still stuck on the same block. :-/ I'll let it run overnight to see if it syncs, otherwise I'll try to get the wallet to sync on a windows computer tomorrow.

i remember now looking at your log that i saw similar crap but not with 1337,
2 other coins, and it was weird 1-block timeshift in database ops,
for every request of block N wallet actually received block N+1 or N-1 to process,
so no matter the nodes and such, any block couldn't pass the check.
sync precisely your pc clock (to time server),
if doesn't help try this in your conf:
synctime=0
i doubt it'll help but no harm in trying

My clock is synced, still no luck. Tried the synctime=0 config flag, still no luck.. I'm hoping somebody with a fully synced chain will upload the complete blockchain somewhere.. :-)

[kiklo]

Yes my wallet is 1.6.0.2-g and I've disabled staking. I tried allowing more than one connection, currently I have  16 connections, but I'm still stuck on the same block. :-/ I'll let it run overnight to see if it syncs, otherwise I'll try to get the wallet to sync on a windows computer tomorrow.

i remember now looking at your log that i saw similar crap but not with 1337,
2 other coins, and it was weird 1-block timeshift in database ops,
for every request of block N wallet actually received block N+1 or N-1 to process,
so no matter the nodes and such, any block couldn't pass the check.
sync precisely your pc clock (to time server),
if doesn't help try this in your conf:
synctime=0
i doubt it'll help but no harm in trying

My clock is synced, still no luck. Tried the synctime=0 config flag, still no luck.. I'm hoping somebody with a fully synced chain will upload the complete blockchain somewhere.. :-)

Is your wallet encrypted, so it is not trying to stake during sync?
(Be sure to have a wallet backup before encrypting it, to be safe.)

 

FYI:
Snapshot is updated to today. Upload Complete.
https://bitcointalk.org/index.php?topic=1378653.msg15734992#msg15734992

[kiklo]

he's just syncing, look at his log.
request for block f3d5e5e3b8c7db401ade7c792c50264349832be632e8c40d7ffb79fc00d1f4b1
it's valid block #609354
but wallet can't confirm tx 27bf42e502fa4584635f180812fe8e0ff9c152e3738d344aaf1176e4c8eca26e,
which is valid tx in this block

http://www.presstab.pw/phpexplorer/1337/block.php?blockhash=f3d5e5e3b8c7db401ade7c792c50264349832be632e8c40d7ffb79fc00d1f4b1

weird a bit that he's talking about being stuck at #609242,
and seems getbestblockhash gives this number,
but log shows him stuck at #609354,
as if database gone south

WARNING: AcceptBlock(): check proof-of-stake failed for block f3d5e5e3b8c7db401ade7c792c50264349832be632e8c40d7ffb79fc00d1f4b1
ERROR: ProcessBlock() : AcceptBlock FAILED

Accept Block failed , does that not mean he is trying to stake?
Or does it mean a Peer is flooding him with invalid blocks?

If so deleting the peers.dat and restarting might be a good idea.
Although the snapshot should jump him ahead of the peer , if that is the issue.

 

[kiklo]

why ?
https://github.com/Velvet78/1337/blob/765ade3e9a1edb56125a3b1c87a0c202fd6d0aa9/src/main.cpp#L2259
many conditions to cause acceptblock failed

besides he's already said the wallet is locked

Ok , missed the locked comment.

Does it mean a Peer is flooding him with invalid blocks?

If so deleting the peers.dat and restarting might be a good idea.
Although the updated snapshot should jump him ahead of the peer , if that is the issue.

 

[kiklo]

Ok , missed the locked comment.

Does it mean a Peer is flooding him with invalid blocks?

If so deleting the peers.dat and restarting might be a good idea.
Although the updated snapshot should jump him ahead of the peer , if that is the issue.

 

nope, the wallet is checking valid block, smth wrong in db ops, maybe even OS/hardware related

Hmm,
After trying the updated snapshot , if it still fails
sounds like he should run , a memory & hard drive diags , and Chkdsk C: /R /F 

 

[synthgauge]

why ?
https://github.com/Velvet78/1337/blob/765ade3e9a1edb56125a3b1c87a0c202fd6d0aa9/src/main.cpp#L2259
many conditions to cause acceptblock failed

besides he's already said the wallet is locked

Ok , missed the locked comment.

Does it mean a Peer is flooding him with invalid blocks?

If so deleting the peers.dat and restarting might be a good idea.
Although the updated snapshot should jump him ahead of the peer , if that is the issue.

 

Could be that peer is on the wrong chain or is located in a remote timezone thus experiencing a clock sync issue. Rebuild the wallet from scratch.

If that doesnt help zip a chain that ure 100% is on the correct height and upload it to mega.

Post an update in the thread asking peers to manually re-download a zipped chain and replace the one causing issues on their servers with the correct one.

[synthgauge]

So check whether u have the deps installed right, and rebuild the wallet. Whats more to say.

Clock sync issue is nothing related to a specific PC, it most likely be a node or strangers peer pushing the block which ur daemon deems invalid because of system clock discrepancies between their timezone and ur timezone.

Either way, assuming the wallet is built right the above issue is what first comes to mind so what I would do the first is rebuild the wallet.

[CryptoWiz420]

Seriously, no one tried repairwallet?

[gufpmvgw3334]

is this coin still alive? I see people dump at 1 satoshi and no one buying....

[freebitcoins4u]

is this coin still alive? I see people dump at 1 satoshi and no one buying....

please tell  me where can i dump my 1337 coins at 1 satoshi without waiting 6 months in the line and than i will buy it again at 0.01 dogecoin at the alternative market

[bredsaal]

My clock is synced, still no luck. Tried the synctime=0 config flag, still no luck.. I'm hoping somebody with a fully synced chain will upload the complete blockchain somewhere.. :-)

there should be "received block 328fab55032da98664d4" which is #609242,
may we see the log from that line on ?

That's almost 100k lines of logfile.. :-O

I've uploaded the first 5k lines after "received block 328fab55032da98664d4" instead, I hope that's enough (http://pastebin.com/ZgUwKqnR).

I'll try to download the blockchain snapshot from kiklo and sync from there.. I'll post in here to let you guys know it goes. :-)

EDIT: It worked perfect, I'm currently at the same blockheight as the presstab block explorer and my node has 20 connections.

[Macr0]

Hi folks here!
It's a crazy coin, but i like it!
I started to sync from scratch and had no problems.

Wallet is fine.

[titteringtacos]

So SAD.... from 82 million plus 1337 before it stop staking, when my wallet sync balance is only 73858070.55691882 1337.. what happened? 9 million is gone

[TeamDisaster]

So SAD.... from 82 million plus 1337 before it stop staking, when my wallet sync balance is only 73858070.55691882 1337.. what happened? 9 million is gone

Did you accidentally stake on the wrong fork for a few days after 25th November?  That's what happened to me.  Do you have a bunch of "mined but not accepted" in your Transactions?

[bitmaster1x]

What's the latest going on here?

[titteringtacos]

So SAD.... from 82 million plus 1337 before it stop staking, when my wallet sync balance is only 73858070.55691882 1337.. what happened? 9 million is gone

Did you accidentally stake on the wrong fork for a few days after 25th November?  That's what happened to me.  Do you have a bunch of "mined but not accepted" in your Transactions?

Yeah.. thats what happened to me.. .. and i dont know what to do