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

[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

[Trent Russell]

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:

...

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.

...

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.

Thanks for this reply. It helps me a lot. Plus it's good in general to see that these reports can lead to such fast action.

By the way, I'm doing these multisigs to test out an idea I posted about a few weeks ago:

https://bitcointalk.org/index.php?topic=1078338

It seems like a good application of clamspeech. When I'm satisfied with the results, I'll post details about the outcome and link to it from here.

[ShapeShift.io]

Clam friends! ShapeShift has re-added Clams to our instant altcoin exchange! So for the downtime. Instantly exchange Clams with 35+ altcoins today with ShapeShift.io

[dooglus]

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.

Thanks for this reply. It helps me a lot. Plus it's good in general to see that these reports can lead to such fast action.

I improved on my fix after posting that, and edited the post you quoted. You can now do what you were trying to do with a single 'signrawtransaction'. The change will be in v1.4.12 of the client, which should be built shortly. The sources are already available for you to build yourself if you're that way inclined.

By the way, I'm doing these multisigs to test out an idea I posted about a few weeks ago:

https://bitcointalk.org/index.php?topic=1078338

It seems like a good application of clamspeech. When I'm satisfied with the results, I'll post details about the outcome and link to it from here.

I look forward to reading about it.

[SuperClam]

CLAM v. 1.4.12 Test Build Released!
Release Notes

Linux 32bit
68500109793daa68f2fe87c54281bccc73405d9dff39099ad7e65a38e2c51533

Linux 64bit
6cee1813a8b13f1e8736a3447d74549b779ae4fc5a6e543fef6abe10896a306b

Windows 32bit
6f1e0363cca3a80ceefb23b6db67f1bb99081191aa9d7e8ebf1f0f4ffa0cc44b

Windows 64bit
20f89ba18481075e50eeaf0528aefd85fe73ce0b6de7eb5c27cb7a4e7b7eac08

OSX
811f94d63501f23eed79719057976fb51cf75052950dca8102127d7030d12361

[dooglus]

Release Notes

Thanks!

You might want to link to the specific release notes for that version:
  https://github.com/nochowderforyou/clams/releases/tag/v1.4.12

[SuperClam]

Release Notes

Thanks!
You might want to link to the specific release notes for that version:
  https://github.com/nochowderforyou/clams/releases/tag/v1.4.12

Fixed

[dooglus]

One thing that seriously has me bothered is the address that is sending outputs on coinstake transactions... I will need to perhaps reindex my db to deal with that.

I forgot to address that.

I created those weird staking transactions yesterday as an experiment.

[...]

So you won't find too many of those weird transactions in the blockchain so far

I just noticed I left my experimental staking code running since I posted that. It has created thousands of ugly multi-input multi-output staking transactions. So much so that the address I was using jumped to #4 in the CLAM rich-list. Ugh. I've now begun merging all those small outputs back to the main JD staking address, a bit at a time:

http://khashier.com/tx/77dd83f67379d7fd01b9665b5bd287e1e6dc63b07361b07279e2beb9ec2af134

Edit: but this whole experiment / mistake gave me an idea...

A few exchanges recently have been having problems with their CLAM wallets, where they fill up with 'dust' from faucets which costs more in transaction fees to spend than it is worth. That's not a good situation - the exchange either has to pay out of pocket to clean up the dust, or leave it polluting the blockchain in the form of unspent outputs forever.

So how about if we add an option to allow the wallet to combine all the dust into a single new output each time it stakes?

I wrote it up here: https://github.com/nochowderforyou/clams/issues/196 and pushed a commit implementing it to the repository. It'll be in the next CLAM client release unless there's a good reason that it shouldn't be.

Here it is cleaning up dust from the Just-Dice hot wallet, and getting paid to do so:



Edit: here's a better example: http://khashier.com/tx/1f879d7896af66e4d533e49d9b49bc7d10f1d0e9b792aa5bcf85c5bda608ebf8

[SuperClam]

One thing that seriously has me bothered is the address that is sending outputs on coinstake transactions... I will need to perhaps reindex my db to deal with that.

I forgot to address that.
I created those weird staking transactions yesterday as an experiment.
[...]
So you won't find too many of those weird transactions in the blockchain so far

I just noticed I left my experimental staking code running since I posted that. It has created thousands of ugly multi-input multi-output staking transactions. So much so that the address I was using jumped to #4 in the CLAM rich-list. Ugh. I've now begun merging all those small outputs back to the main JD staking address, a bit at a time:
http://khashier.com/tx/77dd83f67379d7fd01b9665b5bd287e1e6dc63b07361b07279e2beb9ec2af134
Edit: but this whole experiment / mistake gave me an idea...
A few exchanges recently have been having problems with their CLAM wallets, where they fill up with 'dust' from faucets which costs more in transaction fees to spend than it is worth. That's not a good situation - the exchange either has to pay out of pocket to clean up the dust, or leave it polluting the blockchain in the form of unspent outputs forever.
So how about if we add an option to allow the wallet to combine all the dust into a single new output each time it stakes?
I wrote it up here: https://github.com/nochowderforyou/clams/issues/196 and pushed a commit implementing it to the repository. It'll be in the next CLAM client release unless there's a good reason that it shouldn't be.
Here it is cleaning up dust from the Just-Dice hot wallet, and getting paid to do so:

The only argument I can think of would involve the bloat or lack of tx fees.
Might be reasonable argument for some sanity limits.

That said, I think it would also incentivize services to stake.

[dooglus]

The only argument I can think of would involve the bloat or lack of tx fees.
Might be reasonable argument for some sanity limits.

That said, I think it would also incentivize services to stake.

But it's removing bloat, in the form of unspent transaction outputs. It leaves a bunch of spent dust, which presumably in the future will be prunable. Unspent outputs sticking around forever aren't prunable.

There should be fees for creating dust, not for tidying it up.

Edit: as for the lack of fees, fees are paid to whoever stakes the block - so I'd be paying myself...

[SuperClam]

The only argument I can think of would involve the bloat or lack of tx fees.
Might be reasonable argument for some sanity limits.
That said, I think it would also incentivize services to stake.

But it's removing bloat, in the form of unspent transaction outputs. It leaves a bunch of spent dust, which presumably in the future will be prunable. Unspent outputs sticking around forever aren't prunable.
There should be fees for creating dust, not for tidying it up.
Edit: as for the lack of fees, fees are paid to whoever stakes the block - so I'd be paying myself...

The pruning argument is definitely persuasive.

[presstab]

The only argument I can think of would involve the bloat or lack of tx fees.
Might be reasonable argument for some sanity limits.

That said, I think it would also incentivize services to stake.

But it's removing bloat, in the form of unspent transaction outputs. It leaves a bunch of spent dust, which presumably in the future will be prunable. Unspent outputs sticking around forever aren't prunable.

There should be fees for creating dust, not for tidying it up.

Edit: as for the lack of fees, fees are paid to whoever stakes the block - so I'd be paying myself...

The difference between your implementation and standard PPC is that you add the ability to combine outputs from multiple keys held by the same wallet? Interesting idea, and of course you will have to own those keys in order to sign the transaction over. An exchange would then have to stake their wallets in order to take advantage of this. Some exchanges have been known to stake, as far as I know poloniex does not stake their wallet.

Your doing some really interesting work, keep it up

[dooglus]

The difference between your implementation and standard PPC is that you add the ability to combine outputs from multiple keys held by the same wallet? Interesting idea, and of course you will have to own those keys in order to sign the transaction over. An exchange would then have to stake their wallets in order to take advantage of this. Some exchanges have been known to stake, as far as I know poloniex does not stake their wallet.

Your doing some really interesting work, keep it up

I'm not familiar with PPC, but I expect it's the same as CLAM in this respect. The client doesn't attempt to merge outputs belonging to different keys, but it will accept it when others do so. So you can unilaterally modify your client to do it, and your peers won't mind.

Poloniex don't stake their wallet. I've made large deposits and watched them site idle for days, when they would almost certainly have staked many times in that period if the wallet was being staked.

I don't know why they don't. If they staked their wallets and gave a share of the rewards to whoever holds the CLAM balances, that would give them a competitive advantage over the other altcoin exchanges. They seem to be losing ground to cryptsy according to coinmarketcap.com/currencies/clams/#markets - when I looked a couple of weeks ago poloniex had 98% of the recent volume, with bittrex and cryptsy having less than 1% each. Now they're down to 72% which cryptsy at 18%. And not staking is really just throwing away free money.