[ANN][ARG] Argentum || A New Begining || UPDATE YOUR WALLET ||

[teayudo]

I attempted again with the following steps:
1. Moved all the files/folders in the blocks folder to a folder called old.bad
2. Moved all the files/folders in the chainstate folder to a folder called old.bad
3. Moved .lock, bootstrap.dat.old, and debug.log to a folder called old.bad
4. Downloaded a fresh copy of bootstrap.dat
5. Restarted v3.11.3.1-72cf1f3 with -reindex

Once again, the bootstrap.dat import failed after block 2,388,213:

Code:

2017-05-05 19:34:39 UpdateTip: new best=7494e20b179bf472436db5d9c4a921b6dcee823189b7fc90b0d8922658da357e height=2388213 algo=1 (scrypt) log2_work=73.838186 tx=2630332 date=2017-04-26 11:31:30 progress=0.949481 cache=43.8MiB(231560tx)
2017-05-05 19:34:39 LoadExternalBlockFile: Deserialize or I/O error - ReadCompactSize(): size too large
2017-05-05 19:34:40 Loaded 2395766 blocks from external file in 24061259ms

[protonn]

My sha256 node's debug.log is filled with this

2017-05-07 03:25:55 ERROR: CheckProofOfWork(): hash doesn't match nBits
2017-05-07 03:25:55 ERROR: CheckAuxPowProofOfWork : AUX proof of work failed
2017-05-07 03:25:55 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=11, nPos=21371058)
2017-05-07 03:25:55 ERROR: CheckProofOfWork(): hash doesn't match nBits
2017-05-07 03:25:55 ERROR: CheckAuxPowProofOfWork : AUX proof of work failed
2017-05-07 03:25:55 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=11, nPos=21371706)
2017-05-07 03:25:55 ERROR: CheckProofOfWork(): hash doesn't match nBits

My scrypt node at the exact same height shows no errors.

I am having the same issue with the bootstrap only indexing to 2,388,214. Once we fix the sha256 client errors, we can just continue the blockchain from there.

[SolidStateSurvivor]

Mine is stuck at 2385249 with 7-9 nodes, going no further. 

Hmm, I guess I'll have to wait then.

[protonn]

Yesterday I had two clients with blocks and headers synced to 2390214. I created a scrypt and sha pool. When I found a sha block, it found a chain further along in block height started syncing with it. The same thing happened with the scrypt pool. After they synced, I continued mining and my windows client found the chain and synced up as well.

Here's the problem. Eventually I received this error on every client synced with the chain, and my windows client produced it's own error as well. This crashed every one of my clients that was synced with the blockchain at the time, mining or not.

:~/.argentum$ argentumd: main.cpp:4223: void ProcessGetData(CNode*): Assertion `!"cannot load block from disk"' failed

Debug.log

ERROR: CheckProofOfWork(): hash doesn't match nBits
2017-05-09 11:42:22 ERROR: CheckAuxPowProofOfWork : non-AUX proof of work failed
2017-05-09 11:42:22 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=5, nPos=122908179)

What I can't figure out is why it won't just reject the bad block and move on, like its supposed to do. It appears that its first writing the bad block to the blockchain then rejecting it, which corrupts your local copy of the blockchain until a reindex is done where it will finally discard the bad block as its supposed to. Until a reindex is done, i get the Assertion which crashed every client connected and synced with it.

[teayudo]

I've received the same errors, but keep restarting the client with -reindex. After several of those, I've now gotten up to block 2392566. When it gets stuck, I just do another -reindex.

[IconFirm]

My client is also getting stuck constantly. I think the problem is something to do with the scrypt code:

Code:

"difficulty_scrypt" : 13479767645505657739733591426051172149151986772234706298418734563328.00000000

crazy diff......

[protonn]

My client is also getting stuck constantly. I think the problem is something to do with the scrypt code:

Code:

"difficulty_scrypt" : 13479767645505657739733591426051172149151986772234706298418734563328.00000000

crazy diff......

You shouldn't have that problem on 3.11.3.1. You are on a bad fork.

[IconFirm]

My client is also getting stuck constantly. I think the problem is something to do with the scrypt code:

Code:

"difficulty_scrypt" : 13479767645505657739733591426051172149151986772234706298418734563328.00000000

crazy diff......

You shouldn't have that problem on 3.11.3.1. You are on a bad fork.

Oops, my bad. Just updated my wallets to latest version - now they're all stuck at 2387837 after reindexing.

[protonn]

My client is also getting stuck constantly. I think the problem is something to do with the scrypt code:

Code:

"difficulty_scrypt" : 13479767645505657739733591426051172149151986772234706298418734563328.00000000

crazy diff......

You shouldn't have that problem on 3.11.3.1. You are on a bad fork.

Oops, my bad. Just updated my wallets to latest version - now they're all stuck at 2387837 after reindexing.

I believe I have a fix now, and I'll also present a proposal (for the future.) Give me a few days. Very busy life right now

[IconFirm]

My client is also getting stuck constantly. I think the problem is something to do with the scrypt code:

Code:

"difficulty_scrypt" : 13479767645505657739733591426051172149151986772234706298418734563328.00000000

crazy diff......

You shouldn't have that problem on 3.11.3.1. You are on a bad fork.

Oops, my bad. Just updated my wallets to latest version - now they're all stuck at 2387837 after reindexing.

I believe I have a fix now, and I'll also present a proposal (for the future.) Give me a few days. Very busy life right now

Cool, no stress. life is important.....

[aatheus]

My client is also getting stuck constantly. I think the problem is something to do with the scrypt code:

Code:

"difficulty_scrypt" : 13479767645505657739733591426051172149151986772234706298418734563328.00000000

crazy diff......

You shouldn't have that problem on 3.11.3.1. You are on a bad fork.

Oops, my bad. Just updated my wallets to latest version - now they're all stuck at 2387837 after reindexing.

I believe I have a fix now, and I'll also present a proposal (for the future.) Give me a few days. Very busy life right now

Thanks in advance, protonn!

[aatheus]

Killed the client, reindexed again with 'argentumd -reindex'. Now it's syncing!

2017-05-11 21:31:02 UpdateTip: new best=a10c542cead92d473e1de12b3a59f253796f1ca18b91dcfb7fa3febd45add28a height=2392617 algo=1 (scrypt) log2_work=73.838247 tx=2635407 date=2017-05-11 21:31:00 progress=1.000000 cache=23.3MiB(104340tx)
2017-05-11 21:31:21 UpdateTip: new best=126f1d9b537eac3e65cf6fabf4c50cf69b21f756be8eecb7c6f2b751f0b7df4b height=2392618 algo=1 (scrypt) log2_work=73.838247 tx=2635408 date=2017-05-11 21:31:02 progress=0.999999 cache=23.3MiB(104341tx)
2017-05-11 21:31:40 UpdateTip: new best=00000000000061c20e1e524f97cc47d569c3de1f49487ada32ae701fb0efa35c height=2392619 algo=0 (sha256d) log2_work=73.838247 tx=2635409 date=2017-05-11 21:31:21 progress=0.999999 cache=23.3MiB(104342tx)
2017-05-11 21:31:41 UpdateTip: new best=83d1ddc4ba6955dea53aef983a58466080d4a53844fab0271628447e88f24001 height=2392620 algo=1 (scrypt) log2_work=73.838247 tx=2635410 date=2017-05-11 21:31:41 progress=1.000000 cache=23.3MiB(104343tx)

[protonn]

Looks like my fix is working as expected so far. Release coming soon. You might experience issues with your individual client until on the new version.

[IconFirm]

Looks like my fix is working as expected so far. Release coming soon. You might experience issues with your individual client until on the new version.

Well done protonn, nice work. Let me know when we're good to do a git pull & I'll compile & test.

[protonn]

Looks like my fix is working as expected so far. Release coming soon. You might experience issues with your individual client until on the new version.

Well done protonn, nice work. Let me know when we're good to do a git pull & I'll compile & test.

Right now

Source for everyone else.

https://github.com/argentumproject/argentum

Binaries coming a bit later on.

[protonn]

Windows and MacOS

https://github.com/argentumproject/argentum/releases/

[KorbinDallas]

It appears that exchanges are also experiencing issues with syncing the Argentum blockchain - Right now I can't find a single one that is actively trading; Cryptopia and Coinexchange.io are both unable to sync. 

Not screaming for a change, just spreading the news so Devs are aware 

cheers!

[protonn]

It appears that exchanges are also experiencing issues with syncing the Argentum blockchain - Right now I can't find a single one that is actively trading; Cryptopia and Coinexchange.io are both unable to sync.  

Not screaming for a change, just spreading the news so Devs are aware  

cheers!

Thanks

All exchanges have been notified.

NovaExchange has updated. Still waiting for a response from the others. My guess is tomorrow.

[Vilrex]

Why did this coin die?

[protonn]

Why did this coin die?

https://chainz.cryptoid.info/arg/

It originally died with the cryptsy scandal. Cryptcollector brought it back from the dead.