Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 454. (Read 1151252 times)

CLAMS State of the Chain

-Total number of public keys(BTC,LTC,DOGE) seen from initial distribution: 9,265
-Amount claimed from initial distribution: 42,670
-Lottery winnings: 12,534
-Staked earnings: 4021
-Total CLAMS in circulation: 59,272
-Approx. Market Cap: $30,000 USD

There seems to be a bit of misunderstanding as to how the CLAM Shell actually functions.


The CLAM Shell doesn't "roll out". 
It simply exists in the order book as buy orders.


There are no upward pushing, "moving" buy orders.
This would cause CLAMS to be purchased at above market price...
For? A pump? Not the purpose.


Not true.  The CLAM Shell is made up of exactly 25% (deposit amount * 0.25) of the pool's proceeds.

I think that would have likely been a superior idea, and was indeed the "original" idea -> why didn't we do it that way?


^ This.  It is difficult enough maintaining hash @ the pool.
kHashier.com has the longest term payout system in existence.
It makes p2pool look like it was designed for instant gratification - and yet even p2pool receives complaints about the slow build up of payouts.

Crypto is a short-term mind-set community.
That is understandable; we get it.
However, the CLAMS multi-pool will NOT perform well for short-term mining or pool hopping.
It was designed to not perform well over the short-term.

---

Synopsis:

• The pool sells the block reward from mining for BTC, like any other multi-pool.
• The resulting BTC, minus fees is accrued at Poloniex in order to purchase CLAMS.
• 25% of arriving BTC is immediately placed into a Buy order at 75% of the highest current significant buy order.
• If the price goes up such that the buy order falls to less than 50% of the highest current significant buy order, it is canceled and placed again at 75% of the highest current significant buy order.
• If one of the buy orders is sold into, the resulting purchased CLAMS are periodically withdrawn and paid out to miners during the normal payout cycle.
• The remaining 75% of BTC arriving at Poloniex is used to place purchases of CLAMS that are periodically withdrawn and make up the normal payout cycle.
• All payouts, (25%)CLAM Shell or (75%)regular, are apportioned to miners in CLAMS based on their accrued percentage.
• This includes our fee; which we take in CLAMS.

If you have any additional questions, I am happy to answer them.

What happened to the Clam Shell?

A 50% decline even on tiny volume should have rolled out the Clam Shell...
Meaning 100 or 200 size support bids just below the market... like we've seen previously.

In fact, the Clam Shell should not be predictable...
It should occasionally sweep the Order Book on the up side for no reason other than flex buying muscle.

As far as I understand...
Clam Shell buying is also the only way Pool Participants get paid....
And the Pool is not doing well because the payouts are a fraction of any other scrypt pool.

The 'getCLAMS' people are an unfortunate situation.

They launched after us, and it appears they didn't even bother doing a cursory check to see if the name was taken.
At least the ticker symbol is different.

Alas, it is a free world.

I think the problem is not many people know about clams, or they think it is the same coin as the defunct coin that shares the name. This is why I was pushing for more exchanges. If nothing else it will be a form of advertising. I tried to get it added to c-cex voting list, but the other clams is still on there so it did not work out.

Depending on whether you tell it to rescan or not, it will add the private key, and either rescan (taking a few minutes) or not.

If you have several to add, you should tell it not to rescan on all but the last import, to save time.

Then you'll see the CLAMs in your wallet


I never tried giving khashier a BTC address, so I'm not sure what it does with them.


Yeah. I'm back in business.


No, your CLAM privkey is the same as your BTC privkey. The public keys are the same too. The addresses are only different because of the byte added at the start to make BTC addresses start with a '1' and CLAM addresses with an 'x'.

If you dumpprivkey you'll get the same from the BTC wallet as from the CLAM one if you use addresses which correspond to each other.

thanks @SuperClam @tryphe @dooglus for answering my questions promptly
and as I understand it if we do it via wallet.dat, we need to do the --salvagewallet option
so if we do the importprivkey [btcprivkey] on the CLAM client, do we need to do something else
what should I expect to happen? I haven't downloaded the client, so I cannot try it myself


I have no way to try that script out but isnt doing a search on khashier give me the same result?
btw I couldn't open khashier blockchain for some unknown reason occasionally, anyone experiencing it too?
anyway, what I do was:
go to http://khashier.com:2750/ and enter my btc address there
on the result page I clicked on the first link with btc address on it
then it brings up another page with a CLAM balance and a link to its CLAM address
am I wrong assuming this CLAM address corresponding to my btc priv key? 


woooowww 500/day is equal min 50 CLAMs
and sorry for your recent mishap, but that would be just a minor setback
just need to split them up and wait another 8 hours to mature, right?


meaning it is the only way to claim ownership of my CLAM address and not the actual priv key of that CLAM address, right?
because if I were to dumpprivkey that CLAM addr, the priv key would be completely different from the btc priv key I entered, right?
ok this is becoming too long for a simple post... I will try to join the irc see if I can learn more over there

I recently made a huge mistake with my CLAM wallet which resulted in ~70% of my old CLAM outputs getting merged together into large new outputs.

So my ability to stake has been hugely reduced.

Oops!

I don't agree, entirely.
Do more CLAMS == more stakes? Yes, same as plain-ole' Proof-Of-Stake.

The primary difference, imho, is that with Proof-Of-Pearl this effect is less significant than with conventional Proof-Of-Stake.

With conventional proof-of-stake, not only does more more coins = more stakes (and additional compound interest); but the amount of the reward itself is based on the size of the pile.

At least with proof-of-pearl the reward per block is not greater for those with more coins.

---

Regardless, fairness is a primary concept for CLAMS.
C. L. A(equitas). M.

There are some great ideas being bandied about to level the playing field even more-so, while still preserving what is justifiably a greater return for a greater investment.

More importantly, we are always listening to ideas; stop by #clams @ irc

Is nobody else concerned with the price these days? Noticed someone cleared out a bunch of the buy orders.

That's the downside with this form of PoS... your chance of winning grows exponentially as you stake and your balance grows, thus giving you more staking power. The more you win, the more you CAN win.

congratulation on the lottery win, at least we know for sure that those 900+ clams wont be dumped

even without the lottery win with ~500 stakes a day thats 50 clams a day, awesome

im currently only at 1 stake a day and still waiting for that lottery so i can increase my daily number of stakes  

Re: dooglus,
All accurate information, as usual


Re: gjhiggins.
For users who are particularly concerned, the process you outlined remains possible and recommended.

Thanks for clarifying that.

A precise identification of the address as the lynchpin. IIRC, the original instructions suggested that, for maximum peace of mind, any balance in a qualifying BTC/LTC/DOGE wallet should be transferred to a newly-created BTC/LTC/DOGE wallet/address and the now-empty qualifying wallet/address used for the CLAM import. I couldn't pick any holes in that but IANAC (C=Cryptographer).

Cheers

Graham

Edit, use a more precise reference

I think it's 145 Mb to download. The rest is indexes which your client will create from the 145 Mb it downloads.


I think you have this wrong.

The CLAM client stores your private keys, which are THE SAME as your Bitcoin private keys.

If someone gains access to your CLAM wallet (and the password, if encrypted), then they also have access to the BTC, LTC, or DOGE at the addresses you imported.

It's possible to convert from BTC addresses to CLAM addresses (and back again) without knowing the private keys. I posted a short Python script which does exactly that not long ago. See this post:

I've never sold any CLAMs - so what I'm making out of CLAMs is a lot of CLAMs. lol.

I'll probably hold them until they're worthless, or worth a fortune - same as I do with BTC.

I don't know how to count the number of stakes per day without counting them myself - there are lots.

Here's a screenshot of the most recent stakes to give you an idea of the frequency of staking:



Then nothing staked until 17:21. So I guess about 20 per hour, or around 500 per day. I have a feeling that the screenshot shows an unusually good hour though, so maybe it's half that. But with the lotto wins as well I'm sure the average is higher.


Here are the sizes of the big things in my .clam/ folder, in Mb:

11   database
69   txleveldb
139   blk0001.dat

so it's pretty tiny - my whole .clam/ folder is 256 Mb in total, and includes 43 backups of my wallet.dat.


Yes. Your BTC privkey *is* your CLAM privkey; they are the same thing. Just export it from your bitcoin wallet and import it into the CLAM wallet.

The blockchain takes up around ~230MB of disk space at the current height of 69600 blocks.
I see what you're getting at with having to import a wallet.dat, and that's essentially what's being done. Your wallet keys are basically converted to clam keys on import, and there's virtually no danger here unless your machine is compromised. The once imported data is not stored anywhere in the CLAM client, but that's not to say you shouldn't use multiple btc/ltc/doge wallets (you should). However, there's no way to tell if you own or owned the coin without full key pairs (unless I'm seriously missing something here).

Oh, the envy
We sure could use some more CLAMS for bounties at the donation address *wink wink*

---

That is essentially what the CLAMClient does -> though 'converting' isn't exactly the right word.

We will have a test build floating around, likely later today, with the new in-client GUI import mechanism.
A big thanks to tryphe for the Qt work.

@dooglus
congrats... I guess you're making alot ฿฿ or perhaps $$ out of CLAMs
If I may know, how many of your outputs getting staked everyday?
---

I just got done sync-ing the other altcoin, so I'm planning to focus on this one now
first, can anyone tell me how big is CLAM blockchain?
second, I know I can check beforehand what-could-be-my clam address balance by going to khashier explorer
but is there another way claiming clams other than using wallet.dat
maybe something like converting my btc priv key to clam priv key (if that even possibe) then importing it to the CLAM qt client