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

[dooglus]

Thanks doogplus. If I have 400 clams, how to obtain daily reward? Please answer only those who know for sure. Thank You.

All you need to do is leave your wallet online, and if it is password protected, make sure you have unlocked it for staking. If it isn't password protected, just leave it running.

Coins will only stake if they haven't been involved in a transaction in the last 4 hours, so don't move them around if you don't need to. And after staking, they can't stake again for 500 blocks (which takes about 8 hours).

I would recommend adding

splitsize=5

to your clam.conf file. It's in the same folder as your clam wallet.dat. If it doesn't exist, you can make it, add that line, and restart the client. It will arrange for your 400 CLAMs to be split into 80 separate outputs of size 5 when they first stake. That's good because otherwise you need to wait 8 hours every time you stake.

[eprocent]

Thanks doogplus. If I have 400 clams, how to obtain daily reward? Please answer only those who know for sure. Thank You.

All you need to do is leave your wallet online, and if it is password protected, make sure you have unlocked it for staking. If it isn't password protected, just leave it running.

Coins will only stake if they haven't been involved in a transaction in the last 4 hours, so don't move them around if you don't need to. And after staking, they can't stake again for 500 blocks (which takes about 8 hours).

I would recommend adding

splitsize=5

to your clam.conf file. It's in the same folder as your clam wallet.dat. If it doesn't exist, you can make it, add that line, and restart the client. It will arrange for your 400 CLAMs to be split into 80 separate outputs of size 5 when they first stake. That's good because otherwise you need to wait 8 hours every time you stake.

I want to know a certain number of clams reward per 400 clams deposit or a daily rate.

[dooglus]

I want to know a certain number of clams reward per 400 clams deposit or a daily rate.

Staking has a large element of luck to it.

If you're asking "exactly how many CLAM will I stake per day if I have 400 CLAM?" then I can't tell you, other than "it depends how lucky you are; you'll average a little over 1 CLAM per day, but it could take a week for your first stake if you're unlucky".

Every 16 seconds all the outputs in your wallet get a chance of staking. An sha256 hash is done of a bunch of things, including the time (rounded down to a multiple of 16 seconds since the epoch), and some unique properties of each output. If the hash is lower than the current target times the value of the output, you get to stake the next block. In that respect it's like Bitcoin mining - you can buy the fastest ASIC there is and still not mine any blocks if you're unlucky. Or you can mine on your CPU and find a block very quickly if you have amazing luck.

Or did I misunderstand your question?

The reward is "1 CLAM plus transaction fees" each time you stake a block.

[eprocent]

I want to know a certain number of clams reward per 400 clams deposit or a daily rate.

Staking has a large element of luck to it.

If you're asking "exactly how many CLAM will I stake per day if I have 400 CLAM?" then I can't tell you, other than "it depends how lucky you are; you'll average a little over 1 CLAM per day (1 for 400 CLAMs per day), but it could take a week for your first stake if you're unlucky".

Every 16 seconds all the outputs in your wallet get a chance of staking. An sha256 hash is done of a bunch of things, including the time (rounded down to a multiple of 16 seconds since the epoch), and some unique properties of each output. If the hash is lower than the current target times the value of the output, you get to stake the next block. In that respect it's like Bitcoin mining - you can buy the fastest ASIC there is and still not mine any blocks if you're unlucky. Or you can mine on your CPU and find a block very quickly if you have amazing luck.

Or did I misunderstand your question?

The reward is "1 CLAM plus transaction fees" each time you stake a block.

From what I understand from you, is that the reward is about 0.25 percent per day but as an average of 1 clam is calculated at a higher number of days. I mean ... I'll get CLAM Average 1 per day, but by calculating the average over several days not just one day. So you wanted to tell me through the above?

[freedomno1]

Coins will only stake if they haven't been involved in a transaction in the last 4 hours, so don't move them around if you don't need to. And after staking, they can't stake again for 500 blocks (which takes about 8 hours).

I would recommend adding

splitsize=5

to your clam.conf file. It's in the same folder as your clam wallet.dat. If it doesn't exist, you can make it, add that line, and restart the client. It will arrange for your 400 CLAMs to be split into 80 separate outputs of size 5 when they first stake. That's good because otherwise you need to wait 8 hours every time you stake.

A bit interested in this so the Clam wallet will stop staking once it finds a result, for eight hours (500 Blocks) but if you break the same 400 coins into 5 clam units it will continue staking through the period with the other 395 while the 5 clams that staked are processing the transaction.

Kind of wondering what the advantage is to having them all in one large lump sum instead of say split size 1 instead unless it makes it faster to find blocks with the 400 in a group staking versus separately.
(JD finds them often assume their is a split size there or it would only find one every 8 hours ^^)

[Nthused]

Just Dice is fun as although I lost everything after getting too greedy I'm going to be coming back to try to win it all back plus some

[Gibbs187x]

Just Dice is fun as although I lost everything after getting too greedy I'm going to be coming back to try to win it all back plus some

yea same here got greedy lol

[eprocent]

I want to know a certain number of clams reward per 400 clams deposit or a daily rate.

Staking has a large element of luck to it.

If you're asking "exactly how many CLAM will I stake per day if I have 400 CLAM?" then I can't tell you, other than "it depends how lucky you are; you'll average a little over 1 CLAM per day (1 for 400 CLAMs per day), but it could take a week for your first stake if you're unlucky".

Every 16 seconds all the outputs in your wallet get a chance of staking. An sha256 hash is done of a bunch of things, including the time (rounded down to a multiple of 16 seconds since the epoch), and some unique properties of each output. If the hash is lower than the current target times the value of the output, you get to stake the next block. In that respect it's like Bitcoin mining - you can buy the fastest ASIC there is and still not mine any blocks if you're unlucky. Or you can mine on your CPU and find a block very quickly if you have amazing luck.

Or did I misunderstand your question?

The reward is "1 CLAM plus transaction fees" each time you stake a block.

From what I understand from you, is that the reward is about 0.25 percent per day but as an average of 1 clam is calculated at a higher number of days. I mean ... I'll get CLAM Average 1 per day, but by calculating the average over several days not just one day. So you wanted to tell me through the above?

What is the min stake age?

[dooglus]

From what I understand from you, is that the reward is about 0.25 percent per day but as an average of 1 clam is calculated at a higher number of days. I mean ... I'll get CLAM Average 1 per day, but by calculating the average over several days not just one day. So you wanted to tell me through the above?

It's hard to give you precise answers when you take my words and paraphrase them badly. But I think you have mostly understood what I was trying to tell you.

The minimum block reward is 1 CLAM, and the process is effectively random. So I'm not saying you'll earn 1 CLAM per day, but your expectation is in that ballpark.

A bit interested in this so the Clam wallet will stop staking once it finds a result, for eight hours (500 Blocks) but if you break the same 400 coins into 5 clam units it will continue staking through the period with the other 395 while the 5 clams that staked are processing the transaction.

Kind of wondering what the advantage is to having them all in one large lump sum instead of say split size 1 instead unless it makes it faster to find blocks with the 400 in a group staking versus separately.
(JD finds them often assume their is a split size there or it would only find one every 8 hours ^^)

Your balance is always made up of some finite number of unspent transaction outputs. Those outputs stake independently. When an output stakes, its value increases by 1 CLAM (plus any tx fees) and then can't stake again for 8 hours (500 blocks). So if all your balance is in a single output, your whole balance is tied up for 8 hours each time it stakes. If you have the client set to split your outputs when they stake, then your whole balance will still be tied up for 8 hours after it stakes the first time, but after that you'll have lots of separate small outputs staking independently. When any one of those outputs stakes, only that output will be tied up for 8 hours. The rest will continue trying to stake.

The advantage to keeping your coins in relatively few large outputs:

* you can spend large (in CLAMs) amounts without creating large (in bytes) transactions; if you have a thousand 0.001 CLAM outputs and try to spend them all at once, the transaction size will probably exceed the network limit
* you can check your outputs for staking opportunities relatively quickly; JD used to have close to 100,000 separate outputs in its wallet; it takes quite a while to check them all every 16 seconds to see if they can stake or not; I have since recombined the smallest outputs so now most outputs are in the 10 to 20 CLAM range instead of all being 4 CLAMs.

What is the min stake age?

4 hours since last transaction; 500 blocks since last stake

[eprocent]

From what I understand from you, is that the reward is about 0.25 percent per day but as an average of 1 clam is calculated at a higher number of days. I mean ... I'll get CLAM Average 1 per day, but by calculating the average over several days not just one day. So you wanted to tell me through the above?

It's hard to give you precise answers when you take my words and paraphrase them badly. But I think you have mostly understood what I was trying to tell you.

The minimum block reward is 1 CLAM, and the process is effectively random. So I'm not saying you'll earn 1 CLAM per day, but your expectation is in that ballpark.

A bit interested in this so the Clam wallet will stop staking once it finds a result, for eight hours (500 Blocks) but if you break the same 400 coins into 5 clam units it will continue staking through the period with the other 395 while the 5 clams that staked are processing the transaction.

Kind of wondering what the advantage is to having them all in one large lump sum instead of say split size 1 instead unless it makes it faster to find blocks with the 400 in a group staking versus separately.
(JD finds them often assume their is a split size there or it would only find one every 8 hours ^^)

Your balance is always made up of some finite number of unspent transaction outputs. Those outputs stake independently. When an output stakes, its value increases by 1 CLAM (plus any tx fees) and then can't stake again for 8 hours (500 blocks). So if all your balance is in a single output, your whole balance is tied up for 8 hours each time it stakes. If you have the client set to split your outputs when they stake, then your whole balance will still be tied up for 8 hours after it stakes the first time, but after that you'll have lots of separate small outputs staking independently. When any one of those outputs stakes, only that output will be tied up for 8 hours. The rest will continue trying to stake.

The advantage to keeping your coins in relatively few large outputs:

* you can spend large (in CLAMs) amounts without creating large (in bytes) transactions; if you have a thousand 0.001 CLAM outputs and try to spend them all at once, the transaction size will probably exceed the network limit
* you can check your outputs for staking opportunities relatively quickly; JD used to have close to 100,000 separate outputs in its wallet; it takes quite a while to check them all every 16 seconds to see if they can stake or not; I have since recombined the smallest outputs so now most outputs are in the 10 to 20 CLAM range instead of all being 4 CLAMs.

What is the min stake age?

4 hours since last transaction; 500 blocks since last stake

Thank you very much!

[picolo]

Just Dice is fun as although I lost everything after getting too greedy I'm going to be coming back to try to win it all back plus some

yea same here got greedy lol

Gamblers are going to go play, invest sometimes, divest, play then eventually most of them will lose and buy more clam that will end up in the bankroll.
Investors will tend to keep adding to their holdings by buying more clams rather than divest their clam even as the price goes up. More people will want to invest. They will need to buy clam to invest.
Some investors will divest and get some btc to save in btc or change it for fiat but most of the clam that are lost should stay in the bankroll in the current way things are.
As just-dice will naturally grow, as more people will use internet, as more people will know and use crypto, as more people will know and use clam; more people will play and invest in clam which means the price of clam should increase.

Prediction : we will pass 0.01 again by June 1st; 0.03 by September 1st and 0.05 by December 31th of this year.

[organofcorti]

I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.

I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?


Edit: It finally went through about 10 minutes after the rescan completed.

[SuperClam]

I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.

Welcome to CLAMs organofcorti  

Obviously, under normal circumstances, they shouldn't get stuck at all.
Would love some details either via thread, PM, git, or #clams IRC @ freenode.


For posterity:

If you were running two instances of the client/daemon, shutting one down and running a -rescan(or worse case a -salvagewallet) should solve the problem.

If for some reason your chain itself is stuck (not progressing, doesn't match block explorer), report the issue, update the client/daemon, -reindex should fix the problem.

If you sent a zero fee transaction and no one is willing to include it in a block, you can stake/mine the transaction into a block yourself, or have someone else do so for you.

If the transaction is actually a broadcast block/features the newer split features or CLAM specific features such a checklocktimeverify, or doesn't fit any of the above cases, please report the problem immediately so it can be looked into.

Cheers!

[organofcorti]

I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.

Welcome to CLAMs organofcorti 

Obviously, under normal circumstances, they shouldn't get stuck at all.
Would love some details either via thread, PM, git, or #clams IRC @ freenode.

What details do you need?

[SuperClam]

I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.

Welcome to CLAMs organofcorti 
Obviously, under normal circumstances, they shouldn't get stuck at all.
Would love some details either via thread, PM, git, or #clams IRC @ freenode.

What details do you need?

Anything unusual or non-standard about the transaction itself?
Were more than one client/daemon running at the same time with the same wallet/keys?
Was the client properly sync'd to the chain during the time in which the transaction was not confirming?
Anything anomalous in the debug logs file?

[BayAreaCoins]

Looks like possible CLAM roulette.

https://bitcointalk.org/index.php?topic=990126.msg10773184#msg10773184

Having investigated very much yet.

[dooglus]

I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.

I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?


Edit: It finally went through about 10 minutes after the rescan completed.

There's code that automatically resends our transactions in the event that they need resending:

Code:

void CWallet::ResendWalletTransactions(bool fForce)
{
    if (!fForce)
    {
        // Do this infrequently and randomly to avoid giving away
        // that these are our transactions.
        static int64_t nNextTime;
        if (GetTime() < nNextTime)
            return;
        bool fFirst = (nNextTime == 0);
        nNextTime = GetTime() + GetRand(30 * 60);
        if (fFirst)
            return;

        // Only do it if there's been a new block since last time
        static int64_t nLastTime;
        if (nTimeBestReceived < nLastTime)
            return;
        nLastTime = GetTime();
    }

There's a random delay there of up to 30 minutes. I expect that's what you saw.

I'm unclear on what can cause a transaction to fail to be sent initially. Obviously if you aren't connected to any peers then it won't be sent. I'm not sure what happens if your blockchain is out of sync when you make a transaction - perhaps it delays sending until the sync has finished.

[organofcorti]

I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.

I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?


Edit: It finally went through about 10 minutes after the rescan completed.

There's code that automatically resends our transactions in the event that they need resending:

Code:

void CWallet::ResendWalletTransactions(bool fForce)
{
    if (!fForce)
    {
        // Do this infrequently and randomly to avoid giving away
        // that these are our transactions.
        static int64_t nNextTime;
        if (GetTime() < nNextTime)
            return;
        bool fFirst = (nNextTime == 0);
        nNextTime = GetTime() + GetRand(30 * 60);
        if (fFirst)
            return;

        // Only do it if there's been a new block since last time
        static int64_t nLastTime;
        if (nTimeBestReceived < nLastTime)
            return;
        nLastTime = GetTime();
    }

There's a random delay there of up to 30 minutes. I expect that's what you saw.

Is that in the standard clam-qt? This tx was *from* me rather than *to* me. Still, what you describe does sound about right.

I'm unclear on what can cause a transaction to fail to be sent initially. Obviously if you aren't connected to any peers then it won't be sent. I'm not sure what happens if your blockchain is out of sync when you make a transaction - perhaps it delays sending until the sync has finished.

I was connected to peers and the height that the client reported was the correct height, but the 'confirmations' box in the gui was reporting 'unconnected'. Not sure what to make of that.

[dooglus]

Is that in the standard clam-qt? This tx was *from* me rather than *to* me. Still, what you describe does sound about right.

Yes it is. And this code is for rebroadcasting transactions you made.

I was connected to peers and the height that the client reported was the correct height, but the 'confirmations' box in the gui was reporting 'unconnected'. Not sure what to make of that.

Me neither. I only use the clamd command line version of the client.

Are you sure it said 'unconnected'? I don't see that word anywhere in the sources. Do you mean 'unconfirmed'?

Code:

./qt/transactiontablemodel.cpp:        status = tr("Unconfirmed");

That just means "not in a block yet".

[organofcorti]

Is that in the standard clam-qt? This tx was *from* me rather than *to* me. Still, what you describe does sound about right.

Yes it is. And this code is for rebroadcasting transactions you made.

I was connected to peers and the height that the client reported was the correct height, but the 'confirmations' box in the gui was reporting 'unconnected'. Not sure what to make of that.

Me neither. I only use the clamd command line version of the client.

Are you sure it said 'unconnected'? I don't see that word anywhere in the sources. Do you mean 'unconfirmed'?

Code:

./qt/transactiontablemodel.cpp:        status = tr("Unconfirmed");

That just means "not in a block yet".

Not 'unconfirmed'. I might have 'unconnected' wrong though. Maybe 'not connected' or something similar? It only appeared in the tool tip when hovering over the box, the box itself was empty (no graphical '?' symbol).