[ANN] 1337 [MANDATORY UPDATE] 41.78% APR| POS ONLY - page 105.

vella85

hero member

Activity: 1862

Merit: 590

Quote from: freebitcoins4u on December 14, 2016, 12:06:16 PM

1337 price went from 0.01 dogecoin to 0.016 dogecoin!

That's great and we just need 1337 coin to get back to 1 sat and above. As I said every time it seems to be making an upward trend it then gets dumped big time. But at least we are seeing daily volume which is a good sign that people are interested in 1337 coin.

freebitcoins4u

hero member

Activity: 798

Merit: 500

1337 price went from 0.01 dogecoin to 0.016 dogecoin!

vella85

hero member

Activity: 1862

Merit: 590

Every time it looks like 1337 coin getting back up to 1 sat and over, it gets dumped hard. It's a shame that this happens as this coin deserves to be worth more then below 1 sat. I purchased another 100k sats worth of 1337 coins from my faucet earnings.

steve321

hero member

Activity: 627

Merit: 500

1337 blockchain has been updated on CryptoChainer.com! No need to fully re-sync...

bitmaster1x

legendary

Activity: 1288

Merit: 1000

CRYPTO-CITY.COM 🌟 Communities

Quote from: titteringtacos on December 10, 2016, 02:33:34 PM

Quote from: TeamDisaster on December 09, 2016, 02:28:20 PM

Quote from: titteringtacos on December 09, 2016, 02:16:30 PM

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

9 million is gone Sad

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.. Sad

.. and i dont know what to do Sad

Delete everything except your wallet.dat and resync. If you've staked on the wrong fork, think of it as though it never staked.

titteringtacos

sr. member

Activity: 490

Merit: 250

Quote from: TeamDisaster on December 09, 2016, 02:28:20 PM

Quote from: titteringtacos on December 09, 2016, 02:16:30 PM

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

9 million is gone Sad

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.. Sad

.. and i dont know what to do Sad

bitmaster1x

legendary

Activity: 1288

Merit: 1000

CRYPTO-CITY.COM 🌟 Communities

What's the latest going on here?

TeamDisaster

hero member

Activity: 674

Merit: 500

Quote from: titteringtacos on December 09, 2016, 02:16:30 PM

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

9 million is gone Sad

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?

titteringtacos

sr. member

Activity: 490

Merit: 250

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

9 million is gone Sad

Macr0

sr. member

Activity: 370

Merit: 250

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.

bredsaal

newbie

Activity: 37

Merit: 0

Quote from: ?? on ??

Quote from: bredsaal on December 08, 2016, 06:53:46 AM

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.

freebitcoins4u

hero member

Activity: 798

Merit: 500

Quote from: gufpmvgw3334 on December 08, 2016, 11:50:55 AM

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

gufpmvgw3334

member

Activity: 106

Merit: 10

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

CryptoWiz420

hero member

Activity: 564

Merit: 516

Seriously, no one tried repairwallet?

synthgauge

hero member

Activity: 1150

Merit: 502

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.

synthgauge

hero member

Activity: 1150

Merit: 502

Quote from: kiklo on December 08, 2016, 09:03:49 AM

Quote from: ?? on ??

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.

Cool

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.

kiklo

legendary

Activity: 1092

Merit: 1000

Quote from: ?? on ??

Quote from: kiklo on December 08, 2016, 09:03:49 AM

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.

Cool

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

Cool

kiklo

legendary

Activity: 1092

Merit: 1000

Quote from: ?? on ??

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.

Cool

kiklo

legendary

Activity: 1092

Merit: 1000

Quote from: ?? on ??

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.

Cool

kiklo

legendary

Activity: 1092

Merit: 1000

Quote from: bredsaal on December 08, 2016, 06:53:46 AM

Quote from: ?? on ??

Quote from: bredsaal on December 07, 2016, 06:38:16 PM

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.)

Cool

FYI:
Snapshot is updated to today. Upload Complete.
https://bitcointalksearch.org/topic/m.15734992

Topic: [ANN] 1337 [MANDATORY UPDATE] 41.78% APR| POS ONLY - page 105. (Read 259517 times)