Quote from: Sir Lagsalot on May 08, 2017, 06:46:55 PM

I'm having an issue with digging. I dug 2 valid (afaik) wallet files but received no clams. However, several addresses entered from this same wallet on the FreeBitcoins.com site were shown as diggable, and I just dug one address via that site (https://freebitcoins.com/clamchecker/digs/fcc24c32fc8a2d6e96af82bcd4de5d4a23c8257332844d08ffb1e10317942fb4/) - still waiting on payment but it seemed successful.

I downloaded Clams Client (clam-1.4.17-win64.zip - SHA256 E1206F....D492) yesterday from the GitHub link on the CLAMclient.com site. I then downloaded the bootstrap file (SHA256 checksum matched) and tried to import both an old Bitcoin and Litecoin wallet.dat. Although the wallets held addresses used before May 2014, no Clams were received in my wallet, which shows 0 balances and no visible transactions. I tried both digging both wallets multiple times, both via Import File in the wallet and from the importwallet command in the wallet's console. The console gave no output after running the importwallet command, just a red minus line with no text. The receive tab in my wallet displays a bunch of importwallet addresses, none of which match the addresses in the debug.log file.

I spoke to tryphe in #clams on freenode, he was very helpful but we weren't able to resolve the issue. He told me to examine the debug.log file and I found about 20 DIG entries. The weird thing is these entries link to transactions which occurred arround the time I was digging but lead to addresses not under my control (or at least not visible in the receive tab of my client). From the comments on clamsight, it looks like some of these addresses were dug via freebitcoins.com, others via a wallet, and most of them were spent to an exchange.

I'm really confused, can anyone help me understand what's going on here?

Just to clarify things a bit more, Sir Lagsalot seems to have taken the proper precautions when digging and didn't enter any private keys online. What makes the situation peculiar is these transactions signed by his keys:

http://clamsight.com/tx/73ea5b1acd26a477af250e5bd97d7336751598e2f89aac0ef0c2feeacf9c7f4b#i0
http://clamsight.com/tx/0f4cb75614432bca313a7a3b70aa658d8b2d3f83e494fa3009b71411475f9419#o0

which he claims he did not make. To make it even weirder; one is from freebitcoins.com, and one is from a clam wallet. None of those addresses that the coins got sent to are his exchange/wallet addresses. He also claims that the wallet was encrypted since inception, and given all his keys aren't emptied (they are now, as a precaution), I'm not really sure what to think.

Any ideas?

Quote from: bigsky101 on May 08, 2017, 06:31:27 PM

I've installed v1.4.17 for Linux and am running the console via ./clam-qt

I am only getting 2 peers. I'm wondering if there are nodes I can add to my clam.conf? I've looked around and the info seems to be pretty old and ineffective.

I've also added bootstrap.dat files in my ./clam folder posted by dooglus elsewhere here but that doesn't really address the lack of peers or will it when I catch up?

Thanks in advance.

It doesn't really matter how many peers you have during the bootstrap process. Once it completes, you will have more peers. If you really want a lot of connections, you should open the port, otherwise no one can directly connect to you.

If it seems like it's stuck and not loading the bootstrap (the disk should be swamped while bootstrapping), try restarting the client with '--connect=localhost' in the args, and it should work properly. At some point, it will become 98%+ synced, and you can remove those args.

Quote from: almightyruler on May 08, 2017, 10:25:07 AM

I left CLAM alone for about 80 days, then restarted it a few days ago - and it's still trying to sync...

The debug log is full of "already have block" and "ORPHAN BLOCK 751" entries.

2017-05-08 10:22:14 SetBestChain: new best=e14bb9bc8557e99af05120468920505f7c1208fdb321a9124e41234659fd420a height=1486871 trust=466372186589834826465 blocktrust=338273748876064 date=04/28/17 01:14:40 2017-05-08 10:22:26 ERROR: ProcessBlock() : already have block 1486871 e14bb9bc8557e99af05120468920505f7c1208fdb321a9124e41234659fd420a 2017-05-08 10:22:26 ERROR: ProcessBlock() : already have block 1486871 e14bb9bc8557e99af05120468920505f7c1208fdb321a9124e41234659fd420a 2017-05-08 10:22:30 ERROR: ProcessBlock() : already have block 1486871 e14bb9bc8557e99af05120468920505f7c1208fdb321a9124e41234659fd420a

Here's a random but typical example. The same block was received four times over a period of 16 seconds.

Why are peers sending blocks multiple times, and seemingly (due to all the orphan blocks) out of order?

It's taken 3 or 4 days just to advance the blockchain by a couple of months. Any further work on fixing this?

Check out the bootstrap. It will get you caught up, which avoids most of the orphan nonsense. I wrote a bit of a how-to here: https://www.reddit.com/r/Clamcoin/comments/5z5x77/sync_issue/
(sorry for the piggy-back links)

As for fixing the issue: yes, it's a problem. None of us have been able to pinpoint the root cause, and since it doesn't happen when caught up to the chain, it's been put on the backburner. Eventually the issue was condensed into this one: https://github.com/nochowderforyou/clams/issues/294

Anyone is feel free to help if they're familiar with the block indexing code, and would get some clams thrown their way if they fixed it.