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

[Chuck_Bartowski]

Hey folks. Just a little update on the status of ClamBaker.Club.

We are currently back online and deposits have been re-enabled!

Come check out ClamBaker.Club for the worlds first loss-less investment based game!

Just another HYIP..wondering how long this will last..lol

[1714725903]

1714725903

[1714725903]

1714725903

[1714725903]

1714725903

[TRilon]

Just another HYIP..wondering how long this will last..lol

Too low trading volumes, you need a lot more

[dooglus]

Just another HYIP..wondering how long this will last..lol

Too low trading volumes, you need a lot more

I'd have thought the opposite. The higher the throughput of a HYIP, the more "interest" you need to find from somewhere, and so the less able you are to meet your obligations in a timely manner.

It's all very well to say that any shortfall will be made up from staking, but that fails to take into account just how long it takes to earn a 25% return on the total throughput when only part of a single deposit (and possibly the operator's 2% fee on all throughput) is staking at any given time.

[smooth]

Just another HYIP..wondering how long this will last..lol

Too low trading volumes, you need a lot more

I'd have thought the opposite. The higher the throughput of a HYIP, the more "interest" you need to find from somewhere, and so the less able you are to meet your obligations in a timely manner.

It's all very well to say that any shortfall will be made up from staking, but that fails to take into account just how long it takes to earn a 25% return on the total throughput when only part of a single deposit (and possibly the operator's 2% fee on all throughput) is staking at any given time.

Currently the stake rate is over 4% per month so staking 25% wouldn't really take that long. Were it not for the risk of exit fraud this doesn't seem like a bad idea. You get the ponzi/gambling appeal of possibly getting paid back sooner and an expected payment in several months. If claims continue at a high rate than the 4% will drop rapidly, so it could take longer, but even so 25% should be achievable from staking, probably.

But the risk of exit fraud with an unknown operator on a newly registered newbie account is nearly 100%.

EDIT: Correction, this won't work because as dooglus correctly pointed out most of the investment will already be paid out to earlier investors (thus not available to stake). Just a pozni. Avoid.

[dooglus]

But the risk of exit fraud with an unknown operator on a newly registered newbie account is nearly 100%.

EDIT: Correction, this won't work because as dooglus correctly pointed out most of the investment will already be paid out to earlier investors (thus not available to stake). Just a pozni. Avoid.

There are additional risks from issues like this, where the payout is sometimes sent to the wrong address.

[TooDumbForBitcoin]

CLAM is a pozni.

[PolarPoint]

If my client is connected to 20 other nodes (shown when I click on the network icon) and the ticket icon say I am staking, my settings must be correct, right? Do I need to forward a port from my home router to my computer? If so, which port should I forward? Is there a default port? I scanned through this thread and I see different ports specified. Thanks in advance.

[chriswen]

If my client is connected to 20 other nodes (shown when I click on the network icon) and the ticket icon say I am staking, my settings must be correct, right? Do I need to forward a port from my home router to my computer? If so, which port should I forward? Is there a default port? I scanned through this thread and I see different ports specified. Thanks in advance.

20 other nodes probably means you can accept incoming connections.

[bigsky101]

I downloaded Clam Client 1.4.17 for OSX.  I've noticed that at random blocks it stalls for very long periods of time.  I'm currently at block 338xxx (13 Feb 2015).  I've noticed that restarting the client speeds up the process quit a bit.  I'm wondering if adding nodes (is there a list of nodes available) would be helpful and if using the console or if adding a .config file in Application Support would be appropriate. 

I've been downloading the chain for about 18 hours and am on block 338xxx with 36 weeks left.  Does this seems about right?

I have between 8 - 14 connections at any given time and have a reliable connection 20 Mbps +

[bigsky101]

I downloaded Clam Client 1.4.17 for OSX.  I've noticed that at random blocks it stalls for very long periods of time.  I'm currently at block 338xxx (13 Feb 2015).  I've noticed that restarting the client speeds up the process quit a bit.  I'm wondering if adding nodes (is there a list of nodes available) would be helpful and if using the console or if adding a .config file in Application Support would be appropriate. 

I've been downloading the chain for about 18 hours and am on block 338xxx with 36 weeks left.  Does this seems about right?

I have between 8 - 14 connections at any given time and have a reliable connection 20 Mbps +

Nevermind, I have answered my own question.  I have found the bootstrap for the chain in a previous post. It seems to be working fine.  If anybody is curious:

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

[dooglus]

If my client is connected to 20 other nodes (shown when I click on the network icon) and the ticket icon say I am staking, my settings must be correct, right? Do I need to forward a port from my home router to my computer? If so, which port should I forward? Is there a default port? I scanned through this thread and I see different ports specified. Thanks in advance.

20 other nodes probably means you can accept incoming connections.

To be absolutely sure, go to the debug console and type 'getpeerinfo'.

It will show you a bunch of information about each peer you are connected to, including its "inbound" status. If any of them show "inbound: true" then you are accepting incoming connections, and everything is OK.

[dooglus]

Updated dig charts:

[ShapeShift.io]

ShapeShift.io has released our instant exchange app for Android devices! Buy or sell CLAMs with bitcoin and 45+ cryptos instantly on any Android device. Exchange anytime, anywhere: https://shapeshift.io/site/tools/shapeshift-mobile

[PolarPoint]

If my client is connected to 20 other nodes (shown when I click on the network icon) and the ticket icon say I am staking, my settings must be correct, right? Do I need to forward a port from my home router to my computer? If so, which port should I forward? Is there a default port? I scanned through this thread and I see different ports specified. Thanks in advance.

20 other nodes probably means you can accept incoming connections.

To be absolutely sure, go to the debug console and type 'getpeerinfo'.

It will show you a bunch of information about each peer you are connected to, including its "inbound" status. If any of them show "inbound: true" then you are accepting incoming connections, and everything is OK.

Thanks Dooglus,

I did that just now. About 10 out of about 20 peers had "inbound=true", the rest are false. I think I am OK. I don't understand why the clam client assigns a unique port to each peer and increment the port number indefinitely above 49200. Can I set a parameter in clam.conf to tell peers I want to use the default 37114?

[Bitcoiner2015]

I'm sure it's been mentioned before, but could the digger be Mt. Gox, or representatives of them involved in the liquidation settlements?
They must have a lot of addresses that weren't dust at the time of CLAMs creation.

Otherwise who has so many none dust accounts?  I am holding, there have been big diggers before, and it will happen again, but that is part of CLAMs.

[dooglus]

I don't understand why the clam client assigns a unique port to each peer and increment the port number indefinitely above 49200. Can I set a parameter in clam.conf to tell peers I want to use the default 37114?

No, that's just how TCP/IP works. When you connect to port 31174 on remote hosts, it uses a port on your end which probably won't be 31174, and will be different for each connection you make. The operating system assigns the local port number. You can probably tinker with configuration of the OS to tell it which range to use, but there's not really any need to do so.

[dooglus]

I'm sure it's been mentioned before, but could the digger be Mt. Gox, or representatives of them involved in the liquidation settlements?
They must have a lot of addresses that weren't dust at the time of CLAMs creation.

Otherwise who has so many none dust accounts?  I am holding, there have been big diggers before, and it will happen again, but that is part of CLAMs.

Sites like walletexplorer.com and scorechain.com can 'cluster' addresses based on their blockchain history. Doing so suggests this digging isn't using Gox addresses.

[Kiritsugu]

Forgive the noob-y question, but it's not anywhere easily visible in the OP or on the main CLAM website; What are the PoS statistics for CLAM?  What is the PoS % for each stake and each month (generally), and what is the minimum coin age to stake?

[Kiritsugu]

Forgive the noob-y question, but it's not anywhere easily visible in the OP or on the main CLAM website; What are the PoS statistics for CLAM?  What is the PoS % for each stake and each month (generally), and what is the minimum coin age to stake?

Finally found it, nvm.  Thanks

[SuperClam]

Forgive the noob-y question, but it's not anywhere easily visible in the OP or on the main CLAM website; What are the PoS statistics for CLAM?  What is the PoS % for each stake and each month (generally), and what is the minimum coin age to stake?

Finally found it, nvm.  Thanks

Glad you found it  
For future travelers:
Reward is 1 CLAM per block staked, with 1440 blocks staked per day, or 1 block per minute.
This means "percentage" return is based on difficulty, much like Proof-Of-Work mining. 
Age is not a factor in chance to stake, only the coin pile(output) size.

As a side note, since it isn't percentage based, and can't be "saved" up it allows users to "beat" inflation; which, in many normal Proof-Of-Stake networks, is not possible.