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

It's clear that dev received jackpot when Doog decide to go with CLAM. But what else can we expect from dev. That plans from beginning (http://clamclient.com/#/development-plan/) are still have very slow progress or not progress at all (CLAMprivacy, CLAManon). Beside that; these is only coin that give better reword to those who come later, again thanks to Doog.  Can we expect some change ( reducing rewords) or that 4.6 CLAM per address will stay forever?

The rewards have already been distributed.  I don't think its possible to change that.

It's clear that dev received jackpot when Doog decide to go with CLAM. But what else can we expect from dev. That plans from beginning (http://clamclient.com/#/development-plan/) are still have very slow progress or not progress at all (CLAMprivacy, CLAManon). Beside that; these is only coin that give better reword to those who come later, again thanks to Doog.  Can we expect some change ( reducing rewords) or that 4.6 CLAM per address will stay forever?

It's clear that dev received jackpot when Doog decide to go with CLAM. But what else can we expect from dev. That plans from beginning (http://clamclient.com/#/development-plan/) are still have very slow progress or not progress at all (CLAMprivacy, CLAManon). Beside that; these is only coin that give better reword to those who come later, again thanks to Doog.  Can we expect some change ( reducing rewords) or that 4.6 CLAM per address will stay forever?

Changed the OP post links over to the new block explorer @ CLAMsight.com.

The client is fully synced now, and I can see it's trying to stake, too. With a relatively fresh deposit of only 108 CLAM it may take a while.

For a more consistent and faster syncing experience, try using the bootstrap.dat file I updated yesterday.
[...]
Starting with just that file, and running with -connect=127.0.0.1 should prevent your node from connecting to any peers while it loads the blockchain from the bootstrap file, so if it crashes once it should crash the same way every time.

FWIW, I compiled clam for the Odroid C1 a few hours ago, and it's currently syncing. It did die with a segmentation fault ( ) after syncing a few thousand blocks, but has not skipped a beat since I restarted it. I'm doing a sync from scratch to give it a good workout.

The seemingly random segfault bothers me a little. Once fully synced I'll move the db elsewhere temporarily then try another sync from scratch, to see if it dies at the same place. Hopefully it does. [edit: running from a virgin data dir didn't segfault.]

A Raspberry Pi 2 or Odroid C1 costs only $USD 35; either should be able to run clamd. I'm not sure whether the weaker CPUs will make staking more erratic, or it doesn't really matter. (If it does matter - the C1 CPU clocks 60% faster than the Pi2)

I have an Odroid C1 right next to me, might try compiling and running clamd for a bit, just out of curiosity.

[...]

The router needs a copy of the blockchain in order to be able to stake. That's currently a little under 1 Gb. I don't know what kind of storage your router has available, but that may be a problem.

To clarify, a computing device with the wallet will need to run non-stop with a good internet connection in order to mint a block? Meaning basically every time I resume the OS or come back from a bad internet connection(and I switch IPs), I start from ground zero in terms of staking?

I don't see how it could not run on my router, if I can get the dependencies all the right versions.

To clarify, a computing device with the wallet will need to run non-stop with a good internet connection in order to mint a block? Meaning basically every time I resume the OS or come back from a bad internet connection(and I switch IPs), I start from ground zero in terms of staking?

I don't see how it could not run on my router, if I can get the dependencies all the right versions.

You will miss out on staking if the computer is hibernating. You could also run it on something small like raspberry pi I'm sure. Dunno if you could get it to run on the router or not.

Alternatively, you could stake them online such as by investing in JD.

A good catch.
The OP post title has been updated to reflect the lack of "Proof-Of-Pearl".
Not sure how that wasn't noticed sooner - like, 9 months ago sooner  

In response to your questions:

Proof-Of-Chain, as xploited correctly mentioned, refers to the method of the initial distribution of the CLAM money supply.
Every single BTC, LTC and DOGE address that held a balance above dust around May, 14th (2014) received an equal share of the initial money supply.  Essentially, the entire initial money supply was given away to BTC, LTC and DOGE holders.

Proof-Of-Working-Stake refers to the CLAM's unique implementation of Proof-Of-Stake.  Proof-Of-Stake conventionally provides reward to staking users in proportion to the age of the coins they stake with.  This results in what essentially operates like "interest".  It also, however, removes the incentive for users to stake consistently and secure the network.  There is no incentive to stake now, as opposed to later, if the reward for doing so will simply accrue until that user chooses to stake and claim it.  In CLAM, the reward for staking is a static 1 CLAM per staked block.  This reward, much like proof-of-work, likely aligns incentives to stake with the benefit to the network of persistent competition for blocks.  In addition, as dooglus mentioned, the CLAM network does not provide a benefit to users based on the age of a given pile of coins (output).  This suggests that a CLAM on the network is more akin to a Proof-Of-Work miner.  A CLAM represents something somewhat similar to a unit of hashing power in a Proof-Of-Work network.  If you do not stake (turn on your miner), you do not have the opportunity to be rewarded for securing the network.

---

I hope that was helpful