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

[dooglus]

Still only have 1 active connection. If this is the norm, CLAM looks more centralized then decentralized.

I just downloaded the 1.4.13 windows 64bit wallet and its syncing pretty fast, but its only connected to 1 active connection. This is after filling the clam.conf with a list of active nodes. What am I doing wrong?

Try adding this to clam.conf:

addnode=144.76.185.69:31174
addnode=199.233.246.224:31174
addnode=104.236.69.105:31174
addnode=104.236.149.112:31174
addnode=88.198.207.8:31174
addnode=162.213.195.88:31174
addnode=108.73.85.204:31174
addnode=104.236.83.126:31174
addnode=144.76.64.123:31174
addnode=176.37.47.241:31174
addnode=151.224.82.4:31174
addnode=128.199.167.77:31174
addnode=91.232.105.11:31174
addnode=52.5.155.203:31174
addnode=74.207.230.61:31174
addnode=144.76.239.66:31174
addnode=104.236.69.34:31174
addnode=216.73.219.20:31174
addnode=198.50.243.84:31174
addnode=151.80.33.164:31174
addnode=186.4.30.88:31174
addnode=109.236.85.42:31174

[dooglus]

Version 1.4.16 of the CLAM client has been released.

See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.

[SuperClam]

Version 1.4.16 of the CLAM client has been released.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.

We would love to get this one upgraded to STABLE as soon as possible, given the DNS seed part of the changelog.

The more that can test this release and report possible problems - the better.

Thanks


EDIT: Also, the more that can get https://github.com/dooglus/bitcoin-seeder/tree/clam working and stable on long-term server resources, the better.

[dooglus]

Version 1.4.16 of the CLAM client has been released.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.

We would love to get this one upgraded to STABLE as soon as possible, given the DNS seed part of the changelog.

The more that can test this release and report possible problems - the better.

Thanks

A Mac build would be good too. I would make my own, but the instructions I was following included a step that needed to be done on a Mac and I won't have them in the house.

[tspacepilot]

Version 1.4.16 of the CLAM client has been released.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.

We would love to get this one upgraded to STABLE as soon as possible, given the DNS seed part of the changelog.

The more that can test this release and report possible problems - the better.

Thanks

A Mac build would be good too. I would make my own, but the instructions I was following included a step that needed to be done on a Mac and I won't have them in the house.

I understand what you mean, they have terrible manners at the dinner table and they're impossible to potty-train.  However, if you make them a nice place in the backyard they can probably get along with your rabbits. 

[dooglus]

EDIT: Also, the more that can get https://github.com/dooglus/bitcoin-seeder/tree/clam working and stable on long-term server resources, the better.

If anyone gets a server set up running that code and acting as a DNS server, please post the domain name so I can add it to the CLAM client source, for inclusion in a future release. Thanks.

[Lenore]

Hello everyone,  Weird that I tried to post and it wouldn't let me.  Saying that I have posted within 360 seconds and I have to slow down.  But yet I haven't ever posted.  This is my first post however I am a troll.

Anyways.   I have a question about the CLAM Client.   I was looking threw the debug file.  And every once and a while I see the word "DIG".  What does that mean.  I get what error and accepted mean but every once and a while I see the "DIG" word.

Thank you.   Have a great day everyone.

[tspacepilot]

Hello everyone,  Weird that I tried to post and it wouldn't let me.  Saying that I have posted within 360 seconds and I have to slow down.  But yet I haven't ever posted.  This is my first post however I am a troll.

Probably the previous "post" in that context was your login.  I agree that the wording seems wrong.

Anyways.   I have a question about the CLAM Client.   I was looking threw the debug file.  And every once and a while I see the word "DIG".  What does that mean.  I get what error and accepted mean but every once and a while I see the "DIG" word.

Thank you.   Have a great day everyone.

"digging" is when new clams are made active from the initial distribution.  That is, if I understand correctly, the initial distribution of CLAMS was such that BTC,LTC, or DOGE addresses which were funded above a certain dust threshold on some date in 2014 (May something?) were set up so that the private key from these addresses could be used to fund a clam address with like 4.6 clams.  People refer to new clams being entered into this system from this initual distribution as being "dug up".

[Lenore]

So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).

Just curious ass to why it says "DIG" in the debug file.   Thinking it was answered I just didn't pick up on it.  I know that coins are dug up and all from the previous transactions in the block chain.  Is it that when it says "DIG" I'm producing new coins?

Just want to make sure I have all this correct.

[SuperClam]

So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).
Just curious ass to why it says "DIG" in the debug file.   Thinking it was answered I just didn't pick up on it.  I know that coins are dug up and all from the previous transactions in the block chain.  Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.

There is no way to precisely define, let alone identify, when a key has been imported into the client.

That said, the "DIG" you are referring references a distribution output which has moved or staked for the first time.

[chilly2k]

So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).
Just curious ass to why it says "DIG" in the debug file.   Thinking it was answered I just didn't pick up on it.  I know that coins are dug up and all from the previous transactions in the block chain.  Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.

There is no way to precisely define, let alone identify, when a key has been imported into the client.

That said, the "DIG" you are referring references a distribution output which has moved or staked for the first time.

Plus, Your (Lenore) looking at your debug file.  You should know if you imported a private key, or wallet.dat.  If not, then the "dig" your seeing are other people digging clams.  

[dooglus]

So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).

Just curious ass to why it says "DIG" in the debug file.   Thinking it was answered I just didn't pick up on it.  I know that coins are dug up and all from the previous transactions in the block chain.  Is it that when it says "DIG" I'm producing new coins?

It says "DIG" each time it accepts a block that moves one of the initial distribution outputs. If you're syncing the blockchain, you'll see it a lot as it accepts lots of blocks quickly. It doesn't distinguish between outputs owned by you and those owned by others.

There's no good reason for it to still be in the debug file really.

If you go to the 'console' page, type 'getinfo' and hit return, you'll see a bunch of information including something like the following:

    "moneysupply" : 15250588.13048927,
    "digsupply" : 329552.59638718,
    "stakesupply" : 476186.72641731,
    "activesupply" : 805739.32280449,

The "digsupply" number is the total number of coins from the initial distribution that have moved so far. As your client syncs, that number will increase. The "activesupply" is the sum of "digsupply" and "stakesupply", where "stakesupply" is the total number of coins created by staking.

[0rganic]

Sorry...slightly off topic )

I'm interested in retrieving  some clams from my reddit doge user account, in light of that....

Do you know who would owns the private keys of my dogetipbot address on reddit?, 
would it be me, or Mohland of dogetipbot?

Thanks for your help )

[oldkolobok]

Is it still possible to redeem CLAM's with old BTC & LTC wallets? Cant find the info in the OP.

[dooglus]

Is it still possible to redeem CLAM's with old BTC & LTC wallets? Cant find the info in the OP.

Here's what I wrote last time someone asked the same question. Maybe OP needs to be improved?

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

[oldkolobok]

Is it still possible to redeem CLAM's with old BTC & LTC wallets? Cant find the info in the OP.

Here's what I wrote last time someone asked the same question. Maybe OP needs to be improved?

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

Thank you. Ill try to load the wallets into the client. Do I need to wait for the full blockchain to sync? Or is there a bootstrap somewhere?

Edit: Found the bootstap in OP

[oldkolobok]

The client doesnt detect the bootstrap.dat file. Just skips straight to syncing... Its placed in the correct Appdata folder. What do ?

[tspacepilot]

The client doesnt detect the bootstrap.dat file. Just skips straight to syncing... Its placed in the correct Appdata folder. What do ?

I haven't synced with the clamclient.  One thing you can try if using the client is awkward is the other method suggested by dooglus, to use the Just-Dice chat robot to dig for you.

[oldkolobok]

Ok thanks ill try it. By the way, how are the addresses rewarded? First time seen on the network?, # of transactions?

[chilly2k]

Ok thanks ill try it. By the way, how are the addresses rewarded? First time seen on the network?, # of transactions?

  Non-dust balance on May (14?) 2014.  All rewarded 4.6 clams.