Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 127. (Read 1151252 times)

I expected this

Yes,leverage makes jump and dump.

Maybe it's because of leverage,so just pump&dump.

interesting About price
What are the reasons for the high price!
Are there advantages or is just pump/dump ?

But, I still havent finished sync my clam client.
https://i.imgur.com/zX0ubAH.png
I already have a new poloniex account, but I still don't understand how to use clam wallet.
And could you please explained it in a bit detail with what you said
"Just drag and drop your .dat with digable wallets and we'll save you the headache.  You'll get 3.5 CLAMS worth of Bitcoin @ Poloniex market cost per address.  We keep 1 CLAM for the site & .1xxx to the affiliate (or me if no affiliate.)"

Is there a noobie guide for claiming CLAMS?

Just drag and drop your .dat with digable wallets and we'll save you the headache.  You'll get 3.5 CLAMS worth of Bitcoin @ Poloniex market cost per address.  We keep 1 CLAM for the site & .1xxx to the affiliate (or me if no affiliate.)

https://freebitcoins.com/clamchecker/dig_wallet/

If you wanted to keep trouble shooting... I'd suggest -rescan.  (When it doubt, rescan it out!)

Guys, I downloaded CLAM-1.4.17 [32 bit] and got stuck when sycn. So I download bootstrap.dat
I copied it to my wallet.dat folder, when I open the client says "Importing blocks". And nothing happen since then.
Should I be connected to the internet when using bootstrap or not?
And do I need to delete my old clam data that I already sycn to make the bootstrap works?
"I already 2 years and 1 weeks behind".

Would it be a negative or a positive if Satoshi dug his/her clams?

satoshi needs to chime in here lol buying more CLAMMMMMMM WEEEEEEE

Dooglus IS satoshi fool.

Bow down and suck his Bitcoin making pecker! 

^DDOS attack or insiders desperate for coins? Regardless CLAM is a safe haven of sorts because it has legit developer dooglus who knew satoshi so... .O1 easy imho :-D

There is a strong correlation between trading Stellar and trading CLAMs on Poloniex.  Perhaps the single entity driving the price of both coins.

Here is the 1 week charts for both:

Click images for full-sized versions.

The difficulty has roughly halved since the coin price started pumping. Presumably because lots of coins moved from Just-Dice which stakes them to Poloniex which doesn't:



The all-time dig chart:



The dig chart since the 'big digger' stopped digging:



ie. there has been an uptick in digging in the last couple of weeks, but it's nothing compared to the rate at which new coins are created by staking, and nothing at all compared to the "big digger" activity.

This price is not crazy, let us wait and see.

Having a "DIG" piped into your debug file doesn't suggest that the 'dig' has anything to do with you.  
It is a common debug line which occurs any time a distribution output is moved - yours or anyone else's.  
  
If you have a transaction that is signed with your keys, but you didn't sign it, you need to take immediate security steps as the machine is compromised.  
Remove any and all crypto from any and all keys stored on that machine.  
  

---

Concerning the issue with digging, you might try expanding your key pool.  
 
Replace '###' with a suitably large number. 

Edit:
Alternatively, you could try the repairwallet command.

I didn't make one for a few months now. I'll make a new one and post it when it's ready. It'll take an hour or two I guess.

Now that the price of clams has gone bonkers, Bring back the proof of pearl lottery 

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?



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.




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.

edit: I resolved this by downloading the 32 bit wallet, backing up the previous Clam data directory and reinstalling. This time both wallets imported without issue and I have my Clams. Still curious as to what happened... Thanks again to tryphe for all the help!

-

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 let it sync fully.

Next, I 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 balance 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?