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

[dooglus]

Heya Doog, I gave this a try tonight and I ended up getting the message from the just-dice.com/pushtx page "transaction rejected".  This made me wonderi if I gave the private key in the wrong format.  I was using wallet import format (key starts with a 5), is that right?

When you run the big long command, you should get back something like:

{
    "hex" : "0200[...]3433",
    "complete" : true
}

If you see "false" instead of "true", it means it wasn't able to find all the private keys it needed, which in your case should just be one of them.

The private key is meant to be in WIF, starting with a 5 for BTC keys. It will also accept the corresponding CLAM, LTC, or DOGE private keys in the same format.

So that's the first thing: did you see "compete" as true or false? If false, you're giving a valid private key, but the wrong one. If true, you're likely copy/pasting incorrectly. You need to copy just the hex value, without the quotes.

[xploited]

@Clam experts: What's the leading byte for clam p2sh addresses supposed to be? x05 or x0d?

x0d is the correct one to use now. It was originally x05 but there was a situation where an old just-dice user sent clams to a multisig btc address, so to avoid any future conflicts it was changed so the leading identifier was 6 when converted to base58.

I will look into the other multisig question for you tomorrow, just on my way to sleep.

[tspacepilot]

Heya Doog, I gave this a try tonight and I ended up getting the message from the just-dice.com/pushtx page "transaction rejected".  This made me wonderi if I gave the private key in the wrong format.  I was using wallet import format (key starts with a 5), is that right?

When you run the big long command, you should get back something like:

{
    "hex" : "0200[...]3433",
    "complete" : true
}

If you see "false" instead of "true", it means it wasn't able to find all the private keys it needed, which in your case should just be one of them.

The private key is meant to be in WIF, starting with a 5 for BTC keys. It will also accept the corresponding CLAM, LTC, or DOGE private keys in the same format.

So that's the first thing: did you see "compete" as true or false? If false, you're giving a valid private key, but the wrong one. If true, you're likely copy/pasting incorrectly. You need to copy just the hex value, without the quotes.

Thanks for the debugging suggestion, I see "true".  I'm quite confident about the validity of my private key as well.  However, I'l go back and double-check all the steps.

EDIT: I re-pasted and now it says "OK".  It's a little strange because I was using the same rawtransaction data sitting there in the terminal window.  I had double-checked the quotes before I posted, who knows?  Something must have been different.  In any case, I'm sure I'l see the balance show up in my JD account shortly.  Thanks again for making the tool to produce the raw transaction so easily.

[dooglus]

EDIT: I re-pasted and now it says "OK".  It's a little strange because I was using the same rawtransaction data sitting there in the terminal window.

I don't do any kind of logging of pushed raw transactions, so I can't check the logs to see what went wrong. I'm glad it worked out for you eventually though.

Edit: since the data is intended to be publicly broadcast I don't see any harm in logging it. So I'll do that going forward. That should help to debug this issue if it happens again.

[Trent Russell]

Clam trading is "unavailable" on shapeshift.io at the moment. It's probably a good thing for me since I'm not sure I have the willpower to resist selling a few after the price spike of about 20% in the past hour. But I thought I'd point it out in case it's an issue shapeshift isn't aware of.

@Clam experts: What's the leading byte for clam p2sh addresses supposed to be? x05 or x0d?

x0d is the correct one to use now. It was originally x05 but there was a situation where an old just-dice user sent clams to a multisig btc address, so to avoid any future conflicts it was changed so the leading identifier was 6 when converted to base58.

I will look into the other multisig question for you tomorrow, just on my way to sleep.

Thanks!

[Bitcoiner2015]

What's going on? 31 Bitcoins trying to buy at Poloniex..

[chilly2k]

What's going on? 31 Bitcoins trying to buy at Poloniex..

No there are 110 bitcoins trying to buy.  There are 31 trying to buy at .0062   

[dooglus]

I'm experimenting with multisig in clams. The first part worked (creating a p2sh and sending clams to it), but the second part (spending the funds) didn't do what I expected. I found a workaround, but it's possible there's a bug in signrawtransaction. Or I made a mistake, of course. Here's more detail:

1. I used "addmultisigaddress" and created a 2-of-2 address: 6WnV4Jhe7iNQLDekwr31h9zeoK1eaDMjAw

2. I sent 0.1 clams there (small enough that it's OK if I lose it). It's txout 0 of the transaction 21db92347e153a6afdddca7f96d444d81d7daa19674ed3101e50de72cb387b19. khashier shows this transaction, but is confused by the multisig address.

3. I used "createrawtransaction" to create an unsigned tx spending this back one of my ordinary addresses.

I had one private key in my wallet and the other on paper. Using "signrawtransaction" it would sign with the one in the wallet, as expected. But then if I tried to sign with "signrawtransaction" giving the other private key explicitly in the command line, it failed. (By "failed" I mean the partially signed transaction wasn't changed.)

I can reproduce the exact same behaviour. I'll investigate, and fix it if possible. It seems to not be using the private key provided in the signtransaction RPC call.

Thanks for the report.

The problem seems to be related to the fact that signrawtransaction decides whether to use information from the wallet, or from the RPC command arguments. It won't use both.

Here's an example where I make a transaction with two simple inputs. One's private key is in the wallet, and the other's is provided in the RPC command. signrawtransaction is unable to sign it fully:

$ cc signrawtransaction $(cc createrawtransaction '[{"txid":"dddf6ac41c281317aed6445196fc14db712f0cc5812880e45eb8e534ebffd8de","vout":0},{"txid":"5bbe0ca12578cb520266178b2d6413eb2597bc251e7343b03a9d42b8733ea961","vout":0}]' '{"xJDCLAMZtRD72TC31E8SJ4a6ycFtnQyuDH":0.1}') '[]' '["'$privkey'"]' | grep complete
    "complete" : false

But if I call signrawtransaction twice, once providing the private key on the command line and once not, it is successful:

$ cc signrawtransaction $(cc signrawtransaction $(cc createrawtransaction '[{"txid":"dddf6ac41c281317aed6445196fc14db712f0cc5812880e45eb8e534ebffd8de","vout":0},{"txid":"5bbe0ca12578cb520266178b2d6413eb2597bc251e7343b03a9d42b8733ea961","vout":0}]' '{"xJDCLAMZtRD72TC31E8SJ4a6ycFtnQyuDH":0.1}') | grep hex | cut -d'"' -f4) '[]' '["'$privkey'"]' | grep complete
    "complete" : true

Edit2: here I'm able to sign a transaction spending a multisig input (2 of 2) where one key is in the wallet and the other is in $privkey. I had to provide the scriptPubKey which isn't easy to get hold of:

$ cc signrawtransaction $(cc signrawtransaction $(cc createrawtransaction '[{"txid":"2db3324af1b8e5db5ec92b85ec68226e7b17664bdff34c8e73d303c6f7011907","vout":1}]' '{"xJDCLAMZtRD72TC31E8SJ4a6ycFtnQyuDH":0.1}') | grep hex | cut -d'"' -f4) '[{"txid":"2db3324af1b8e5db5ec92b85ec68226e7b17664bdff34c8e73d303c6f7011907","vout":1,"scriptPubKey":"a914810721c3f1790b5668dcd776d2df728cb9103b8f87","redeemScript":"522103145dbd6986ff283b26d88efc2d366ee3437e64fab8c084bc766bec0b5fc41a692103fb6c6 11bf45051b192077632d79b2201577231480165c8ecb45b34c4058e530b52ae"}]' '["'$privkey'"]' | grep complete
    "complete" : true

To get the scriptPubKey, I started with the multisig address, 6SA5Wh49HnS12U3zZLvYGdFb9kDXUGx7ye, and did this:

$ python
Python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path.append("/home/chris/Programs/python-bitcoinlib/") # from https://github.com/jgarzik/python-bitcoinlib.git
>>> import bitcoin.base58
>>> import binascii
>>> 'a9' + '14' + binascii.hexlify(bitcoin.base58.decode("6SA5Wh49HnS12U3zZLvYGdFb9kDXUGx7ye")[1:-4]) + '87'
'a914810721c3f1790b5668dcd776d2df728cb9103b8f87'
>>>

0xa9 is OP_HASH160
0x14 is 20, the length of the script hash in bytes
0x87 is OP_EQUAL

The redeemScript is from here:

$ cc validateaddress 6SA5Wh49HnS12U3zZLvYGdFb9kDXUGx7ye | grep hex
    "hex" : "522103145dbd6986ff283b26d88efc2d366ee3437e64fab8c084bc766bec0b5fc41a692103fb6c6 11bf45051b192077632d79b2201577231480165c8ecb45b34c4058e530b52ae",

I made a pull request to fix this issue: https://github.com/nochowderforyou/clams/pull/194

Now I can sign a 2-of-2 transaction without having to look up the scriptPubKey or the redeemScript for the multisig address:

$ cc signrawtransaction $(cc signrawtransaction $(cc createrawtransaction '[{"txid":"2db3324af1b8e5db5ec92b85ec68226e7b17664bdff34c8e73d303c6f7011907","vout":1}]' '{"xJDCLAMZtRD72TC31E8SJ4a6ycFtnQyuDH":0.1}') | grep hex | cut -d'"' -f4) '[]' '["'$privkey'"]' | grep complete
    "complete" : true

I do still need to run signrawtransaction twice, since it will still only take private keys from EITHER the wallet OR the RPC parameters, not both at the same time.

Edit3: I thought I made this edit yesterday, but I don't see it now, so I'll make it again...

I made a better pull request which lets signrawtransaction use all available private keys and multisig scripts:
  https://github.com/nochowderforyou/clams/pull/195

I also tagged a new release:
  https://github.com/nochowderforyou/clams/releases/tag/v1.4.12

And so now you can sign your 2-of-2 multisig transaction all at once, using 1 key from the wallet and one in WIF:

$ cc signrawtransaction $(cc createrawtransaction '[{"txid":"2db3324af1b8e5db5ec92b85ec68226e7b17664bdff34c8e73d303c6f7011907","vout":1}]' '{"xJDCLAMZtRD72TC31E8SJ4a6ycFtnQyuDH":0.1}') '[]' '["'$privkey'"]' | grep complete
    "complete" : true

[PesiHUN]

i cant find calm.conf where i needed to be?

[SuperClam]

i cant find calm.conf where i needed to be?

clam.conf should be located in the data directory - you may need to manually create it.
On windows, this defaults to %appdata%/clam/
On linux, this defaults to ~/.clam/

Alternatively, this can be set via command-line flag.

[tspacepilot]

@dooglus, you alias your clamd to "cc"?  Doesn't that screw your brain because, erm, c compiler?

[dooglus]

@dooglus, you alias your clamd to "cc"?  Doesn't that screw your brain because, erm, c compiler?

I've used 'gcc' for as long as I can remember. Years ago I aliased 'bc' to 'bitcoind', then 'dc' to 'dogecoind', so clamd had to be cc really.

(And I know bc and dc are calculators, but I use Python as my command-line calculator, so that's not a problem either).

[Altis2014]

where can i create a CLAM coin wallet ?

[dooglus]

where can i create a CLAM coin wallet ?

The CLAM client will create one for you automatically the first time you run it.

It goes in the same folder as clam.conf, which SuperClam just located for us:

clam.conf should be located in the data directory - you may need to manually create it.
On windows, this defaults to %appdata%/clam/
On linux, this defaults to ~/.clam/

If you don't really want to create your own CLAM wallet, but want to use a hosted solution then there are several sites that will hold a CLAM balance for you. I don't know of any dedicated CLAM web wallets, but both poloniex.com and just-dice.com will let you deposit and withdraw CLAMs.

[Bitcoiner2015]

What's going on? 31 Bitcoins trying to buy at Poloniex..

No there are 110 bitcoins trying to buy.  There are 31 trying to buy at .0062   

Ok, what's going on, there are 100 bitcoins trying to buy and 31 at 0.0062.  Actually it looks like they have split up the order into smaller chunks, but still lots of buying pressure.

[dooglus]

Ok, what's going on, there are 100 bitcoins trying to buy and 31 at 0.0062.  Actually it looks like they have split up the order into smaller chunks, but still lots of buying pressure.

There are often ~100 BTC on the buy side. What seems to have changed is that there are no more cheap coins available at the moment. I guess the people who have been selling have run out or decided to wait for higher prices.

[freedomno1]

Ok, what's going on, there are 100 bitcoins trying to buy and 31 at 0.0062.  Actually it looks like they have split up the order into smaller chunks, but still lots of buying pressure.

There are often ~100 BTC on the buy side. What seems to have changed is that there are no more cheap coins available at the moment. I guess the people who have been selling have run out or decided to wait for higher prices.

It's a bit fun to speculate I'm going with the presumption that there is no whales that hold a lot of clams at the moment to dump in the market, and the buy pressure is strong the bankroll profit is at 100K + for now so it's just a matter of a big winner winning some clams back from the house edge.
Nice to see it at 0.669999 now ^^

[SuperClam]

Ok, what's going on, there are 100 bitcoins trying to buy and 31 at 0.0062.  Actually it looks like they have split up the order into smaller chunks, but still lots of buying pressure.

There are often ~100 BTC on the buy side. What seems to have changed is that there are no more cheap coins available at the moment. I guess the people who have been selling have run out or decided to wait for higher prices.

It's a bit fun to speculate I'm going with the presumption that there is no whales that hold a lot of clams at the moment to dump in the market, and the buy pressure is strong the bankroll profit is at 100K + for now so it's just a matter of a big winner winning some clams back from the house edge.
Nice to see it at 0.669999 now ^^

We are still a relatively small market, so there will be shenanigans.

That said, it doesn't hurt that there are still less than 750k CLAM in active circulation

[romjpn]

Yes guys, for the website just take any simple Wordpress theme or whatever CMS. I think many people don't understand how the heck you navigate on the official website  .
Anyway, CLAM and JD are amazing together ! Around 400$ profit so far .

[SuperClam]

Yes guys, for the website just take any simple Wordpress theme or whatever CMS. I think many people don't understand how the heck you navigate on the official website  .
Anyway, CLAM and JD are amazing together ! Around 400$ profit so far .

I have been putting work in on it; though I became side-tracked today working on a stand-alone community application for social campaigns and such