Just over a day until reward drops to 26k, which means 2.7 million fewer LiteDoge emitted everyday. The sell wall at 2 satoshis is nearly gone and no one has dumped any at 1 satoshi in a very long time. They say cats have nine lives, but LiteDoge has at least three lives. Hold tight, and let's start eating away at the 3 satoshi wall next.
AND SO HELP YOU GOD IF YOU START ANY DRAMA OR FIGHTS AFTER 4 SATOSHIS BECAUSE I WILL MURDER YOU IF YOU DO!!!!!
Topic: [ANN] LiteDoge - such Community coin | no premine | very fast | much profit - page 30. (Read 125384 times)
August 07, 2015, 08:29:06 AM
August 06, 2015, 04:59:44 PM
... LiteDoge Wisdom ...
August 06, 2015, 10:44:55 AM
26.000 LDOGE/block SOON 
August 05, 2015, 04:16:02 PM
lol ok thanks
my pc was on time.windows.com i changed for time.nist.gov
now i'm to 4 accepted in a row
thanks
my pc was on time.windows.com i changed for time.nist.gov
now i'm to 4 accepted in a row
thanks
Thanks for that good info.
Thanks for that good info, i wonder how many orphans I have lost due to Windows time.
Thanks for that good info, i wonder how many orphans I have lost due to Windows time.
I don't think it necessarily matters which server you sync with. I imagine the Windows servers would work just as well as the .gov servers. The most important thing is just manually clicking that button and resyncing with any time server in the list.
I agree , any server will do
August 04, 2015, 12:29:18 PM
Per your suggestion I deleted everything but wallet.dat and it worked.
Was just noting what led up to the glitch.
Ok. Have a nice staking Was just noting what led up to the glitch.
August 04, 2015, 08:38:56 AM
lol ok thanks
my pc was on time.windows.com i changed for time.nist.gov
now i'm to 4 accepted in a row
thanks
my pc was on time.windows.com i changed for time.nist.gov
now i'm to 4 accepted in a row
thanks
Thanks for that good info.
Thanks for that good info, i wonder how many orphans I have lost due to Windows time.
Thanks for that good info, i wonder how many orphans I have lost due to Windows time.
I don't think it necessarily matters which server you sync with. I imagine the Windows servers would work just as well as the .gov servers. The most important thing is just manually clicking that button and resyncing with any time server in the list.
August 04, 2015, 07:55:35 AM
Per your suggestion I deleted everything but wallet.dat and it worked.
Was just noting what led up to the glitch.
Was just noting what led up to the glitch.
August 04, 2015, 01:57:26 AM
ERROR: AcceptBlock() : rejected by synchronized checkpoint
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
Try to sync your time with basic time server "time.windows.com". Your Windows OS must not have any issues with it. Reload it,if you would have any problems. Resync again,but not run LDOGE client(Qt-wallet). When your time clock would be ok,run LDOGE Wallet. If you would have ORHANS again,resync blockchain since start: 1. Close your wallet. 2. Go to Computer-System Disc(ussually "C")-Users-AppData-Roaming-LDOGE folder. 3. Open LDOGE folder and delete all files,except wallet.dat. NOT DELETE ONLY WALLET.DAT FILE IN LDOGE FOLDER. 4. After that run LDOGE WALLET and wait end of sync. ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
I'll try some of the latter steps. If you read back I've already tried to re-sync time with multiple servers and restart the qt-client and it's not working.
EDIT: After deleting everything but the wallet file, it appears to be successfully re-syncing. Very odd that it happened right after I got 2 super-quick stakes and around the time someone was reporting a similar issue. I went over the debug log again and didn't see anything other than what's posted above.
August 03, 2015, 08:49:17 PM
http://pastebin.com/LLPqB9F3 here is the conf file for LDoge hope this helps everyone it has a few nodes and how I have my wallet set up. 
Keep on stakeage stakeums stake stake stake LITEDOGE Litedoge LDOGE ldoge
Keep on stakeage stakeums stake stake stake LITEDOGE Litedoge LDOGE ldoge
i resync my wallet and put this .conf
but still same i think, 1 accepted and 3 rejected
i just closed my others wallet for try but it worked well together before
i'm lost i don't understand i do nothing of special
Resync the clock on your PC.
the clock? im not good in english and cryptothing, i dont know if its a joke
but apparently i have 3 accepted in a row so may be problem is fixed
i wait until tonight before open my others wallet for stake
Oh no, it's a real thing. A lot of POS coins have tight timedrift specifications. Meaning if your PC's clock is off by just a few seconds, your blocks will get rejected. I included a picture below. Just click on that 'update now' button to resync the clock on your PC. 95% of the time people say they are getting a lot of rejected blocks in any POS coin, this is the reason. I do it frequently on the PC that I stake coins 24/7 on. Your PC probably just automatically resynced it's clock so now you are fine, but just an FYI in case it happens again.
Thanks for that good info.
Thanks for that good info, i wonder how many orphans I have lost due to Windows time.
August 03, 2015, 07:44:04 PM
Another thing it may be is the incorrect wallet version. I just want to make sure of this, but you have probably already checked it.
Are you using v3.2.1.1-community?
Yeah I updated to that version as soon as it was released. First thing I did was to check to make sure there wasn't another update I'd missed. Thanks for the assist.
August 03, 2015, 07:06:03 PM
ERROR: AcceptBlock() : rejected by synchronized checkpoint
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
Try to sync your time with basic time server "time.windows.com". Your Windows OS must not have any issues with it. Reload it,if you would have any problems. Resync again,but not run LDOGE client(Qt-wallet). When your time clock would be ok,run LDOGE Wallet. If you would have ORHANS again,resync blockchain since start: 1. Close your wallet. 2. Go to Computer-System Disc(ussually "C")-Users-AppData-Roaming-LDOGE folder. 3. Open LDOGE folder and delete all files,except wallet.dat. NOT DELETE ONLY WALLET.DAT FILE IN LDOGE FOLDER. 4. After that run LDOGE WALLET and wait end of sync. ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
I'll try some of the latter steps. If you read back I've already tried to re-sync time with multiple servers and restart the qt-client and it's not working.
EDIT: After deleting everything but the wallet file, it appears to be successfully re-syncing. Very odd that it happened right after I got 2 super-quick stakes and around the time someone was reporting a similar issue. I went over the debug log again and didn't see anything other than what's posted above.
Another thing it may be is the incorrect wallet version. I just want to make sure of this, but you have probably already checked it.
Are you using v3.2.1.1-community?
August 03, 2015, 06:30:22 PM
ERROR: AcceptBlock() : rejected by synchronized checkpoint
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
Try to sync your time with basic time server "time.windows.com". Your Windows OS must not have any issues with it. Reload it,if you would have any problems. Resync again,but not run LDOGE client(Qt-wallet). When your time clock would be ok,run LDOGE Wallet. If you would have ORHANS again,resync blockchain since start: 1. Close your wallet. 2. Go to Computer-System Disc(ussually "C")-Users-AppData-Roaming-LDOGE folder. 3. Open LDOGE folder and delete all files,except wallet.dat. NOT DELETE ONLY WALLET.DAT FILE IN LDOGE FOLDER. 4. After that run LDOGE WALLET and wait end of sync. ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
I'll try some of the latter steps. If you read back I've already tried to re-sync time with multiple servers and restart the qt-client and it's not working.
EDIT: After deleting everything but the wallet file, it appears to be successfully re-syncing. Very odd that it happened right after I got 2 super-quick stakes and around the time someone was reporting a similar issue. I went over the debug log again and didn't see anything other than what's posted above.
August 03, 2015, 06:16:51 PM
ERROR: AcceptBlock() : rejected by synchronized checkpoint
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
Try to sync your time with basic time server "time.windows.com". Your Windows OS must not have any issues with it. Reload it,if you would have any problems. Resync again,but not run LDOGE client(Qt-wallet). When your time clock would be ok,run LDOGE Wallet. If you would have ORHANS again,resync blockchain since start: 1. Close your wallet. 2. Go to Computer-System Disc(ussually "C")-Users-AppData-Roaming-LDOGE folder. 3. Open LDOGE folder and delete all files,except wallet.dat. NOT DELETE ONLY WALLET.DAT FILE IN LDOGE FOLDER. 4. After that run LDOGE WALLET and wait end of sync. ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
August 03, 2015, 05:39:40 PM
ERROR: AcceptBlock() : rejected by synchronized checkpoint
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK 751, prev=13ca9fb507542ba079f0e92e3932c0f2f8a7d26c6be837692f685d2f3595213e
ProcessBlock: ORPHAN BLOCK 751, prev=57dad18911a864ac3ae90dbcb26a9f0e46124dd8ab5d0c05fed3d27c4ec5ea4c
Then about 1,000 occurrences of ORPHAN BLOCK 751
and occasionally
ERROR: ProcessBlock() : already have block (orphan)
August 03, 2015, 02:55:22 PM
Oh no, it's a real thing. A lot of POS coins have tight timedrift specifications. Meaning if your PC's clock is off by just a few seconds, your blocks will get rejected. I included a picture below. Just click on that 'update now' button to resync the clock on your PC. 95% of the time people say they are getting a lot of rejected blocks in any POS coin, this is the reason. I do it frequently on the PC that I stake coins 24/7 on. Your PC probably just automatically resynced it's clock so now you are fine, but just an FYI in case it happens again.
lol ok thanks
my pc was on time.windows.com i changed for time.nist.gov
now i'm to 4 accepted in a row
thanks
So suddenly yesterday this happened to me too. I've tried re-sycning to time.nist.gov; for a while it was showing 23h or 25h behind; now it's back to just saying "out of sync." Any additional ideas? I've left it running for several hours each time, I'm also showing minimum 8 connections to the network. It's also odd that it says its staking, but again it remains in this "out of sync" state. Last successful stake was the morning of 8/2/15.
I am not sure why this is happening. Perhaps some more info would be useful. If you don't mind, click on Help --> debug window --> then click the open button under debug log file.
If there are any errors that show up there please report them here. This could be quite useful in figuring out the issue that you are having.
August 03, 2015, 02:21:41 PM
i put the conf file, i re sync, reboot the pc (in doubt reboot) and did the clock internet changement
i have still 2 connection but so far 6 mined accepted, no rejected
i have still 2 connection but so far 6 mined accepted, no rejected
August 03, 2015, 02:12:50 PM
Oh no, it's a real thing. A lot of POS coins have tight timedrift specifications. Meaning if your PC's clock is off by just a few seconds, your blocks will get rejected. I included a picture below. Just click on that 'update now' button to resync the clock on your PC. 95% of the time people say they are getting a lot of rejected blocks in any POS coin, this is the reason. I do it frequently on the PC that I stake coins 24/7 on. Your PC probably just automatically resynced it's clock so now you are fine, but just an FYI in case it happens again.
lol ok thanks
my pc was on time.windows.com i changed for time.nist.gov
now i'm to 4 accepted in a row
thanks
So suddenly yesterday this happened to me too. I've tried re-sycning to time.nist.gov; for a while it was showing 23h or 25h behind; now it's back to just saying "out of sync." Any additional ideas? I've left it running for several hours each time, I'm also showing minimum 8 connections to the network. It's also odd that it says its staking, but again it remains in this "out of sync" state. Last successful stake was the morning of 8/2/15.
August 03, 2015, 09:56:17 AM
http://pastebin.com/LLPqB9F3 here is the conf file for LDoge hope this helps everyone it has a few nodes and how I have my wallet set up.
Keep on stakeage stakeums stake stake stake LITEDOGE Litedoge LDOGE ldoge
Keep on stakeage stakeums stake stake stake LITEDOGE Litedoge LDOGE ldoge
i resync my wallet and put this .conf
but still same i think, 1 accepted and 3 rejected
i just closed my others wallet for try but it worked well together before
i'm lost i don't understand i do nothing of special
Resync the clock on your PC.
the clock? im not good in english and cryptothing, i dont know if its a joke
but apparently i have 3 accepted in a row so may be problem is fixed
i wait until tonight before open my others wallet for stake
Oh no, it's a real thing. A lot of POS coins have tight timedrift specifications. Meaning if your PC's clock is off by just a few seconds, your blocks will get rejected. I included a picture below. Just click on that 'update now' button to resync the clock on your PC. 95% of the time people say they are getting a lot of rejected blocks in any POS coin, this is the reason. I do it frequently on the PC that I stake coins 24/7 on. Your PC probably just automatically resynced it's clock so now you are fine, but just an FYI in case it happens again.
lol ok thanks
my pc was on time.windows.com i changed for time.nist.gov
now i'm to 4 accepted in a row
thanks
August 03, 2015, 09:26:34 AM
http://pastebin.com/LLPqB9F3 here is the conf file for LDoge hope this helps everyone it has a few nodes and how I have my wallet set up.
Keep on stakeage stakeums stake stake stake LITEDOGE Litedoge LDOGE ldoge
Keep on stakeage stakeums stake stake stake LITEDOGE Litedoge LDOGE ldoge
i resync my wallet and put this .conf
but still same i think, 1 accepted and 3 rejected
i just closed my others wallet for try but it worked well together before
i'm lost i don't understand i do nothing of special
Resync the clock on your PC.
the clock? im not good in english and cryptothing, i dont know if its a joke
but apparently i have 3 accepted in a row so may be problem is fixed
i wait until tonight before open my others wallet for stake
Oh no, it's a real thing. A lot of POS coins have tight timedrift specifications. Meaning if your PC's clock is off by just a few seconds, your blocks will get rejected. I included a picture below. Just click on that 'update now' button to resync the clock on your PC. 95% of the time people say they are getting a lot of rejected blocks in any POS coin, this is the reason. I do it frequently on the PC that I stake coins 24/7 on. Your PC probably just automatically resynced it's clock so now you are fine, but just an FYI in case it happens again.
August 03, 2015, 09:01:48 AM
By the way... I'm staking like crazy!!!
How are you guys doing in staking???
Cheers!!
How are you guys doing in staking???
Cheers!!
Not good yet.. only have 2mil LDOGE. But getting there!
Jump to: