Topic: i quit - page 44. (Read 142559 times)
Happy Puppy or need to see the Vet. again? Looks happy...
second pos reward and still no fork with my conf, i will not touch anything for now, works fine 
Thx for the help !
Thx for the help !
alright, i renamed my conf file "litedoge-qt.conf" instead of "litedoge.conf", so my conf file is not used i guess, but it seems to work.
Had my first pos reward, and no fork, still synced to the explorer (http://www.sooncoin.com/litedogeex/block_crawler.php) chain.
My pos reward appears on the explorer, but without the right conf file, if it can help others...
What does it mean ?
Had my first pos reward, and no fork, still synced to the explorer (http://www.sooncoin.com/litedogeex/block_crawler.php) chain.
My pos reward appears on the explorer, but without the right conf file, if it can help others...
What does it mean ?
lucky stroke
close the wallet and restart it, so it will have only two connections
if your wallet listens to a node that is forked, it will fork too
alright, i renamed my conf file "litedoge-qt.conf" instead of "litedoge.conf", so my conf file is not used i guess, but it seems to work.
Had my first pos reward, and no fork, still synced to the explorer (http://www.sooncoin.com/litedogeex/block_crawler.php) chain.
My pos reward appears on the explorer, but without the right conf file, if it can help others...
What does it mean ?
Had my first pos reward, and no fork, still synced to the explorer (http://www.sooncoin.com/litedogeex/block_crawler.php) chain.
My pos reward appears on the explorer, but without the right conf file, if it can help others...
What does it mean ?
15 min ago i named the conf file exactly the same than the exe, since no pos reward every 2min (still not a single one for now ), 22 active connections, and same block than the explorer, stay tuned
), 22 active connections, and same block than the explorer, stay tuned config file must have the name litedoge.conf
and with listen=0, you can't have 22 connections, you must be getting only two (the 2 nodes added in the conf file)
you are probably going to fork, if you haven't already
15 min ago i named the conf file exactly the same than the exe, since no pos reward every 2min (still not a single one for now ), 22 active connections, and same block than the explorer, stay tuned
), 22 active connections, and same block than the explorer, stay tuned I followed instructions, i'm using the last exe and did the right conf file, when i use the "repairwallet" command i have this message : "wallet check passed" : true
I guess its good, but when i try to stack, i fork again
I guess its good, but when i try to stack, i fork again
that's above my paygrade.....
txid of your block doesn't appear on block crawler?
I followed instructions, i'm using the last exe and did the right conf file, when i use the "repairwallet" command i have this message : "wallet check passed" : true
I guess its good, but when i try to stack, i fork again
I guess its good, but when i try to stack, i fork again
What is the new wallet version? I installed the wallet again a few days ago to try to fix problems I have been having and just noticed you guys recommend running "repairwallet" This is what I get.

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)
download the latest from the 1st page
I was getting the same message a couple of days ago, updating wallet fixed the problem
current block is #46719
What block should I be on?
What is the new wallet version? I installed the wallet again a few days ago to try to fix problems I have been having and just noticed you guys recommend running "repairwallet" This is what I get.

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)

Safe mode: WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)
Follow the steps:
1) download the new wallet (see page 1)
2) update your config file (config must read only):
addnode=93.157.4.11
addnode=91.121.6.19
listen=0
3) Delete all your old files, except wallet.dat
4) Run "repairwallet" in Help/debug window/console
5) unlock wallet
6) POS
1) download the new wallet (see page 1)
2) update your config file (config must read only):
addnode=93.157.4.11
addnode=91.121.6.19
listen=0
3) Delete all your old files, except wallet.dat
4) Run "repairwallet" in Help/debug window/console
5) unlock wallet
6) POS
staking made me fork again, have i to wait until the fork ?
then you are very unlucky
I haven't forked even before the last fix, for the past 16 hours
all my stakes are currently accepted
What's your config looking like?
Any advice for others?
unfortunately, nothing different than what is posted
if I was using something different and worked, I would let you all know
last fork I had was on 17/4 22:05
are the new wallet graphics/logo not included yet?
They are in the wallet now.ok done. now waiting for staking (hopefully not storking again
) are the new wallet graphics/logo not included yet?
They are in the wallet now.
are the new wallet graphics/logo not included yet?
staking made me fork again, have i to wait until the fork ?
then you are very unlucky
I haven't forked even before the last fix, for the past 16 hours
all my stakes are currently accepted
Follow the steps:
1) download the new wallet (see page 1)
2) update your config file (config must read only):
addnode=93.157.4.11
addnode=91.121.6.19
listen=0
3) Delete all your old files, except wallet.dat
4) Run "repairwallet" in Help/debug window/console
5) unlock wallet
6) POS
1) download the new wallet (see page 1)
2) update your config file (config must read only):
addnode=93.157.4.11
addnode=91.121.6.19
listen=0
3) Delete all your old files, except wallet.dat
4) Run "repairwallet" in Help/debug window/console
5) unlock wallet
6) POS
staking made me fork again, have i to wait until the fork ?
here we go again...
staking made me fork again, have i to wait until the fork ?
One observation: there is Cryptsy on the roadmap but I can't see any Litedoge in there
Jump to: