[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"

[shawn2025]

I can't seem to find that folder.  I revealed hidden folders as well.   

On OS  10.7.5

In Finder use the cmd+Shift+g keycombination and go to ~/Library/Application Support/

You rock!  Much appreciated! 

/s/

[paolo77]

hello, I'm new in the world clam, I'd like to know how do I know that I have the possibility of doing staking. is there any command you in the wallet? thanks in advance.

[omahapoker]

doing my part and helping clam get out there

[rocoro]

I'm on v1.4.4

Why is number of connections for me,  only 4 ?

Seems, always only 4.

[shawn2025]

hello, I'm new in the world clam, I'd like to know how do I know that I have the possibility of doing staking. is there any command you in the wallet? thanks in advance.

As far as I can tell you only need to leave it running and unencrypted. 
Perhaps one clam in there to be safe, but I understand it's pretty random. 
I'm learning as I go myself so if there is more to add, I hope someone will contribute. 

[omahapoker]

we need CLAM on page 1 always if you want to make it.


found this thread on page 6

[BayAreaCoins]

we need CLAM on page 1 always if you want to make it.


found this thread on page 6

Probably true, but it is the largest pay off in crypto currency.

We should push CLAM to exchange 1 for 1 with BTC and see if folks claim 

[Vortex20000]

we need CLAM on page 1 always if you want to make it.


found this thread on page 6

Probably true, but it is the largest pay off in crypto currency.

We should push CLAM to exchange 1 for 1 with BTC and see if folks claim 

1 for 1 with BTC would be CRAZYNESS!

[EGStrategies]

Clam price is extremely low right now if you value it based on the $bet volume in the first ~2 months of JD reopening, as well as future prospects for betting growth on the site given its peak popularity pre-shutdown and its relative newness as the re-opened clam dice. Leverage has upped the max a ton which should attract huge betting soon, and investors have almost all kept their clam invested despite the leverage option.


I'm not sure it's too undervalued though. I am holding, but there are a few major factors that I see as discounting the price

1. un-dug clams represent 98+% of the available clams to dig... less than 2% have been dug. Price action will motivate new digs causing sell offs in uptrends. The low dug amount currently provides a large staking interest rate to holders, but the stake stays fixed at 1 clam per minute regardless of dug clams.

2. Just-Dice could close again at some point




Ultimately JD is enough for me to be in for the long haul. It will be very interesting. Extremely low supply right now.

[NUFCrichard]

The physical clams might be in short supply, but JD is backed by paper CLAMs now, I don't know how much effect that has on the market, but I don't like it.

[Trent Russell]

Hi everyone,

A couple of weeks ago I realised I had some of these initially distributed clams so I'm trying to stake with them. I used the bootstrap file to get up-to-date in a reasonable time and did manage to stake once, so that was a good start. I'm just running clamd, not qt. I was using some 1.4.4-beta that I compiled from source on linux.

Unfortunately, I realised today that my clamd has been stuck at block 300998 (from Jan 18). Plus getinfo said my balance was 0, but fortunately that part was just wrong. I found this thread and saw a recent post that suggested looking at the debug.log file, so I did. I found error messages like

ERROR: ProcessBlock() : duplicate proof-of-stake ...

just like shawn2025 above did. Following allejuppa's suggestion above, I just restarted everything restarting from the bootstrap again. To be specific, I moved my .clam to an old directory, downloaded the latest version of clam for linux(32), created a new .clam directory and copied over (only) my clam.conf and wallet.dat files. I then put the latest bootstrap.dat in the new .clam directory. I restarted and let it run for 6 hours or so.

I think I'm now caught up and things seem to be running OK. I just wanted to confirm this kind of thing is happening and there is a somewhat time consuming way around it.

Even with the problems, I'm enjoying learning about your coin.

[dooglus]

The physical clams might be in short supply, but JD is backed by paper CLAMs now, I don't know how much effect that has on the market, but I don't like it.

"backed by paper CLAMs" is a funny way of putting it. Any CLAMs you win on Just-Dice are real CLAMs. There's no danger of winning "paper" CLAMs and not being able to withdraw them.

Interestingly, the recent change of allowing people to have only a fraction of their investment actually on deposit was the opposite of what I expected.

I thought it would allow the biggest investors to free up some of their CLAMs, possibly resulting in lots of CLAM being sold off, but what seems to be happening is that new even bigger investors are coming in now that they can have a significant stake in the site without having to convert more than a small percentage of their net worth into CLAM to do so.

Edit: oh, and the reason I came back to this thread right now was to mention that I've replaced the bootstrap.dat with a new up-to-date version. See the old post for details.

Edit2: it's been a while since I posted charts of the network difficulty over time:

[shawn2025]

Hi everyone,

A couple of weeks ago I realised I had some of these initially distributed clams so I'm trying to stake with them. I used the bootstrap file to get up-to-date in a reasonable time and did manage to stake once, so that was a good start. I'm just running clamd, not qt. I was using some 1.4.4-beta that I compiled from source on linux.

Unfortunately, I realised today that my clamd has been stuck at block 300998 (from Jan 18). Plus getinfo said my balance was 0, but fortunately that part was just wrong. I found this thread and saw a recent post that suggested looking at the debug.log file, so I did. I found error messages like

ERROR: ProcessBlock() : duplicate proof-of-stake ...

just like shawn2025 above did. Following allejuppa's suggestion above, I just restarted everything restarting from the bootstrap again. To be specific, I moved my .clam to an old directory, downloaded the latest version of clam for linux(32), created a new .clam directory and copied over (only) my clam.conf and wallet.dat files. I then put the latest bootstrap.dat in the new .clam directory. I restarted and let it run for 6 hours or so.

I think I'm now caught up and things seem to be running OK. I just wanted to confirm this kind of thing is happening and there is a somewhat time consuming way around it.

Even with the problems, I'm enjoying learning about your coin.

I did not use the bootstrap, but same here. Everything running smooth.  It's taking a day or so to stake, but I've generated a couple coins since then.  Good luck! 

[chriswen]

One thing about using the client is that you can stake your blocks right after.  I think it should stake easily because its been a long time.  While I did use the client I made the mistake of sending straight to JD.  quite unfortunate. 

[dooglus]

One thing about using the client is that you can stake your blocks right after.  I think it should stake easily because its been a long time.  While I did use the client I made the mistake of sending straight to JD.  quite unfortunate. 

I think you've got it backwards.

You seem to be saying that the coins you dig up will stake quickly because they're old, but age isn't a factor in staking, only size.

When you invest in JD you immediately start receiving a share of the staking rewards, whereas coins arriving in your own wallet won't start staking for 4 hours (if they were sent to you) or for 510 blocks (if they are immature after staking).

(The coins you send to JD also won't start staking for 4 hours, but that cost is shared between all the investors).

[equipoise]

Few months ago I created a clams wallet based on a bitcoin old wallet of mine and I got some clams. I still have the old bitcoin wallet file, but I don't have the clams wallet. I tried the same import procedure, but I got no clams this time. The clams I got the first time were not spent. Is it possible to reclaim those?

Edit: Never mind, it seems to work with file->import wallet.

[NUFCrichard]

Yeah I am using the lingo of commodities!  Everyone hates paper gold and silver keeping the prices down!
It is an interesting idea with Cryto though, and I guess on a dice betting site there won't be a short call as the profits and losses will be gradual.

The physical clams might be in short supply, but JD is backed by paper CLAMs now, I don't know how much effect that has on the market, but I don't like it.

"backed by paper CLAMs" is a funny way of putting it. Any CLAMs you win on Just-Dice are real CLAMs. There's no danger of winning "paper" CLAMs and not being able to withdraw them.

Interestingly, the recent change of allowing people to have only a fraction of their investment actually on deposit was the opposite of what I expected.

I thought it would allow the biggest investors to free up some of their CLAMs, possibly resulting in lots of CLAM being sold off, but what seems to be happening is that new even bigger investors are coming in now that they can have a significant stake in the site without having to convert more than a small percentage of their net worth into CLAM to do so.

Edit: oh, and the reason I came back to this thread right now was to mention that I've replaced the bootstrap.dat with a new up-to-date version. See the old post for details.

Edit2: it's been a while since I posted charts of the network difficulty over time:

[BitcoinINV]

after reading this thread i checked my old wallet and found some clams there

why clam wallet show virus when scanned with virustotal

[allejuppa]

why clam wallet show virus when scanned with virustotal

Clams is pretty addictive, smart scanner

[MikeCoin]

I have my old doge wallet backup but there's no doge left in them. Do I still get clams?

You don't sorry bro.