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

[dooglus]

xploited recently brought it to my attention that the CLAM network difficulty was through the floor. I plotted it to confirm, and he's right:



It turns out that the wallet Just-Dice is using to stake recently hit 300MB in size, and is now pausing to write something to disk for 90 seconds after each stake, which prevents it from staking more than once per 90 seconds.

I have made a new staking wallet, and am in the process of moving the coins over to the new address.

The coins won't start trying to stake again until 4 hours after they were moved, so we can expect difficulty to decrease further.

This is good news for people solo-staking. You should see your wallet staking much more than you're used to.

Normal service at Just-Dice will be resumed as soon as possible.

Edit: This is the address I'm moving the coins into. The chart looks funny:



http://www.presstab.pw/phpexplorer/CLAM/address.php?address=xJDCLAMZPRxN7YHfRQmyq7rho8EBSYkDFQ

Edit2: I've got most of the coins moved over to the new staking wallet now. The only ones I can't move yet are the ones which staking within the last 8 hours and so are currently still maturing:

[1713860636]

1713860636

[1713860636]

1713860636

[gjhiggins]

This is good news for people solo-staking. You should see your wallet staking much more than you're used to.

Confirmed, my solo-staking wallet just staked 3 CLAMS in the last 2 days, it's usually ~3 a month.

Cheers,

Graham

[dooglus]

Difficulty is back to normal. I expect it will overshoot and take a while to get back to its usual pattern.

[presstab]

Edit: This is the address I'm moving the coins into. The chart looks funny:



http://www.presstab.pw/phpexplorer/CLAM/address.php?address=xJDCLAMZPRxN7YHfRQmyq7rho8EBSYkDFQ

cheezus riced that is ugly.... I will work on straightening that chart out.

[dooglus]

I see the difficulty got straight back into its old range, no overshoot:

[zy0n]

Anybody that has any private keys that are able to be dug, willing to test out a website let me know.

[dooglus]

Anybody that has any private keys that are able to be dug, willing to test out a website let me know.

I expect anyone who knows about CLAM and had access to funded private keys will have dug them up already.

[zy0n]

Anybody that has any private keys that are able to be dug, willing to test out a website let me know.

I expect anyone who knows about CLAM and had access to funded private keys will have dug them up already.

I like to think optimistically the search continues...

[forzendiablo]

after fight with snails guy not sure where this will go

[wtfonly16]

how the fuk u mine this?>?

[andulolika]

how the fuk u mine this?>?

You dont mine it you stake it since its a POS coin.
To learn more about proof of stake check OP or FAQ of just-dice.com

This guy is making mobile staking wallets : 
https://bitcointalk.org/index.php?topic=1065204.0
The cost is two BTC so i tought maybe the community would do a crowdfunding.
This address is owned by SebastianJu that will act as escrow for the funds to be raised
18Me4dCRBPvHQnuqsQPFWzcGTnJsUHpa1E
Also he left this jd uid for clams 1418619.

Edit: Seems that price is reduced to 1 btc, i kinda missed it, total crowdfund should be of 1.025 btc so we can cover little for seba too.

^

[dooglus]

Hi guys, i was searching some technical info about clam but can't find what i was searching, i have some questions:

How to calculate clam fees?

For this transaction i had to pay 0.02 1733a6aa80719165161872a751e83ae98c5624c1f8ce28c5b6e7dd1c7baa6dfc
and for this other one i pay 0.01 48348338da41f9d5243a4050c9cfadfadecd185454dd00851f810a0d87fb9b5c

But most of the transactions use 0.0001

The fees are by default 0.0001 CLAM per 1000 bytes (or part thereof). So a tx of 1000 bytes pays 0.0001 and a tx of 1001 bytes pays 0.0002, because it uses a part of the 2nd 1000 bytes.

It looks like you have your wallet set to pay 0.01 per 1000 bytes. Do you see 'fee' somewhere in your clam.conf?

Your 0.02 fee transaction is 1606 bytes, and the 0.01 fee transaction is less than 1000 bytes, so it's not surprising that one pays twice as much as the other. The only issue is why you're paying 100 times more than the default.

Edit: if you run the Qt version, check in 'Options', in the 'Main' tab. There's a setting "pay transaction fee". Mine's set to zero and I end up paying the default 0.0001 per 1000 bytes I think. What's yours set to?

I know there is a bitcoin equation to know the transaction size and that way calculate fees for btc (180*in+34*out), is there something like this for clam?

It should be the same for CLAM, except that pay-to-pubkey transactions are more common in CLAM, which makes inputs take a different number of bytes.

The clam network have grow and i would like to know how much clams i can stack if i have, 500, 1,000 or 10,000.

I usually answer this question by looking at how much JD is staking.

JD has 1180k CLAM and stakes about 1150 CLAM per day. So each 1000 CLAMs stakes a little less than 1 per day on average.

[seoincorporation]

Hi guys, i was searching some technical info about clam but can't find what i was searching, i have some questions:

How to calculate clam fees?

For this transaction i had to pay 0.02 1733a6aa80719165161872a751e83ae98c5624c1f8ce28c5b6e7dd1c7baa6dfc
and for this other one i pay 0.01 48348338da41f9d5243a4050c9cfadfadecd185454dd00851f810a0d87fb9b5c

But most of the transactions use 0.0001

The fees are by default 0.0001 CLAM per 1000 bytes (or part thereof). So a tx of 1000 bytes pays 0.0001 and a tx of 1001 bytes pays 0.0002, because it uses a part of the 2nd 1000 bytes.

It looks like you have your wallet set to pay 0.01 per 1000 bytes. Do you see 'fee' somewhere in your clam.conf?

Your 0.02 fee transaction is 1606 bytes, and the 0.01 fee transaction is less than 1000 bytes, so it's not surprising that one pays twice as much as the other. The only issue is why you're paying 100 times more than the default.

Edit: if you run the Qt version, check in 'Options', in the 'Main' tab. There's a setting "pay transaction fee". Mine's set to zero and I end up paying the default 0.0001 per 1000 bytes I think. What's yours set to?

I know there is a bitcoin equation to know the transaction size and that way calculate fees for btc (180*in+34*out), is there something like this for clam?

It should be the same for CLAM, except that pay-to-pubkey transactions are more common in CLAM, which makes inputs take a different number of bytes.

The clam network have grow and i would like to know how much clams i can stack if i have, 500, 1,000 or 10,000.

I usually answer this question by looking at how much JD is staking.

JD has 1180k CLAM and stakes about 1150 CLAM per day. So each 1000 CLAMs stakes a little less than 1 per day on average.

Thanks for your reply dooglus, Now is all clear for me. Have a great week. 

[romjpn]

Anyone noticed that khashier.com and CLAMS are listed as a scam there ? http://www.badbitcoin.org/thebadlist/index.htm#K
I think they don't understand how does it works right ?

[dooglus]

Anyone noticed that khashier.com and CLAMS are listed as a scam there ? http://www.badbitcoin.org/thebadlist/index.htm#K
I think they don't understand how does it works right ?

I hadn't noticed that. That's quite funny. khasier.com is nothing but a block explorer as far as I know. It doesn't ask for your private keys in any way.

badbitcoin.org is run by a guy who continued promoting and defending scrypt.cc and GAW/Paycoin well after they were known to be scams.

See https://bitcoinnewsmagazine.com/badbitcoin-org-gives-bad-bitcoin-advice/ for example.

Not the sharpest tool in the box...

[romjpn]

Anyone noticed that khashier.com and CLAMS are listed as a scam there ? http://www.badbitcoin.org/thebadlist/index.htm#K
I think they don't understand how does it works right ?

I hadn't noticed that. That's quite funny. khasier.com is nothing but a block explorer as far as I know. It doesn't ask for your private keys in any way.

badbitcoin.org is run by a guy who continued promoting and defending scrypt.cc and GAW/Paycoin well after they were known to be scams.

See https://bitcoinnewsmagazine.com/badbitcoin-org-gives-bad-bitcoin-advice/ for example.

Not the sharpest tool in the box...

Yes I knew for the GAW stuff. I followed it pretty close and for a while, thought the mining venture still looked somewhat legit. But bad bitcoin continued denying even after everything was getting pretty obvious. The problem is that this site made authority and despite its drifts to some shady cloud mining services, it's a useful site to get a glance on what are the scams going on in the crypto space. I don't know why he thought clam or khashier was a scam though. Anybody digging clams MUST transfer his btc to another wallet before giving away the private key to dig.

[dooglus]

I don't know why he thought clam or khashier was a scam though.

If you read the first few pages of this thread it was a pretty common idea at the start. It does look scammy on the surface having to give up your BTC private keys to claim free CLAMs so the confusion is understandable.

I would contact the guy and ask him to remove his accusation but from what I've seen of previous interactions with him he isn't exactly rational.

[JoelKatz]

I don't know why he thought clam or khashier was a scam though.

If you read the first few pages of this thread it was a pretty common idea at the start. It does look scammy on the surface having to give up your BTC private keys to claim free CLAMs so the confusion is understandable.

Has anyone we have any reason to trust audited the CLAM client? Otherwise, I think it's a very good idea to steer people away from feeding the Bitcoin private keys into some software that talks to the Internet and that they have no reason to trust.

[BayAreaCoins]

I don't know why he thought clam or khashier was a scam though.

If you read the first few pages of this thread it was a pretty common idea at the start. It does look scammy on the surface having to give up your BTC private keys to claim free CLAMs so the confusion is understandable.

Has anyone we have any reason to trust audited the CLAM client? Otherwise, I think it's a very good idea to steer people away from feeding the Bitcoin private keys into some software that talks to the Internet and that they have no reason to trust.

https://github.com/nochowderforyou/clams

[SuperClam]

I don't know why he thought clam or khashier was a scam though.

If you read the first few pages of this thread it was a pretty common idea at the start. It does look scammy on the surface having to give up your BTC private keys to claim free CLAMs so the confusion is understandable.

Has anyone we have any reason to trust audited the CLAM client? Otherwise, I think it's a very good idea to steer people away from feeding the Bitcoin private keys into some software that talks to the Internet and that they have no reason to trust.

Given that many users use the pre-compiled client, it is a minor matter to alter the code at will and no one seems very interested in taking part in the provable build process, I don't believe an 'audit' would be all that useful. 
 
That said, we've been here for some time and I would expect a handful of 'old hats' have reviewed the code. 
Poloniex did a thorough review before adding CLAM.
dooglus has about as much experience with the CLAM codebase as anyone, if you consider him trustworthy (and has commit permissions).

Beyond that, as with most codebases, I would encourage you to review the code and report your findings. 
 
It is important to note that the claim process has always included the prior step of emptying any BTC/LTC/DOGE balance from the key before importing/claiming them inside the CLAM client. 
These keys should also be retired and not used in the future. 
 
The above steps aren't required to import/claim CLAM, but recommended to avoid the issue entirely.

The offer/promise to delete the announcement post, code repository and end the CLAM project given proof of a 'scam' still stands (and has since the beginning).