i quit - page 55. | Bitcointalksearch.org

Pepijn

newbie

Activity: 36

Merit: 0

Quote from: mellon on April 16, 2015, 05:45:52 PM

Quote from: MinerFTW on April 16, 2015, 05:28:18 PM

im rebaseing wallets. think i did all from original hash/genesis etc now going into pics / logo's etc

I'm wait your answer Miner. Plz check the thread.

@MinterFTW - Please go easy with mellon. He has been contributing much to the community. Due to his limited English he was not able to ask nicely. He was asking for your help. Looks like complete misunderstanding between you two.

Glad the original dev is back.

luongdk

full member

Activity: 686

Merit: 102

Quote from: antzz on April 17, 2015, 12:16:27 AM

now my block stop @ 43888
block expl now @43896

something wrong again...

Only if your block is faster than explorer, it fork issue. For your case, maybe you should check your network connection.

antzz

member

Activity: 62

Merit: 10

now my block stop @ 43888
block expl now @43896

something wrong again...

romancingthecoin

newbie

Activity: 2

Merit: 0

Quote from: MinerFTW on April 17, 2015, 12:06:55 AM

no daemon is only for headless clients.

I never send messages on bitcointalk but I have been watching this nightmare and you might have saved this coin. I just wanted to say thank you, you much the man! Grin

MinerFTW

sr. member

Activity: 462

Merit: 250

no daemon is only for headless clients.

Josevv

member

Activity: 146

Merit: 10

Thanks, now is working.

I made my litedoge file with that text, but I did not write "daemon=1" is that important?

Lorren

full member

Activity: 144

Merit: 100

Quote from: Josevv on April 16, 2015, 10:38:09 PM

Quote from: MinerFTW on April 16, 2015, 10:29:23 PM

Quote from: antzz on April 16, 2015, 10:21:14 PM

have new wallet and add the new nodes...
hope this will work...
tq guys for your work in this coin...

sync 4563...
cheers...

i don't know if it really matters but please use also listen=0 in conf and connect to those 2 ip only.

that reduce chance of forking i think.

I am noob, I dont know how to add nodes or how to use "listen=0" lol... I know that my wallet is not working....what must I do?

Were you able to figure it out? If not, hopefully I can be of help.

If you are using windows, there should be a folder in your computer called Litedoge under C:\Users\\AppData\Roaming\ (be sure that you are showing hidden files and folders or you won't be able to see AppData). Go there.

You'll want to delete all of the files except wallet.dat. Never Delete wallet.dat!!!!. To be extra cautious, I even create a copy of wallet.dat and put it in a different place when I'm fiddling with these things.

Create a text file. Put the following things in it:

daemon=1
listen=0
addnode=93.157.4.11
addnode=91.121.6.19

No need to put anything else in it at the moment. That's currently what my file looks like (although I currently have been too lazy to add the second node at the moment).

Save the file in the Litedoge folder (above) and name it litedoge.conf .

Now you can start the wallet, resync, and it should work. :-)

Josevv

member

Activity: 146

Merit: 10

Quote from: Josevv on April 16, 2015, 11:35:15 PM

Quote from: MinerFTW on April 16, 2015, 11:30:06 PM

do you see only 2 connections?

Yes, but now I am trying with new wallet...Sorry I did not know there was a new wallet.

I sync to block 43871 and now I can see "block 43876" in my wallet, I make a new block and It has 5 confirmations so... Thank you!!!

MinerFTW for president! Wink

antzz

member

Activity: 62

Merit: 10

Quote from: MinerFTW on April 16, 2015, 11:49:52 PM

np yw.

when you do next code change version and kick old nodes. i think that is causing forks when ppl get info from older forked chains.

can be set in version.h and version.cpp

done...
sync with block expl now
begin staking again..
thx alot

MinerFTW

sr. member

Activity: 462

Merit: 250

np yw.

when you do next code change version and kick old nodes. i think that is causing forks when ppl get info from older forked chains.

can be set in version.h and version.cpp

aquitasIJ

member

Activity: 112

Merit: 10

Quote from: luongdk on April 16, 2015, 11:26:04 PM

Ok, now I have all information and can explain everything here. Sorry for my bad English if you cannot understand what I mean.

At first, after block 40k, everything went wrong because of each wallet generated wrong chain itself and do not keep up with explorer and network -> many version of chain.

After few day after, Dev blinked in (very lazy dev, I am blaming you) and sync his checkpoint server with explorer (via my wallet). He also released fix version of wallet about the checkpoint. Then PoS was working smoothly for 1-2 hours til dev's crap checkpoint server down again while he blinked out.

Today, dev gives MinerFTW checkpoint privatekey. The checkpoint server is stayed with MinerFTW and is working smoothly now and so on (will be). But fork again after few try because of many obsolete, wrong chain nodes are still out there, keeping "poising" each other.

Finally, MinerFTW found out, if we put the entry listen=0 to .conf file, the wallet connect to correctly node only. To fix everything, follow my steps bellow:

Step 1: Download new wallet at first post

Step 2: Clean %appdata%\roamming\LiteDoge except wallet.dat (DO NOT DELETE WALLET.DAT IN ANY CASE)

Step 3: Create litedoge.conf and add bellow entries

Quote

addnode=91.121.6.19
addnode=93.157.4.11
listen=0

Step 4: Run wallet and wait for synced up (should have 2 connections)

Step 5: Unlock wallet to begin stake

Good luck everyone!

Thank you for making this post.
And thank you MinerFTW for helping.

MinerFTW

sr. member

Activity: 462

Merit: 250

no worries its a little bit a clusterF

eventually we will get where we must be. all those nice ppl helping out is really cool to see. Like Luong's post that should be made sticky

Josevv

member

Activity: 146

Merit: 10

Quote from: MinerFTW on April 16, 2015, 11:30:06 PM

do you see only 2 connections?

Yes, but now I am trying with new wallet...Sorry I did not know there was a new wallet.

MinerFTW

sr. member

Activity: 462

Merit: 250

do you see only 2 connections?

Josevv

member

Activity: 146

Merit: 10

Quote from: antzz on April 16, 2015, 10:54:45 PM

Quote from: luongdk on April 16, 2015, 10:51:41 PM

Quote from: antzz on April 16, 2015, 10:36:56 PM

Quote from: luongdk on April 16, 2015, 10:35:16 PM

Quote from: antzz on April 16, 2015, 10:34:19 PM

Quote from: MinerFTW on April 16, 2015, 10:29:23 PM

Quote from: antzz on April 16, 2015, 10:21:14 PM

have new wallet and add the new nodes...
hope this will work...
tq guys for your work in this coin...

sync 4563...
cheers...

i don't know if it really matters but please use also listen=0 in conf and connect to those 2 ip only.

that reduce chance of forking i think.

tq bro... if we use original wallet and just change the node... is it working?

Nope, you have to resync

so we must use new fixed wallet?

Yes It's better to to use new fix wallet

- Download new wallet
- Clean %appdata%\roamming\LiteDoge except wallet.dat
- Create litedoge.conf and add bellow entries

Quote

addnode=91.121.6.19
addnode=93.157.4.11
listen=0

- Run wallet and wait for synced up
- Unlock wallet to begin stake

tq ... hope this will work...

I resync and I was in block 43842 more than 15 minutes... and now I make two blocks 43843 and 43844... the problem is we are in block 43850, so, I think my wallet is broken yet...

luongdk

full member

Activity: 686

Merit: 102

Ok, now I have all information and can explain everything here. Sorry for my bad English if you cannot understand what I mean.

At first, after block 40k, everything went wrong because of each wallet generated wrong chain itself and does not keep up with explorer and network -> many version of chain.

Few days after, Dev blinked in (very lazy dev, I am blamming you) and sync his checkpoint server with explorer (via my wallet). He also released fix version of wallet about the checkpoint. Then PoS was working smoothly for 1-2 hours til dev's crappy checkpoint server down again while he blinked out.

Today, dev gives MinerFTW checkpoint privatekey. The checkpoint server is stayed with MinerFTW and is working smoothly now and so on (will be). But fork again after few try because of many obsolete, wrong chain nodes are still out there, keeping "poising" each other.

Finally, MinerFTW found out, if we put the entry listen=0 to .conf file, the wallet connects to correct nodes only. To fix everything, follow my steps bellow:

Step 1: Download new wallet at first post

Step 2: Clean %appdata%\roamming\LiteDoge except wallet.dat (DO NOT DELETE WALLET.DAT IN ANY CASE)

Step 3: Create litedoge.conf and add bellow entries

Quote

addnode=91.121.6.19
addnode=93.157.4.11
addnode=183.91.4.3
listen=0

Step 4: Run wallet and wait for synced up (should have 2-3 connections)

Step 5: Unlock wallet to begin stake

Good luck everyone!

------
EDIT: Add my node before listen=0

Quote

addnode=183.91.4.3

MinerFTW

sr. member

Activity: 462

Merit: 250

if my suspicion is right about the reason it can fork off. then we can make a more stable less hassle fix i think.

Majority of this community is really great. i am happy i can contribute to help you guys out

antzz

member

Activity: 62

Merit: 10