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

[tirthraj]

whats the staking rate of this coin .
let stake example if I have deposited 100 CLAMS then how much i will get per day or week as per staking procedure..?

[FlungSpun]

whats the staking rate of this coin .
let stake example if I have deposited 100 CLAMS then how much i will get per day or week as per staking procedure..?

Real world on Just-Dice
An invested deposit from Jan 2018 yields ~30% (29.4)

This is the 2018 bear so .... currently a whopping USD loss and a modest BTC gain.

Can't confirm the CLAM client results at this time.
Should be slightly better if you consider site commission but JD performance will also vary on the profits from house edge.

Running your own client is definitely more erratic in rewards as you might expect. Your Keys, Your Coins.


Rule of thumb used to be (a year or so  ago) 1k Clams gets you a clam a day. Likely need a few more for that same return now.

[criptocambio]

whats the staking rate of this coin .
let stake example if I have deposited 100 CLAMS then how much i will get per day or week as per staking procedure..?

The difficulty now is 228801, so you need aprox. 2000 clams to stake once a day. 100 clams will get you a coin each 20 days, give or take. But the difficulty is varying wildly in the last months, ranging from 100000 to 250000

[Bit-Exo.com]

Invest and stake CLAM at Bit-Exo.com


We do not charge any fee on stakes! You can even only stake by setting your kelly to 0.

[dooglus]

The attacker (see here) is back:

    link to example spammy block

He's spamming Just-Dice with tens of thousands of tiny outputs presumably in an attempt to disrupt staking.

If you're staking CLAMs please check whether he's attacking your wallets too. You can set "mininput=0.01" in your clam.conf to tell it to ignore UTXOs worth less than 0.01 CLAMs and that pretty much defeats the attack.

[criptocambio]

The attacker (see here) is back:

    link to example spammy block

He's spamming Just-Dice with tens of thousands of tiny outputs presumably in an attempt to disrupt staking.

If you're staking CLAMs please check whether he's attacking your wallets too. You can set "mininput=0.01" in your clam.conf to tell it to ignore UTXOs worth less than 0.01 CLAMs and that pretty much defeats the attack.

Im not sure, but i think it's affecting everyone. Here is my debug.log:

SetBestChain: new best=6bb9fa2bb3c51f7526d153307d68e9acce3e00e1033e53e73f707310$
ProcessBlock: ACCEPTED
receive version message: version 60014, blocks=931607, us=51.158.75.80:31174, t$
stake took 10s


10 seconds to validate a block, as there is a lot of blocks that take only 1 second or less.

Looks like every block minted by just-dice is affected, as every time i receive them, they take more than 10 seconds to validate even in the ones that do not have dust output. Blocks that dont have your addresses, stake as quick as one second or less. Right now, i had put mininput=0.001 in the config file to see if this attack ceases, and hope this does not fork the network as someone can mint a block with outputs smaller than this and my node will reject it.

I saw blocks taking several seconds to validate months before and thought this was because some other software taking resources in my machine other than clam client. Also, the elevation in the difficulty from 90000-100000 to almost 200000 at some times started at the same time i saw these blocks that take a lot of time to validate. Maybe this attack is much more older than we think

[dooglus]

Im not sure, but i think it's affecting everyone. Here is my debug.log:

SetBestChain: new best=6bb9fa2bb3c51f7526d153307d68e9acce3e00e1033e53e73f707310$
ProcessBlock: ACCEPTED
receive version message: version 60014, blocks=931607, us=51.158.75.80:31174, t$
stake took 10s


10 seconds to validate a block, as there is a lot of blocks that take only 1 second or less.

Looks like every block minted by just-dice is affected, as every time i receive them, they take more than 10 seconds to validate even in the ones that do not have dust output. Blocks that dont have your addresses, stake as quick as one second or less. Right now, i had put mininput=0.001 in the config file to see if this attack ceases, and hope this does not fork the network as someone can mint a block with outputs smaller than this and my node will reject it.

I saw blocks taking several seconds to validate months before and thought this was because some other software taking resources in my machine other than clam client. Also, the elevation in the difficulty from 90000-100000 to almost 200000 at some times started at the same time i saw these blocks that take a lot of time to validate. Maybe this attack is much more older than we think

Note that the "stake took 10s" is telling you how long your client took to check through your unspent outputs to see whether you had any which were ready to stake. You should be seeing those "stake took Xs" about every 16 seconds, not once per block.

Note also that you should put "logtimestamps=1" in your clam.conf so that every line of your debug,log gets timestamped.

The "mininput" thing won't fork the network. You're not rejecting any transactions, you're just ignoring some of them. They still go into your UTXO database but your wallet doesn't recognize them as belonging to you and so it won't waste time trying to stake them.

The difficulty goes up and down wildly every day due to how it is calculated. I don't think that's anything to worry too much about. How are your "stake took ..." times looking now? Are they back to where they used to be again?

[tirthraj]

whats the staking rate of this coin .
let stake example if I have deposited 100 CLAMS then how much i will get per day or week as per staking procedure..?

The difficulty now is 228801, so you need aprox. 2000 clams to stake once a day. 100 clams will get you a coin each 20 days, give or take. But the difficulty is varying wildly in the last months, ranging from 100000 to 250000

thnx for response.  any online pool or staking because  i can't do staking from my own system as compatibility issue.

[yayat]

When I saw this Announcement there was a lot of jam commenting and this made me look for CLAMS coins at Coinmarketcap.
Then I saw it at POLONIEX and it only took 1 month CLAMS raised its price more than 1005. LOL

http://prntscr.com/m0j47k

[slasi1974]

quit interesting idea is it still active or not?

[BayAreaCoins]

FreeBitcoins.com CLAM faucet is back online.

We are strictly doing offchain transactions for our faucet in order not to shit up the CLAM blockchain any more than necessary.

Our CLAM faucet currently connects to Freebitcoins.com and Just-dice.com... we will be adding more site though!

[jpcfan]

when will new clam wallet come out?


over/under is 36 months


place your wagers now

[tbct_mt2]

Today, Bitcoin has passed exactly 10 years since its born day.

For CLAM, the project started in May of 2014.

Code:

May 24, 2014, 04:33:19 AM

It means the project has nearly four-year history, long enough to be recogised by crypto enthusiasts globally.
Fortunately, CLAM has actually had very solid community around the globe.

[Dimon777]

I downloaded the file to better synchronize the wallet but the problem remained
it does not load what is the reason?

[BayAreaCoins]

Deb from Just-Dice.com made a commit today!  (Her first one ever I believe)

https://github.com/nochowderforyou/clams/commit/d59fba3c5b0bdcdfceb091e08ea430579b1e12a5

We need more people helping get this new client release... Please message dooglus or myself for a link to the Discord if you think you can help.

Thanks!

[vashshawn]

having trouble syncing the current client, even with the current bootstrap..

[BayAreaCoins]

having trouble syncing the current client, even with the current bootstrap..

You need to be a fairly experienced user atm to run a CLAM wallet it seems.

It may be best to just wait for the new wallet to be released.... it's being worked on.

[vashshawn]

I will just delete the blockchain and try loading the bootstrap again and see if it works. I tried the normal download and the torrent.

[Broko82]

having trouble syncing the current client, even with the current bootstrap..

You need to be a fairly experienced user atm to run a CLAM wallet it seems.

It may be best to just wait for the new wallet to be released.... it's being worked on.

I don't think so. I have been running the 1.4.17 client for several months without any issues. I also downloaded the bootstrap file via torrent.
Syncing just needs time. Let it work and the client will download all the necessary data, although it may seem unresponsive for quite some time.

[criptocambio]

Im not sure, but i think it's affecting everyone. Here is my debug.log:

SetBestChain: new best=6bb9fa2bb3c51f7526d153307d68e9acce3e00e1033e53e73f707310$
ProcessBlock: ACCEPTED
receive version message: version 60014, blocks=931607, us=51.158.75.80:31174, t$
stake took 10s


10 seconds to validate a block, as there is a lot of blocks that take only 1 second or less.

Looks like every block minted by just-dice is affected, as every time i receive them, they take more than 10 seconds to validate even in the ones that do not have dust output. Blocks that dont have your addresses, stake as quick as one second or less. Right now, i had put mininput=0.001 in the config file to see if this attack ceases, and hope this does not fork the network as someone can mint a block with outputs smaller than this and my node will reject it.

I saw blocks taking several seconds to validate months before and thought this was because some other software taking resources in my machine other than clam client. Also, the elevation in the difficulty from 90000-100000 to almost 200000 at some times started at the same time i saw these blocks that take a lot of time to validate. Maybe this attack is much more older than we think

Note that the "stake took 10s" is telling you how long your client took to check through your unspent outputs to see whether you had any which were ready to stake. You should be seeing those "stake took Xs" about every 16 seconds, not once per block.

Note also that you should put "logtimestamps=1" in your clam.conf so that every line of your debug,log gets timestamped.

The "mininput" thing won't fork the network. You're not rejecting any transactions, you're just ignoring some of them. They still go into your UTXO database but your wallet doesn't recognize them as belonging to you and so it won't waste time trying to stake them.

The difficulty goes up and down wildly every day due to how it is calculated. I don't think that's anything to worry too much about. How are your "stake took ..." times looking now? Are they back to where they used to be again?

How are your "stake took ..." times looking now? Are they back to where they used to be again?

I still get 5-10 seconds to validate after a block arrives, but then it gets to 0 again. Probably not related to the dust outputs tough, as i already got mininput in the clam.conf