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

[dooglus]

I forked bitaddress.org and changed it to work with CLAM addresses:
  https://github.com/dooglus/bitaddress.org

I need the graphics updated if anyone has the time and skills required.

It's up at:

  https://clamaddress.org

I made some crappy 'art' for the logo and wallets. I'm happy to accept better versions.

[dooglus]

Here is some info from my debug.log file that might help. If you want the whole thing I can get that for you too.

Code:

$ cat debug.log | grep ORPHAN > debug_orphans
$ cat debug_orphans | curl -F 'clbin=<-' https://clbin.com
https://clbin.com/FTBHj

I tried syncing from scratch. It worked flawlessly. I only saw 414 orphans in total, so never hit the 750 limit:

$ grep ORPHAN debug.log | wc -l
414

I guess it depends which peer you're downloading from.

[SebastianJu]

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

I forked bitaddress.org and changed it to work with CLAM addresses:
  https://github.com/dooglus/bitaddress.org

I need the graphics updated if anyone has the time and skills required.

It's up at:

  https://clamaddress.org

I made some crappy 'art' for the logo and wallets. I'm happy to accept better versions.

[dooglus]

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?

[thefix]

Ok thanks for the help, I'll send them a message and see if they may be able to point me in the right direction.

Include the CLAM community into your distribution - and we will go so far as to provide scripts or even do it for you

Before you take the CLAM snapshot give me a second to split the JD staking wallet into 100,000 different addresses...
ftw
Edit: and by that I mean you should make sure the snapshot date is some time before now. Because otherwise people will abuse it.

Or, distribute based proportionally to balance.
Or, alternatively, distribute at a minimum balance that is high enough to make splitting likely negative expected value.

Is this talk about a new coin distributed to Clam addresses?

[dooglus]

Is this talk about a new coin distributed to Clam addresses?

Yes. But there's no reason to believe it will happen.

[thefix]

Is this talk about a new coin distributed to Clam addresses?

Yes. But there's no reason to believe it will happen.

Bummer, I was picturing Pearlcoin with a chance of finding one in every Clam!

[dooglus]

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.

[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?