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

[casinobitco]

Thanks doog!

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

I fixed the issue today and made a new release:

  https://github.com/nochowderforyou/clams/releases/tag/v1.4.15

I'm guessing that official binaries will be linked from the OP soon.

[GordoZ]

Hi. I wold like to invite you to see a Counterparty asset based on CLAM distribution. XCLAM.
https://bitcointalk.org/index.php?topic=1133581.0
Thanx for reading!

[Cyrax89721]

I visited Dooglus' new www.clamaddress.org site and printed & laminated myself a paper wallet. 

Looks sexy.

[brettbarth]

I added clamcoin last night to my staking portfolio. Are there any tweaks I need to do to the wallet or is it a "set it and forget it" stake coin?

Any help is greatly appreciated.


-Brett

[dooglus]

Thanks doog!

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

I fixed the issue today and made a new release:

  https://github.com/nochowderforyou/clams/releases/tag/v1.4.15

I'm guessing that official binaries will be linked from the OP soon.

I uploaded binaries here: https://github.com/nochowderforyou/clams/releases/tag/v1.4.15

I don't know how to make OSX binaries with access to a Mac, so I only made Linux and Windows binaries.

Edit: xploited uploaded an OSX binary there too.

[dooglus]

I added clamcoin last night to my staking portfolio. Are there any tweaks I need to do to the wallet or is it a "set it and forget it" stake coin?

Any help is greatly appreciated.


-Brett

There's nothing much you need to do other than making sure your client is fully synced with the blockchain. If you're having trouble with that, my post here links to a bootstrap file that will help.

For better staking efficiency you can split your outputs up into pieces of around 10 CLAMs each, but the wallet will do that for you automatically in time anyway.

[dooglus]

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.

So only the staked 1 Clam coin will move to the specified address? will it work like the send 4 charity feature on other wallets?

No, the whole output will go to the specified address, but now I've added another new flag, -rewardto=ADDR, which sends just the block reward to the specified address:

See this transaction for instance. It was staked with:

  rewardto=xJDCLAMZSGaTadAzcS7tcVNTa46qCr6j2s                                                                                                  
  staketo=xJDCLAMZkcp7fQ3ieHfZA4SLu3aTy2Y1mr                                                                                        

So the reward goes to one address and the rest goes to a different address, and both are different than the address which is staking.

It will be in the next release of the client, v1.4.16.

[shawn2025]

Is there an advantage to running the beta versions? 

Running Mac 1.4.11 now.  Hesitant to update.  Pros - Cons? 

Thanks!  

/s/

[tspacepilot]

Is there an advantage to running the beta versions? 

Running Mac 1.4.11 now.  Hesitant to update.  Pros - Cons? 

Thanks!  

/s/

Really the advantages would either be in:

1) some critical fix that's in the new version
2) some new features

If you're not suffering from an issue in the old client that's fixed in the new version and you're not chomping at the bit to try out the new features (described in just the preceding posts) then you're probably not going to be in a rush to upgrade.

The pros are clearly the new features.  The cons are the risk that the less tested betas won't work right on your setup.  I don't think we can tell you how to balance those things for your personal goals, you'll have to figure them out yourself, right?

[dooglus]

Is there an advantage to running the beta versions? 

Running Mac 1.4.11 now.  Hesitant to update.  Pros - Cons? 

Thanks!  

/s/

"Beta" is kind of an arbitrary designation. The older versions have been around for longer, and so are less likely to contain surprises. The newer versions have more features and bug fixes, but potentially new bugs too.

There's a high-level list of the differences between each version here. But briefly:

v1.4.12 fixed a problem that several exchanges encountered, where if you have a lot of people sending tiny 'faucet' deposits to your wallet, you can end up with so much 'dust' that you can't make transactions any more. Tiny outputs cost more in fees to spend than they are worth, which caused a problem that this version fixed.

v1.4.13 and v1.4.14 didn't add much of any importance.

v1.4.15 updates the list of seed nodes. So if you're having trouble finding peers to connect to, that might help you. It also fixes a bug that prevented the RPC interface working on Windows, and adds code to ban misbehaving peers - so if you have a peer that is re-downloading the same blocks from you over and over and wasting your bandwidth, you might want to upgrade.

I'll be tagging v1.4.16 in the next day or two, which will use dynamic seeds that will always provide fresh peer addresses rather than using a hardcoded list of peers.

I would recommend using the newest version you can at the moment. I really don't think any of the recent changes will have introduced new problems.

[Guns1inger]

Can someone point me to a SIMPLE step by step how to claim clams from my ANDROID Doge wallet (on my phone)?

Edit:
Or was an Android wallet even out when clams were distributed??   Maybe I don't have any clams from that phone wallet?

Thanks in advance...  I can't seem to find an easy way to do this.  
 

[dooglus]

Can someone point me to a SIMPLE step by step how to claim clams from my ANDROID Doge wallet (on my phone)?

Edit:
Or was an Android wallet even out when clams were distributed??   Maybe I don't have any clams from that phone wallet?

Thanks in advance...  I can't seem to find an easy way to do this.

Is there only one DOGE wallet for Android? What's it called? Does it have some way of backing up the wallet or exporting the private keys?

[Guns1inger]

Can someone point me to a SIMPLE step by step how to claim clams from my ANDROID Doge wallet (on my phone)?

Edit:
Or was an Android wallet even out when clams were distributed??   Maybe I don't have any clams from that phone wallet?

Thanks in advance...  I can't seem to find an easy way to do this.

Is there only one DOGE wallet for Android? What's it called? Does it have some way of backing up the wallet or exporting the private keys?

Umm its this one by Langerhans
https://play.google.com/store/apps/details?id=de.langerhans.wallet
https://github.com/langerhans/dogecoin-wallet-new
I think there is a way to back it up and export but I don't know how

[SuperClam]

"Beta" is kind of an arbitrary designation. The older versions have been around for longer, and so are less likely to contain surprises. The newer versions have more features and bug fixes, but potentially new bugs too.

There's a high-level list of the differences between each version here. But briefly:

v1.4.12 fixed a problem that several exchanges encountered, where if you have a lot of people sending tiny 'faucet' deposits to your wallet, you can end up with so much 'dust' that you can't make transactions any more. Tiny outputs cost more in fees to spend than they are worth, which caused a problem that this version fixed.

v1.4.13 and v1.4.14 didn't add much of any importance.

v1.4.15 updates the list of seed nodes. So if you're having trouble finding peers to connect to, that might help you. It also fixes a bug that prevented the RPC interface working on Windows, and adds code to ban misbehaving peers - so if you have a peer that is re-downloading the same blocks from you over and over and wasting your bandwidth, you might want to upgrade.

I'll be tagging v1.4.16 in the next day or two, which will use dynamic seeds that will always provide fresh peer addresses rather than using a hardcoded list of peers.

I would recommend using the newest version you can at the moment. I really don't think any of the recent changes will have introduced new problems.

Added the newest client version 1.4.15 to the OP post.


For those curious, here are the release notes for the four most recent versions:


1.4.15 - LINK

Ban forked peers who are stuck in a getblocks loop.
Add -staketo flag to allow us to move coins from one address to another as they stake.
Updated peer list to current node list from blocktree
Fix formatting on Windows when building using MinGW.

1.4.14 - LINK

Add optional 3rd parameter to dumpbootstrap to specify the first block number to dump.
Add a checkpoint at block 530,000. The last one was back in December last year.
New option -stake=<addr> to limit which outputs are allowed to stake to only those with the given address(es).

1.4.13 - LINK

Always show scriptPubKey in validateoutputs output, even for spent outputs.
Add -combineany flag to allow staking to merge any small outputs together regardless of their address.
Add raw parameter to getblock and getblockbynumber to allow dumping of raw block data suitable for use with submitblock.

1.4.12 - LINK

Fixed an issue with coin selection; previously the client would attempt to create transactions over 100kB in size if there were too many 'dust' outputs in the wallet. (dooglus)
Modified the signrawtransaction RPC command such that it will now use all available private keys to sign the transaction; previously if you specified private keys in the RPC command itself, it would only use those private keys and would ignore any in the wallet. It also wouldn't look up the scripts for multisig addresses in the wallet if keys were supplied in the RPC command. Now it does. (dooglus)
Changed Bitcoin references to Clam. (FuzzyHobbit)

[tspacepilot]

Can someone point me to a SIMPLE step by step how to claim clams from my ANDROID Doge wallet (on my phone)?

Edit:
Or was an Android wallet even out when clams were distributed??   Maybe I don't have any clams from that phone wallet?

Thanks in advance...  I can't seem to find an easy way to do this.

I think you can start by verifying that your DOGE address(es) were funded using the Just-Dice chat.  I assume it works for any BTC,LTC,or DOGE address. 

1) got to just-dice.com
2) write in the chat "/dig YOURDOGEADDRESS"

That should print a message about whether or not your address was funded.  If it was funded, you can then see about extracting your private key from that app, if it wasn't funded, then you don't have to bother with it.

[SuperClam]

Can someone point me to a SIMPLE step by step how to claim clams from my ANDROID Doge wallet (on my phone)?
Edit:
Or was an Android wallet even out when clams were distributed??   Maybe I don't have any clams from that phone wallet?
Thanks in advance...  I can't seem to find an easy way to do this.

I think you can start by verifying that your DOGE address(es) were funded using the Just-Dice chat.  I assume it works for any BTC,LTC,or DOGE address. 
1) got to just-dice.com
2) write in the chat "/dig YOURDOGEADDRESS"
That should print a message about whether or not your address was funded.  If it was funded, you can then see about extracting your private key from that app, if it wasn't funded, then you don't have to bother with it.

I hate to repeat myself - but, this is an important concept that users utilizing individual address check/claim systems need to understand:

Bitcoin based systems do not work like the vast majority of people believe.

Coins are stored on chain in what are called "outputs". 
Every single time that a transaction is sent, the TOTAL value of every involved output must be accounted for - this is important.
This most often results in what are called "change" addresses.

Essentially, your wallet software sends the remainder of any output not entirely "used" by the transaction to a new address.
This address is not an address that you manually created and is controlled by a private key which you likely do not even know that your wallet controls.


What does this mean for users attempting to claim distribution CLAMs?

If you are one of the few users who understand how "change" addresses function and are capable of ensuring that you check and claim every single key that could possibly control CLAMs, nothing.

However, most users are very likely to find that claiming the entire wallet (which automatically checks all keys, including "change" address controlling keys) results in a larger amount of CLAMs claimed.
This is accomplished by importing the wallet into the CLAM client directly.

[SebastianJu]

Oh, is bitaddress.org yours too or did you rip their design only? I used bitaddress quite some time already.

No, bitaddress.org isn't mine. It's open-source, so I forked it and made a CLAM version. I also used a small bit from https://bitcoinpaperwallet.com/bitcoinpaperwallet/generate-wallet.html (which itself is based on bitaddress.org) to allow skipping of the entropy collection.

Could this be the first CLAM paper wallet in the world?



He used photoshop to replace the low-resolution image produced by clamaddress.org with a higher resolution version. I wonder how best to allow clamaddress.org to produce print-ready images itself, while still fitting on the screen. Any ideas?

If its written in php then there are certain libraries that can create images out of text and such things. Its widely used with typo3, the cms, and it creates nice images. Im not sure what you will use it for but these things exist. Though they are rather big and they have a learning curve. At the end it will be easy.

[Guns1inger]

This is accomplished by importing the wallet into the CLAM client directly.

So how do I get the wallet off my phone and do that? 

Do I have to file transfer from the phone somehow?

[tspacepilot]

This is accomplished by importing the wallet into the CLAM client directly.

So how do I get the wallet off my phone and do that?  

Do I have to file transfer from the phone somehow?

It still might be worth it to see if you have any clams in one of your "non-change" addresses before you go through the hassle.  Depending on your wallet software, you may be able to print a list of all your addresses and what their balances are (akin to listreceivedbyaddress in bitcoind-RPC).  If I were you, I'd assure myself there's at least some clams to be gotten, then I'd go about figuring out how to do the wallet import into the clam client (if it turns out yu have more than one address to claim from).

EDIT: some wallets, espcially mobile ones from a while ago actually use the sending address as the change address (not as common now that HD wallets are here) so you may actually only have the addresses you manually generated.

[Guns1inger]

Uggghhh I can't get my address off the phone,  I can't see it.

The wallet keeps saying "Dogecoin wallet has stopped working" when I try to edit to see the whole address

Maybe I should just forget trying to get clams from that.