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

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: foodstamps on July 19, 2015, 09:29:27 AM

Quote from: dooglus on July 19, 2015, 01:10:55 AM

So thanks for playing, but we're done here.

Thanks for the game. No luck finding an addy, but I learned how to use vanitygen well if another contest like this arises.

Me too...

So the new addresses I have use 'compressed' public keys and so use less space on the blockchain each time they stake. But I was left with the question of how to migrate from the old addresses to the new ones.

I ended up adding a new flag to the CLAM client: -staketo=ADDR which you can use to tell it to move coins to the new address as they stake.

It results in a nice smooth transition:

but somewhat ugly transactions:

because the CLAM protocol says that input 0 and output 1 have to have the same address, so I make an empty output 1 and a new non-empty output 2 to follow the protocol. All the 0-value outputs should be 'spent' automatically when they mature thanks to my "combineany=1" setting.

Edit: here's evidence that it is indeed cleaning up the zero-valued outputs it creates:

Quote

$ clamd listunspent 0 99999999 '[]' 0 | grep -A1 -F 'amount" : 0.00000000' | grep conf | sort -k3n
   "confirmations" : 1
   "confirmations" : 2
   "confirmations" : 3
   "confirmations" : 4
   "confirmations" : 5
[...]
   "confirmations" : 497
   "confirmations" : 498
   "confirmations" : 499
   "confirmations" : 500
   "confirmations" : 503
   "confirmations" : 504
   "confirmations" : 505
   "confirmations" : 506
   "confirmations" : 508
   "confirmations" : 510
   "confirmations" : 511

ie. only one mature unspent 0 output, waiting for the next time we stake to get spent in the staking transaction.

Here's an example of it spending a zero-valued output as it creates a new one:

The creation of new zero-valued outputs only happens when moving coins from one address to another while staking - so only once per output.

foodstamps

hero member

Activity: 938

Merit: 502

Quote from: dooglus on July 19, 2015, 01:10:55 AM

So thanks for playing, but we're done here.

Thanks for the game. No luck finding an addy, but I learned how to use vanitygen well if another contest like this arises.

dooglus

legendary

Activity: 2940

Merit: 1333

I found one:

Pattern: xJDCLAMZ
Address: xJDCLAMZkcp7fQ3ieHfZA4SLu3aTy2Y1mr
PrivkeyPart: LiqWRFz5L1CM6vYma7TyZDtdZaJ3NULaJZXtnp45UXix5epTVPkR

One bounty of 50 CLAMs remaining...

Edit: but it turns out I no longer have the private key for the public key I posted!

So we're going to have to start over.

Edit2: oh, I found it again. Phew.

And I found a 2nd vanity too:

Pattern: xJDCLAMZ
Address: xJDCLAMZSGaTadAzcS7tcVNTa46qCr6j2s
PrivkeyPart: Lnxm6XTD45N6eEnmow9eKDmotchWUBtQsrWPFeg8DwAA5SXEPj4L

So thanks for playing, but we're done here.

Quote

> validateaddress xJDCLAMZkcp7fQ3ieHfZA4SLu3aTy2Y1mr
{
   "isvalid" : true,
   "address" : "xJDCLAMZkcp7fQ3ieHfZA4SLu3aTy2Y1mr",
   "ismine" : true,
   "isscript" : false,
   "pubkey" : "037bedfabb451755cf6061636c8004dba32cb95095ba8cba61de236a70f95e3d2a",
   "iscompressed" : true,
   "account" : ""
}

> validateaddress xJDCLAMZSGaTadAzcS7tcVNTa46qCr6j2s
{
   "isvalid" : true,
   "address" : "xJDCLAMZSGaTadAzcS7tcVNTa46qCr6j2s",
   "ismine" : true,
   "isscript" : false,
   "pubkey" : "02c8c838d0fbd7167a8fc2e153eb6717c6f7a9886d38415aa6e8dd805087fbd7e9",
   "iscompressed" : true,
   "account" : ""
}

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: dooglus on July 18, 2015, 08:27:16 PM

Quote from: K1773R on July 18, 2015, 07:37:13 PM

oclvanitygen has no working -P switch...

What makes you say that?

Are you using the vanitygen repo I linked to? I just tried it and it works for me.

Quote from: K1773R on July 18, 2015, 07:37:13 PM

also check --help

Thanks. I just added documentation for the -P flag to the --help text.

Quote from: K1773R on July 18, 2015, 07:37:13 PM

Code:

./oclvanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Invalid character '0' in prefix '048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB'
Difficulty: 888446610538
[32.19 Mkey/s][total 209715200][Prob 0.0%][50% in 5.3h]

Yeah, that looks like you're running the wrong version.

Quote from: dooglus on July 18, 2015, 03:34:55 PM

The standard vanitygen program isn't able to make CLAM addresses. I made a fork here:
https://github.com/dooglus/vanitygen
which does.

[...]

Once you've built my fork of vanitygen, run it like this:

Code:

./vanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ

I decided to check whether oclvanitygen really works with the -P flag, because nobody has yet posted a private key that works for me, so I rented a machine with a video card:

Code:

$ ./oclvanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLA
Difficulty: 264104224
Pattern: xJDCLA
Address: xJDCLAE7QkEFsQe9jENL8KgNL8txiLRAdN
PrivkeyPart: LgeVmeaXv5gMETfs6q8CYJEB9W6UhooAnwXUb9c3nf5uor5u6QpX
[25.14 Mkey/s][total 260046848][Prob 22.4%][50% in 4.6s][Found 1]

When I combine LgeVmeaXv5gMETfs6q8CYJEB9W6UhooAnwXUb9c3nf5uor5u6QpX with my private key, I get a private key which gives me an XJDCLA address. So it is working.

I'm searching keys at 26 Mkey/s, 50% in 6 hours. So you guys have some competition.

after a make clean && make, it works. tough i probably cant respond in time with the keys it finds...

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: K1773R on July 18, 2015, 07:37:13 PM

oclvanitygen has no working -P switch...

What makes you say that?

Are you using the vanitygen repo I linked to? I just tried it and it works for me.

Quote from: K1773R on July 18, 2015, 07:37:13 PM

also check --help

Thanks. I just added documentation for the -P flag to the --help text.

Quote from: K1773R on July 18, 2015, 07:37:13 PM

Code:

./oclvanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Invalid character '0' in prefix '048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB'
Difficulty: 888446610538
[32.19 Mkey/s][total 209715200][Prob 0.0%][50% in 5.3h]

Yeah, that looks like you're running the wrong version.

Quote from: dooglus on July 18, 2015, 03:34:55 PM

The standard vanitygen program isn't able to make CLAM addresses. I made a fork here:
https://github.com/dooglus/vanitygen
which does.

[...]

Once you've built my fork of vanitygen, run it like this:

Code:

./vanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ

I decided to check whether oclvanitygen really works with the -P flag, because nobody has yet posted a private key that works for me, so I rented a machine with a video card:

Code:

$ ./oclvanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLA
Difficulty: 264104224
Pattern: xJDCLA
Address: xJDCLAE7QkEFsQe9jENL8KgNL8txiLRAdN
PrivkeyPart: LgeVmeaXv5gMETfs6q8CYJEB9W6UhooAnwXUb9c3nf5uor5u6QpX
[25.14 Mkey/s][total 260046848][Prob 22.4%][50% in 4.6s][Found 1]

When I combine LgeVmeaXv5gMETfs6q8CYJEB9W6UhooAnwXUb9c3nf5uor5u6QpX with my private key, I get a private key which gives me an XJDCLA address. So it is working.

I'm searching keys at 26 Mkey/s, 50% in 6 hours. So you guys have some competition.

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: dooglus on July 18, 2015, 07:05:20 PM

Quote from: K1773R on July 18, 2015, 04:19:42 PM

Quote from: dooglus on July 18, 2015, 04:16:46 PM

Ah - that Privkey you gave me is the actual privkey for an xJDC address. Did you specify the -P flag and the pubkey? It looks like either you didn't, or oclvanitygen is ignoring it.

yes, -P dosnt work for OCL Sad

it was ignored.

It isn't ignored for me. If I copy it wrong it complains, and if I get it right it accepts it and goes on to find that I don't have a suitable video card:

Code:

$ ./oclvanitygen -CkP xx8F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Invalid base pubkey

$ ./oclvanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Difficulty: 888446610538
clGetPlatformIDs(0): Unknown code -1001
clGetPlatformIDs(0): Unknown code -1001
Available OpenCL platforms:

$

oclvanitygen has no working -P switch... also check --help

Code:

./oclvanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Invalid character '0' in prefix '048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB'
Difficulty: 888446610538
[32.19 Mkey/s][total 209715200][Prob 0.0%][50% in 5.3h]

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: K1773R on July 18, 2015, 04:19:42 PM

Quote from: dooglus on July 18, 2015, 04:16:46 PM

Ah - that Privkey you gave me is the actual privkey for an xJDC address. Did you specify the -P flag and the pubkey? It looks like either you didn't, or oclvanitygen is ignoring it.

yes, -P dosnt work for OCL Sad

it was ignored.

It isn't ignored for me. If I copy it wrong it complains, and if I get it right it accepts it and goes on to find that I don't have a suitable video card:

Code:

$ ./oclvanitygen -CkP xx8F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Invalid base pubkey

$ ./oclvanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Difficulty: 888446610538
clGetPlatformIDs(0): Unknown code -1001
clGetPlatformIDs(0): Unknown code -1001
Available OpenCL platforms:

$

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

built your client and copied in your command, but it doesn't like the invocation:

Code:

tsp@citrus:~/src/vanitygen-dooglus$ ./vanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD18 97F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ
Invalid base pubkey

Edit: now I got it running, I copied the pubkey from the code element rather than the main text and it's working now

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: dooglus on July 18, 2015, 04:16:46 PM

Quote from: dooglus on July 18, 2015, 04:14:16 PM

Quote from: K1773R on July 18, 2015, 04:03:33 PM

using OCL, is this correct?

Code:

Pattern: xJDC
Address: xJDCQtZP9MTyDVhUwHeNX7HYhXqhDuZMN1
Privkey: LmGxCNahLoFuYHsFXoYbG8T3ggjK9dBud5V7JxW8fMs1WPYYMBPQ

No. That gives me these two CLAM addresses (one's compressed, one isn't):

xBhBpydGF9xduGRSBt3uSWENqaeKiZRzvX
xMiZ42BzUjeRgpa45Q4tWkzdeMsHhyP2U5

Neither starts xJDC.

Maybe my patch to oclvanitygen.c was bad.

Ah - that Privkey you gave me is the actual privkey for an xJDC address. Did you specify the -P flag and the pubkey? It looks like either you didn't, or oclvanitygen is ignoring it.

yes, -P dosnt work for OCL Sad

it was ignored.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: dooglus on July 18, 2015, 04:14:16 PM

Quote from: K1773R on July 18, 2015, 04:03:33 PM

using OCL, is this correct?

Code:

Pattern: xJDC
Address: xJDCQtZP9MTyDVhUwHeNX7HYhXqhDuZMN1
Privkey: LmGxCNahLoFuYHsFXoYbG8T3ggjK9dBud5V7JxW8fMs1WPYYMBPQ

No. That gives me these two CLAM addresses (one's compressed, one isn't):

xBhBpydGF9xduGRSBt3uSWENqaeKiZRzvX
xMiZ42BzUjeRgpa45Q4tWkzdeMsHhyP2U5

Neither starts xJDC.

Maybe my patch to oclvanitygen.c was bad.

Ah - that Privkey you gave me is the actual privkey for an xJDC address. Did you specify the -P flag and the pubkey? It looks like either you didn't, or oclvanitygen is ignoring it.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: RussianRaibow on July 18, 2015, 04:09:24 PM

Sorry, I do not understand exactly how CLAM works, but when someone is generating an address for you, wont he have access on the private key as well and thereby the ability to spend your fund on that address in future ?

It's more about how vanitygen works. If you give it a -P pubkey argument, the private key won't be useful for anyone who doesn't have the corresponding private key. And I only posted the pubkey.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: K1773R on July 18, 2015, 04:03:33 PM

using OCL, is this correct?

Code:

Pattern: xJDC
Address: xJDCQtZP9MTyDVhUwHeNX7HYhXqhDuZMN1
Privkey: LmGxCNahLoFuYHsFXoYbG8T3ggjK9dBud5V7JxW8fMs1WPYYMBPQ

No. That gives me these two CLAM addresses (one's compressed, one isn't):

xBhBpydGF9xduGRSBt3uSWENqaeKiZRzvX
xMiZ42BzUjeRgpa45Q4tWkzdeMsHhyP2U5

Neither starts xJDC.

Maybe my patch to oclvanitygen.c was bad.

RussianRaibow

hero member

Activity: 616

Merit: 500

I AM A SCAMMER

Quote from: dooglus on July 18, 2015, 03:34:55 PM

Bounty offer:

I need two new CLAM vanity addresses. One for the hot wallet, and one for the staking wallet.

I want them both to start with xJDCLAMZ, case sensitive.

I want them both to use *compressed* public keys.

The standard vanitygen program isn't able to make CLAM addresses. I made a fork here:
https://github.com/dooglus/vanitygen
which does.

My public key for vanitygen is 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD18 97F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB

Once you've built my fork of vanitygen, run it like this:

./vanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD18 97F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ

-C to generate CLAM addresses
-k to keep going after finding the first one
-P to specify my public key

I don't have a graphics card. You might find that oclvanitygen works better, but I've never even been able to check if it works at all. I made some changes to have it accept -C but don't know whether I did it right. If you want to check, generate an xJD address, post the privkey here and I'll tell you if it works for me.

I'll pay 50 CLAM to the finder(s) of each of the first two working private keys posted here. Only unedited posts will count, so I can check the post timestamps.

Sorry, I do not understand exactly how CLAM works, but when someone is generating an address for you, wont he have access on the private key as well and thereby the ability to spend your fund on that address in future ?

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: dooglus on July 18, 2015, 03:34:55 PM

Bounty offer:

I need two new CLAM vanity addresses. One for the hot wallet, and one for the staking wallet.

I want them both to start with xJDCLAMZ, case sensitive.

I want them both to use *compressed* public keys.

The standard vanitygen program isn't able to make CLAM addresses. I made a fork here:
https://github.com/dooglus/vanitygen
which does.

My public key for vanitygen is 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD18 97F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB

Once you've built my fork of vanitygen, run it like this:

./vanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD18 97F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ

-C to generate CLAM addresses
-k to keep going after finding the first one
-P to specify my public key

I don't have a graphics card. You might find that oclvanitygen works better, but I've never even been able to check if it works at all. I made some changes to have it accept -C but don't know whether I did it right. If you want to check, generate an xJD address, post the privkey here and I'll tell you if it works for me.

I'll pay 50 CLAM to the finder(s) of each of the first two working private keys posted here. Only unedited posts will count, so I can check the post timestamps.

using OCL, is this correct?

Code:

Pattern: xJDC
Address: xJDCQtZP9MTyDVhUwHeNX7HYhXqhDuZMN1
Privkey: LmGxCNahLoFuYHsFXoYbG8T3ggjK9dBud5V7JxW8fMs1WPYYMBPQ

dooglus

legendary

Activity: 2940

Merit: 1333

Bounty offer:

I need two new CLAM vanity addresses. One for the hot wallet, and one for the staking wallet.

I want them both to start with xJDCLAMZ, case sensitive.

I want them both to use *compressed* public keys.

The standard vanitygen program isn't able to make CLAM addresses. I made a fork here:
https://github.com/dooglus/vanitygen
which does.

My public key for vanitygen is:

Code:

048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB

Once you've built my fork of vanitygen, run it like this:

Code:

./vanitygen -CkP 048F08DCB868F3C22397BF5BAE1F19DE55F4D936AF66DC144E098F69A488FE3266A14FDCDAFBD1897F034AA54CAE13D2AB9A9D96B487A263594F408100D6DCC0FB xJDCLAMZ

-C to generate CLAM addresses
-k to keep going after finding the first one
-P to specify my public key

I don't have a graphics card. You might find that oclvanitygen works better, but I've never even been able to check if it works at all. I made some changes to have it accept -C but don't know whether I did it right. If you want to check, generate an xJD address, post the privkey here and I'll tell you if it works for me.

I'll pay 50 CLAM to the finder(s) of each of the first two working private keys posted here. Only unedited posts will count, so I can check the post timestamps.

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: dooglus on July 18, 2015, 03:16:06 PM

Quote from: tspacepilot on July 18, 2015, 02:45:25 PM

I guess that means that difficulty will get harder in the fuature as more clams are created. You said nowadays there are 600K trying to stake. With 1.4K created each day, then, unless many clams are lost, I guess staking will be twice as hard in approx 2 years when there are 1200K trying to stake.

Yes - you can see how the difficulty has gone up over time here:

http://www.presstab.pw/phpexplorer/CLAM/charts.php?type=posdifficulty

The drop just before block 400k was a JD user withdrawing 5 CLAMs over and over again into their local wallet as an easy way of splitting their coins up. The wallet spent all its time trying to decide which outputs to use so it was too busy to stake. After that I put a limit on the number of withdrawals you can make, and moved most of the coins to the staking wallet.

The drop just a few days ago was due to me typing "clamd stop" in the wrong window, thinking I was shutting down my local CLAM client, but actually shutting down the JD staking wallet.

Wow, so when is CLAM going to be officially rechristened as JDCOIN?

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: tspacepilot on July 18, 2015, 02:45:25 PM

I guess that means that difficulty will get harder in the fuature as more clams are created. You said nowadays there are 600K trying to stake. With 1.4K created each day, then, unless many clams are lost, I guess staking will be twice as hard in approx 2 years when there are 1200K trying to stake.

Yes - you can see how the difficulty has gone up over time here:

http://www.presstab.pw/phpexplorer/CLAM/charts.php?type=posdifficulty

The drop just before block 400k was a JD user withdrawing 5 CLAMs over and over again into their local wallet as an easy way of splitting their coins up. The wallet spent all its time trying to decide which outputs to use so it was too busy to stake. After that I put a limit on the number of withdrawals you can make, and moved most of the coins to the staking wallet.

The drop just a few days ago was due to me typing "clamd stop" in the wrong window, thinking I was shutting down my local CLAM client, but actually shutting down the JD staking wallet.

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: dooglus on July 17, 2015, 07:31:44 PM

Quote from: dalvi on July 17, 2015, 07:00:33 PM

And how can I know what is the probability of geting one clam based on how much CLAMs I have, by time period?
PS: sorry for the bad english

One CLAM is created every minute, so 1440 per day.

There are about 600k CLAMs trying to stake.

600k/1440 = 416.666

So each 416 CLAMs can expect to stake about once per day.

If you have 41 CLAMs, you can expect them to stake about every 10 days.

And so on.

I guess that means that difficulty will get harder in the fuature as more clams are created. You said nowadays there are 600K trying to stake. With 1.4K created each day, then, unless many clams are lost, I guess staking will be twice as hard in approx 2 years when there are 1200K trying to stake.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: dalvi on July 17, 2015, 07:00:33 PM

And how can I know what is the probability of geting one clam based on how much CLAMs I have, by time period?
PS: sorry for the bad english

One CLAM is created every minute, so 1440 per day.

There are about 600k CLAMs trying to stake.

600k/1440 = 416.666

So each 416 CLAMs can expect to stake about once per day.

If you have 41 CLAMs, you can expect them to stake about every 10 days.

And so on.

dalvi

newbie

Activity: 2

Merit: 0

OK, so I basically need to have some CLAMs on my qt wallet, and leave it open as much as possible? That's it? Much fairer than all those hardware-heavy minings of other coins Cheesy

And how can I know what is the probability of geting one clam based on how much CLAMs I have, by time period?
PS: sorry for the bad english

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