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

[SuperClam]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

That`s sounds great, i only have 12 GB left on my Laptop. Hope synchronization will not take 12 hours.
Thanks buddy

I would suggest shutting down the client, downloading the most recent bootstrap file and placing it in your data directory (next to the wallet.dat file), and then restarting the client.
If you don't interrupt it, it should get a large portion of the way to sync'd.

[crazyivan]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

Ok. So, what s the easiest way to split my 50 CLAM block into 10 blocks of 5 CLAM each? Please dont tell me I have to do it manually.
Thx a lot.

[kolloh]

Ok. So, what s the easiest way to split my 50 CLAM block into 10 blocks of 5 CLAM each? Please dont tell me I have to do it manually.
Thx a lot.

Using the clam client and the sendtoaddress, you can specify amounts if you are using at least version v1.4.11 . You may need to use clamd instead of the GUI client to do this though.

The sendtoaddress and sendfrom RPC calls can now specify the amount as {"amount":aaa,"count":ccc} to cause the send amount to be split into ccc outputs each of size aaa CLAMs. This allows users to more easily split their coins into multiple outputs without needing to resort to the raw transactions calls.

[dooglus]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

It depends how many CLAMs you have, and what kind of a percentage loss you're willing to take while your CLAMs mature after staking. I generally aim to have 1% of my outputs maturing at any point in time, so I only lose 1% of potential earnings. Since it takes 8 hours for an output to mature that means I need to size my outputs such that their expected time-to-stake is 800 hours. 800 hours is 800 * 60 = 48k minutes, and the network aims to stake once per minute. The network weight is currently around 700k, so I need each output to be 700k/48k = 14.58 CLAMs in order to only lose 1% of potential profit.

Smaller than 14 CLAMs per output will result in a smaller percentage loss, bigger than 15 CLAMs will result in a bigger percentage loss, but 14.5 seems like a good size for now.

CLAMs take 510 blocks to mature, but also outputs can't stake until 4 hours after the last time they were involved in a transaction.

The expected time to stake is roughly (network weight) / (output value) minutes.

For an output of 14.5 CLAMs, that's 700k/14.5 = 48275 minutes = 804.59 hours.

Note the network weight shown by the client is only an estimate. It's impossible to know how many CLAMs are actually trying to stake right now - we can only guess based on how many are actually staking and the current difficulty.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

The wallet itself is pretty small unless you do a lot of transactions, or import a lot of private keys.

The things that do take up space are:

1) blk0001.dat (the raw blocks). It's currently 650 MB.
2) txleveldb (the block database). It's currently 370 MB.
3) debug.log (the logfile). It grows over time. Mine is 1.4 GB. But you can delete it whenever you like.

So the blockchain uses up just over 1 GB right now.

[Zeta0S]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

That`s sounds great, i only have 12 GB left on my Laptop. Hope synchronization will not take 12 hours.
Thanks buddy

I would suggest shutting down the client, downloading the most recent bootstrap file and placing it in your data directory (next to the wallet.dat file), and then restarting the client.
If you don't interrupt it, it should get a large portion of the way to sync'd.

Hmm, what am i doing wrong here..

[SuperClam]

Ok. So, what s the easiest way to split my 50 CLAM block into 10 blocks of 5 CLAM each? Please dont tell me I have to do it manually.
Thx a lot.

Using the clam client and the sendtoaddress, you can specify amounts if you are using at least version v1.4.11 . You may need to use clamd instead of the GUI client to do this though.
The sendtoaddress and sendfrom RPC calls can now specify the amount as {"amount":aaa,"count":ccc} to cause the send amount to be split into ccc outputs each of size aaa CLAMs. This allows users to more easily split their coins into multiple outputs without needing to resort to the raw transactions calls.

The client will also automatically split in half outputs which stake in less than a 24 hour period.

Additionally, the client allows fine tuned runtime splitting via the flags: -maxstakevalue, -splitsize and -combinelimit.

Our staking system is, at this point, almost certainly the most powerful and customizable system currently in existence.

You can review notes on some of these additional features via change logs here: https://github.com/nochowderforyou/clams/releases

[SuperClam]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

That`s sounds great, i only have 12 GB left on my Laptop. Hope synchronization will not take 12 hours.
Thanks buddy

I would suggest shutting down the client, downloading the most recent bootstrap file and placing it in your data directory (next to the wallet.dat file), and then restarting the client.
If you don't interrupt it, it should get a large portion of the way to sync'd.

Hmm, what am i doing wrong here..

I expect nothing is wrong - it appears to be importing blocks. 
Unfortunately, the beginning of the import (due to the initial distribution block size) as well as up to a certain point (due to utilizing scrypt as opposed to sha256) can take some time to verify and import.

[Zeta0S]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

That`s sounds great, i only have 12 GB left on my Laptop. Hope synchronization will not take 12 hours.
Thanks buddy

I would suggest shutting down the client, downloading the most recent bootstrap file and placing it in your data directory (next to the wallet.dat file), and then restarting the client.
If you don't interrupt it, it should get a large portion of the way to sync'd.

Hmm, what am i doing wrong here..

I expect nothing is wrong - it appears to be importing blocks.  
Unfortunately, the beginning of the import (due to the initial distribution block size) as well as up to a certain point (due to utilizing scrypt as opposed to sha256) can take some time to verify and import.

I downloaded the bootstrap.dat and placed if in the same map as the clam wallet.dat.
I do not see any deliverance in getting the blocks more quickly that i did before downloading the bootstrap.dat
Its it whise to delete this bootstrap, i do not thing its doing anything...or will it help later when more blocks are synchronized? 

[SuperClam]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

That`s sounds great, i only have 12 GB left on my Laptop. Hope synchronization will not take 12 hours.
Thanks buddy

I would suggest shutting down the client, downloading the most recent bootstrap file and placing it in your data directory (next to the wallet.dat file), and then restarting the client.
If you don't interrupt it, it should get a large portion of the way to sync'd.

Hmm, what am i doing wrong here..

I expect nothing is wrong - it appears to be importing blocks.  
Unfortunately, the beginning of the import (due to the initial distribution block size) as well as up to a certain point (due to utilizing scrypt as opposed to sha256) can take some time to verify and import.

I downloaded the bootstrap.dat and placed if in the same map as the clam wallet.dat.
I do not see any deliverance in getting the blocks more quickly that i did before downloading the bootstrap.dat
Its it whise to delete this bootstrap, i do not thing its doing anything...or will it help later when more blocks are synchronized? 

You can look at your debug.log file to verify that the bootstrap file is being imported.

It appears to be importing.

If you interrupt it during the import - you will have to start all over.

[dooglus]

I downloaded the bootstrap.dat and placed if in the same map as the clam wallet.dat.
I do not see any deliverance in getting the blocks more quickly that i did before downloading the bootstrap.dat
Its it whise to delete this bootstrap, i do not thing its doing anything...or will it help later when more blocks are synchronized? 

It takes a while to skip through the bootstrap file to get to blocks you haven't seen before. Leave it running and it won't take too long to finish.

You can get the latest bootstrap.dat file and/or pieces of it using links in this post, which I keep updated:

    https://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191

[oldkolobok]

Someone pls address my question, can I keep all of my CLAM in one block? Should I break it to smaller blocks?
Also, where do you see how long it takes for CLAM to stake? In other words, how long until CLAM reaches maturity?

Common understanding at the moment is that a user might be more efficient to split their outputs up.
The reasoning is that when a block is staked, only a single output goes immature - with the remaining outputs continuing to attempt to stake.

Hi, just downloaded the wallet and waiting for synchronization, but how big is the wallet gonna be? It`s on my laptop and i have a limited hard-disk space on it.
Thanks!

I don't have an exact number handy but, I expect the chain is still less than 2 gigs in size.

That`s sounds great, i only have 12 GB left on my Laptop. Hope synchronization will not take 12 hours.
Thanks buddy

I would suggest shutting down the client, downloading the most recent bootstrap file and placing it in your data directory (next to the wallet.dat file), and then restarting the client.
If you don't interrupt it, it should get a large portion of the way to sync'd.

Hmm, what am i doing wrong here..

Ive had this problem with the CLAM bootstrap aswell... the client is not recognizing the bootstrap. If it was, the client would take a long time to load, with a message like verifying blocks or something like that. From the screenshot I can tell its just syncing with the network like no bootstrap has been used.

If you just want to claim your clams, checkout the just-dice digging function. Worked faster for me!

[dooglus]

Ive had this problem with the CLAM bootstrap aswell... the client is not recognizing the bootstrap. If it was, the client would take a long time to load, with a message like verifying blocks or something like that. From the screenshot I can tell its just syncing with the network like no bootstrap has been used.

See how it says "importing blocks" in the lower left? That means it's loading blocks from the bootstrap.dat file.

You're wrong about it syncing from the network. To prove it to yourself try switching off your cable router or otherwise going offline and see how it continues making progress.

If you just want to claim your clams, checkout the just-dice digging function. Worked faster for me!

Yeah, whoever made that site is a fricken genius.

There's also clamchecker.com. They have fee of 24%; for every 4.6 CLAM you claim you get 3.5 CLAM, they get 1.0 CLAM and the affiliate gets 0.1 CLAM. On Just-Dice for every 4.6 CLAM you claim you get 4.6 CLAM. The site takes off 0.001 CLAM for the transaction fee and you get the rest.

[Trent Russell]

If you just want to claim your clams, checkout the just-dice digging function. Worked faster for me!

Yeah, whoever made that site is a fricken genius.

Ha! I thought posters were supposed to use sock puppet accounts for replies like this. Hmm. I've just noticed your avatar. Maybe you are your own sock puppet.

[BayAreaCoins]

If you just want to claim your clams, checkout the just-dice digging function. Worked faster for me!

Yeah, whoever made that site is a fricken genius.

Ha! I thought posters were supposed to use sock puppet accounts for replies like this. Hmm. I've just noticed your avatar. Maybe you are your own sock puppet.

I thought it was common knowledge by now that doogs a satoshi sock . jk

ClamChecker still isn't complete yet.  Still a few edits to go.

[BayAreaCoins]

There's also clamchecker.com. They have fee of 24%; for every 4.6 CLAM you claim you get 3.5 CLAM, they get 1.0 CLAM and the affiliate gets 0.1 CLAM. On Just-Dice for every 4.6 CLAM you claim you get 4.6 CLAM. The site takes off 0.001 CLAM for the transaction fee and you get the rest.

17% (ish) if you refer yourself for BTC.

That is hedging your bets against the CLAM market and still earning Bitcoins from a empty address.

(3.5 CLAMS + .002 BTC)

[BurstIncomeAsset]

This cryptocurrency is an interesting one, it is already widely used in gambling as I observed, while also in investing.

In fact most gambling sites offer CLAM based investing in their bankroll. So it is somewhat a gambling oriented coin.

[krile]

Are there any services online to check the status of the clam network?

Like the number of active nodes, their geographic location and other info...

Something like https://bitinfocharts.com/

[dooglus]

Are there any services online to check the status of the clam network?

Like the number of active nodes, their geographic location and other info...

Something like https://bitinfocharts.com/

http://blocktree.io/peers/CLAM/ ?

[krile]

Are there any services online to check the status of the clam network?

Like the number of active nodes, their geographic location and other info...

Something like https://bitinfocharts.com/

http://blocktree.io/peers/CLAM/ ?

Thanks for the info!

But from what I see here, this site currently lists 49 active peers. My own clam client has 59 active connections atm. So this site is not measuring the number of all the nodes, just the ones it is currently connected to. (am I right?)

Am I missing something about the basics of the clams network, is it not possible to capture the number of all the active nodes? So in the same way that bitinfocharts displays the nodes of various coins, for example: https://bitinfocharts.com/blackcoin/nodes-active/

P.S. Sorry if this is a silly question

[SuperClam]

Are there any services online to check the status of the clam network?
Like the number of active nodes, their geographic location and other info...
Something like https://bitinfocharts.com/

http://blocktree.io/peers/CLAM/ ?

Thanks for the info!
But from what I see here, this site currently lists 49 active peers. My own clam client has 59 active connections atm. So this site is not measuring the number of all the nodes, just the ones it is currently connected to. (am I right?)
Am I missing something about the basics of the clams network, is it not possible to capture the number of all the active nodes? So in the same way that bitinfocharts displays the nodes of various coins, for example: https://bitinfocharts.com/blackcoin/nodes-active/
P.S. Sorry if this is a silly question

It is not an exact science, but there is no reason that one couldn't attempt to, and be reasonably successful at, listing a mostly comprehensive list of active nodes.