I wanted to give an update on my observations this morning and see if I can get any feedback.
Yesterday I did the zapwallettxes=1 command and rebooted the PC and HOdl wallet.
After that transactions (sent coins) and mined coins and locked coins literally disappeared from the wallet however I was able to begin mining.
This morning I can see that I've mined blocks but a whole lot of weird stuff is going on for example...
If I send HOdl coin to an address it shows as being fully sent and confirmed from the sending wallet however it never arrives at the wallet I sent it to. Also, if I take the transaction ID from that send and search for it in the block explorer it doesn't exist and literally those sent coins have vanished.
On this same PC I did an experiment and I am able to HOdl coins for a term deposit but when I HOdl'ed just 1 coin it immediately produced a transaction for 49 coins or basically the balance of a block reward.
This same PC claims to be connected to 8 other nodes and oddly on the block explorer the IP shows up on the node list.
All of this is just mind blowing and it gives me the impression that there are different blockchains running for this coin and those are disconnected from each other.
What will be the end result of all of this and how long will it take to get sorted out?
I would appreciate any feedback or suggestions from the forum members.
I think there are still nodes that haven't upgraded to v3 - and so are likely on a different chain. Make sure you're on v3 and try a re-index on all your clients.
@freetrade this is definitely on v3 but of course not on the latest since the binaries aren't released yet. When you say re-index the clients what is the best procedure to do that?
Update: Ok I did a -reindex and also a -rescan and no change whatsover. Do I need to delete everything except the wallet.dat, reinstall and start over or can I somehow delete the entire block chain and just reload that?
You might also be seeing this issue -
https://github.com/HOdlcoin/HOdlcoin/issues/63DF, can you check the two nodes - see if they are both on the same block, and if the hashes of those blocks are the same, and if the nodes connected are primarily v3 nodes.
No sir I can't I deleted the blockchain folders and re-downloaded. After that I was able to send HOdl to Coinexchange.IO with no problems.
I can tell you that before I made changes earlier today these nodes were NOT on the same block number that was showing in the Fuzzbawls block explorer.
I have a suggestion although it may be far-fetched....
If a Version 2.0 was connected at the V3 fork and stayed connected it continued to mine blocks although I assume on a different blockchain.
Because that V2 node never disconnected and it was still connected to V3 nodes it corrupted their blockchains.
Crazy idea or what?
Oh yeah let me edit this and add one other odd observation. When I ran -reindex the problem persisted however when I deleted the blockchain folders and re-downloaded I was fixed.
Here is a record from the receiving node on the failed sending transactions:
Status: conflicted
Date: 6/8/2017 10:13
From: unknown
To: HCtWb7De1PEpRcPZ1UX1K7Vx9DEfSoHHAL (own address, label: From Miners 6-8-2017)
Credit: 44.00077004 HODL
Net amount: +44.00077004 HODL
Transaction ID: 12cc68a1c17589a578615a0faa945ab198442260b507b3c46684846b478898ea-000
Status: conflicted
Date: 6/8/2017 10:12
From: unknown
To: HCtWb7De1PEpRcPZ1UX1K7Vx9DEfSoHHAL (own address, label: From Miners 6-8-2017)
Credit: 5.00000000 HODL
Net amount: +5.00000000 HODL
Transaction ID: f36e30016114a5c87cba3a81f6105d106d6c163dbe37fbde9f9f0cea66238e6c-000
Status: conflicted
Date: 6/8/2017 10:08
From: unknown
To: HCtWb7De1PEpRcPZ1UX1K7Vx9DEfSoHHAL (own address, label: From Miners 6-8-2017)
Credit: 1.00000000 HODL
Net amount: +1.00000000 HODL
Transaction ID: b3906fad40edc498d98b90a592b2dd3bebddbceb021ebcf044201cea571f83d6-000
Status: conflicted
Date: 6/8/2017 09:02
From: unknown
To: HCtWb7De1PEpRcPZ1UX1K7Vx9DEfSoHHAL (own address, label: From Miners 6-8-2017)
Credit: 650.03835272 HODL
Net amount: +650.03835272 HODL
Transaction ID: e1042333a84d1fdb5794d626a0d65296639ea13025516cb12d38d6045cd618d4-000