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

[RussianRaibow]

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 ?

[dooglus]

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.

[dooglus]

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]

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.

[K1773R]

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 it was ignored.

[tspacepilot]

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

[dooglus]

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 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:

$ 

[K1773R]

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 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]

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.

also check --help

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

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.

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]

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.

also check --help

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

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.

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]

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.

> 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" : ""
}

[foodstamps]

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]

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:

$ 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.

[cloverme]

Checking in to see if there's a testnet for clam yet. I think I remember someone saying in a future release, so just checking

[casinobitco]

Thanks Doog - We'll keep an eye out for a fix, then it should be pretty easy for us to integrate into PeerBet!

<snip>
I opened a github issue about this: https://github.com/nochowderforyou/clams/issues/202

[presstab]

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.

Wow. That is an awesome feature.

[statdude]

So, how do i go about claiming my clams with private keys? not clear from OP.

[dooglus]

So, how do i go about claiming my clams with private keys? not clear from OP.

The easiest way is to import your whole BTC/LTC/DOGE wallet.dat into the CLAM client. It will add all the private keys into its own wallet and scan the blockchain for distribution CLAMs.

Alternatively, if you have specific private keys in WIF format, you can "importpriv" in the CLAM client debug console.

As a third alternative, you can use the Just-Dice.com chat tab to check addresses for CLAM (/dig ADDRESS) and to claim any CLAMs it locates (/dig ADDRESS PRIVKEY). That involves sending your private key to a remote server, so make sure the address is empty and retired from use before doing that.

Oh, and finally, you can use an the CLAM client on an offline machine (without even a copy of the blockchain) to sign a transaction with your private key. Then you don't have to trust the CLAM client or Just-Dice.com. The Just-Dice chat tab can give you a command to run on the offline machine. For example, I type:

/dig 1CrPRwBkwZdEejXusCbh8o35YMN7g7ffKf offline

and it tells me:

02:14:34 INFO: run the following on an offline Linux machine, then broadcast the resulting hex value using https://just-dice.com/pushtx
02:14:34 INFO: the addr= part tells it where to send your CLAMs; the default is your Just-Dice deposit address
02:14:34 INFO: when prompted, type your private key:
02:14:34 INFO: echo -n "privkey: "; read privkey; addr=xMYvd61airRrnSUmV2oE1JhEqvzLdFWP7r; val=4.60535574; txid=b45c2a20731f8a88ba980f9cc9ce1d43cd7913d9c26ee3e8002ba1d08676b3de; vout=0; pubkey=76a91482007d41eec3a28b66b1ba726721d95577eb5a7688ac; output='"txid":"'$txid'","vout":'$vout; clamd signrawtransaction $(clamd createrawtransaction '[{'$output'}]' '{"'$addr'":'$val'}') '[{'$output',"scriptPubKey":"'$pubkey'"}]' '["'$privkey'"]'

[Crestington]

Dooglus, do you have some helpful links in how to create a CLAMS like distribution?

I want to create redeemable keys securely for 2 different Coins but I have having a hard time finding useful information that is easy to understand.

[dooglus]

Dooglus, do you have some helpful links in how to create a CLAMS like distribution?

I want to create redeemable keys securely for 2 different Coins but I have having a hard time finding useful information that is easy to understand.

I don't, sorry. I wasn't around for the initial distribution of CLAMs.

The big picture is pretty clear: You can convert BTC addresses to CLAM addresses simply by changing the 'version' byte in the base58check encoding. So I guess all you need to do is get a list of the BTC addresses you want to fund, convert them to your new coin's addresses, and fund those addresses.

But as for actual scripts to do the work for you, I don't have them. Maybe SuperClam or xploited do.