Author

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

legendary
Activity: 2968
Merit: 1198
Also the diff s been going up big time which s gonna limit the supply of CLAM from staking.

The supply is mostly constant (1 CLAM per minute +/- randomness and tracking fluctuations). The difficulty going up means it is harder to get a share of it, but the amount stays mostly the same.
legendary
Activity: 1652
Merit: 1007
DMD Diamond Making Money 4+ years! Join us!
Also the diff s been going up big time which s gonna limit the supply of CLAM from staking.

I dont know why I have this feeling but I think we re gonna have another pump and after that dump.

Still, things looks much better then 10 days ago.
legendary
Activity: 2968
Merit: 1198
Have a nice day bigfoots. I expect someone to raise this to 0.003, it would be very funny. Wink Anyway, it's not gonna happen, want facts? Here you have one: 0.0025 WAS THE TOP, IT WILL NEVER TOUCH NOR SURPASS IT AGAIN.

Your move, Mr. Vulture:



Is it funny yet?

CLAM is really taking off it seems. With this pace it will soon be back at the 500k+ range Smiley
But as you say'd "Your move, Mr. Vulture". Will be interesting to see what happens but my money is on nothing.

It's pretty clear "their move" is to get margin called on their short. Or they throw in the towel and try to unwind in a more orderly manner. It hasn't happened quite yet but it can't be long.

(Sorry of OT...people seems interested in discussing.)
legendary
Activity: 1624
Merit: 1007
Have a nice day bigfoots. I expect someone to raise this to 0.003, it would be very funny. Wink Anyway, it's not gonna happen, want facts? Here you have one: 0.0025 WAS THE TOP, IT WILL NEVER TOUCH NOR SURPASS IT AGAIN.

Your move, Mr. Vulture:



Is it funny yet?

CLAM is really taking off it seems. With this pace it will soon be back at the 500k+ range Smiley
But as you say'd "Your move, Mr. Vulture". Will be interesting to see what happens but my money is on nothing.
legendary
Activity: 2968
Merit: 1198
Not that I don't greatly enjoy your mocking of VultureFund, dooglas, but if his trading comments are off topic, aren't your comments about his trading comments off topic too?
legendary
Activity: 2940
Merit: 1333
Have a nice day bigfoots. I expect someone to raise this to 0.003, it would be very funny. Wink Anyway, it's not gonna happen, want facts? Here you have one: 0.0025 WAS THE TOP, IT WILL NEVER TOUCH NOR SURPASS IT AGAIN.

Your move, Mr. Vulture:



Is it funny yet?
full member
Activity: 147
Merit: 100
Thank you so much for that post.  I will use that to double check.  I seem to have done *Something* wrong because I just started redownloading the blockchain and the transactions came in.

Thanks for your help!
legendary
Activity: 2940
Merit: 1333
Is it possible that http://clam.makejar.com/ was wrong and I didn't have clams to claim? Rescan didnt work.

Try using Just-Dice's "chat" tab. Type /dig and the BTC/LTC/DOGE address. It will tell you whether the address received any CLAMs and whether they have already been claimed.

For example, I type:

  /dig 1P2MktBR3dYoM71jJapSfLBqimAHMADY4K

and it tells me:

  15:10:20 INFO: BTC address [1P2MktBR] was not funded on 12th May 2014; [xWKzem1t] is the corresponding CLAM address; see [history:1P2MktBR] for a history of its balance

where the [...] texts are links. Or I type:

  /dig 14o7zMMUJkG6De24r3JkJ6USgChq7iWF86

and it tells me:

  15:11:50 INFO: CLAM address [xC6ktEBw] corresponding to BTC address [14o7zMMU] was funded with 4.60545574 CLAM when the initial distribution was made; the CLAMs were already dug up, sorry

or, for an address I know is still funded but don't own:

  /dig 1CrPRwBkwZdEejXusCbh8o35YMN7g7ffKf

and it says:

  15:12:49 INFO: CLAM address [xLA2Kp2E] corresponding to BTC address [1CrPRwBk] was funded with 4.60545574 CLAM when the initial distribution was made; the CLAMs have not been spent and are waiting for you to collect them; [further instructions]
full member
Activity: 147
Merit: 100
Is it possible that http://clam.makejar.com/ was wrong and I didn't have clams to claim? Rescan didnt work.

**EDIT**

I just moved the blockchain and started a new download.  That worked.

CLAMS FOR ME!
legendary
Activity: 2940
Merit: 1333
How long before my free clams from a wallet import are visible in my wallet?

Am I supposed to import before the client syncs to 100%? Am I supposed to resync?  Did I do this backwards?

It doesn't matter whether you sync or import first.

You need to be synced up to at least block 10,000 to see your free CLAMs.

And if you import the old privkeys *after* you sync the chain, you need to -rescan before you will see the coins - but I think the import command does that for you.
full member
Activity: 147
Merit: 100
How long before my free clams from a wallet import are visible in my wallet?

Am I supposed to import before the client syncs to 100%? Am I supposed to resync?  Did I do this backwards?
legendary
Activity: 2940
Merit: 1333
Have a nice day bigfoots. I expect someone to raise this to 0.003, it would be very funny. Wink Anyway, it's not gonna happen, want facts? Here you have one: 0.0025 WAS THE TOP, IT WILL NEVER TOUCH NOR SURPASS IT AGAIN.

I'll just leave this here:



full member
Activity: 238
Merit: 100
Can anybody imagine to help Jared (dev of digibyte) to get his coin on the right track?

This community has proven to be outstanding. Clams will reach 1 billion market cap no doubt.
full member
Activity: 194
Merit: 100
Damn CLAM is doing well this week - just one steady uptrend looking like its about to launch!
full member
Activity: 193
Merit: 100
Alright, here we come 1$ ! Cool
legendary
Activity: 2968
Merit: 1198
However, voting on development priorities is useful, as a means for the developers to get some idea what coin owners (somewhat an indicator of coin users) think is important. No one really wants to work on things that aren't wanted.

I see your point, but I mostly add the features that I want the most. If that happens to correspond with what lots of other people also want then that's nice.

I guess probably more people use the Qt client than the command line but I don't like working on it and so avoid it as much as possible. If lots of people want a better Qt client then I expect one of them will make it happen. If not, I guess it isn't really that important, and if they do that's cool with me - it doesn't affect the client I use, or the network as a whole.

You're right. A lot of open source gets done (especially when being done by volunteers) because the developer doing it wants the feature. Nothing wrong with that.
legendary
Activity: 2940
Merit: 1333
However, voting on development priorities is useful, as a means for the developers to get some idea what coin owners (somewhat an indicator of coin users) think is important. No one really wants to work on things that aren't wanted.

I see your point, but I mostly add the features that I want the most. If that happens to correspond with what lots of other people also want then that's nice.

I guess probably more people use the Qt client than the command line but I don't like working on it and so avoid it as much as possible. If lots of people want a better Qt client then I expect one of them will make it happen. If not, I guess it isn't really that important, and if they do that's cool with me - it doesn't affect the client I use, or the network as a whole.
legendary
Activity: 2968
Merit: 1198
It strikes me that this isn't a consensus issue, and so you are free to add it to the client any time you like. We don't need to 'vote' on this.

There's lot of things that aren't consensus issues, but would be great to have votes on anyway. e.g. Take my earlier idea that in a block-race stakers would randomly select a block (rather than use the first-seen) to minimize the orphan-risk for honest miners who produce big-blocks.  I don't think that's a consensus issue, but seems like it'd be crazy to adopt something without knowing what everyone thought?

(Or another good example is mempool policy in bitcoin (Current vs FSS-BRB, Opt-in RBF, Full RBF) which seems wildly controversial, but with the shilling and censorship around it, it seems impossible to get a feel for support of each)

Consensus issues don't need to be voted on either, nor is it particularly useful to do so. If there is consensus, it will be obvious. If there is a real need for a vote, there is very likely no consensus.

However, voting on development priorities is useful, as a means for the developers to get some idea what coin owners (somewhat an indicator of coin users) think is important. No one really wants to work on things that aren't wanted.


legendary
Activity: 2968
Merit: 1198
Petition Id: 066b223d
Link: http://txti.es/066b223d



CLAMour Instructions: https://bitcointalksearch.org/topic/m.13098673



Transaction Fee Pooling to Improve Security

I do not support due to high potential for various perverse incentives and unintended consequences.

The most natural and robust interpretation of fees is an incentive for block-creators to include truncations in a block (payment for scarce block size). There are better mechanisms to in turn control block size and limit spam, such as a reward penalty. These will naturally pull fees higher via a market mechanism. Trying to go the other direction is akin to pushing on a rope. Reward penalties are especially suitable for CLAM since the block reward is fixed, unlike Bitcoin.

@dooglas you can (and will) still have a fee market if any portion of the fee, even 1%, is kept by the block creator. It will dramatically drive up the price of block space though, probably to levels above the social optimum. Though you still face the issue of hidden fees being paid out of band, and the incentive to do so will be large.

Again, none of this is likely what is intended. Tx fees are a round peg trying to be shoved into a square hole here.
legendary
Activity: 2968
Merit: 1198
Petition Id: 02fde4a4
Link: http://txti.es/02fde4a4



CLAMour Instructions: https://bitcointalksearch.org/topic/m.13098673



Chain Analytics

Why is it advantageous to have most of this done by the node itself rather than independent chain explorer and analytics type tools, similar to what you get on blockchain.info?

IMO, if it can be done outside the node, it should be done outside the node. The node itself being critical to the functioning of the network. What if a bug is introduced that introduces a crash of every node on the network when some statistics counter overflows? I'm not saying this is likely, but the risk is entirely unnecessary.

Obviously per-node mempool data needs to be collected by each node, but I don't really see the network as even remotely large enough for that to matter. Bitcoin only reached that point recently.
Jump to: