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

After importing my BTC and Doge wallets, nothing is happening - Why?

The only thing I found was Number of New Addresses Created (with the name of 'importwallet'.

I turned on port forwarding for my 1.4.3 client,   still the same results..  inbounds are false in getpeerinfo. 
And still no stakes - but I realize might take awhile yet. 
I'm assuming the same for when I was running 1.4.5 ,  although I could try that again too.
I'll wait to see if there is any fix from devs.

Hi Guys

Is there anyway to reject peers running 1.4.4 as there just sucking large amounts of data.

Jon 

I see, also a big staking pool too.
But I still want to try and see if making one would pop haha

So this could be the problem I'm experiencing?  

I reverted back to 1.4.3 and seems like getpeerinfo peers are all still false but I do notice I have full / more connections!

Maybe staking on 1.4.3 will be better for me?,  I'll wait and see what happens..

Is it now mandatory to have to use UPnP or port forwarding???

I didn't have to do this in previous versions!

Hey,  mine all show false ! 

How do I fix?

Thanks

An issue was reported recently concerning a lack of connections in v1.4.5:
  https://github.com/nochowderforyou/clams/issues/137

Is anyone running v1.4.5 and actually getting incoming connections?

Running "getpeerinfo" in the debug console will show you "inbound" for each peer. Is it "true" for anyone?

Just out of curiosity,  what was the issue in this case?

Edit: never mind.. probably because of version 1.4.4 ?

Nothing at all..  no orphaned blocks either. 
I'll try to send a pm soon!

Have you been seeing orphan blocks, or just nothing at all?

If you PM me your IP address, I'll check my logs and see if I notice anything weird relating to your peer. I expect you will have connected to at least one of my peers recently.

Well for the set amount I have (actually above 360)  I haven't seen anything for days.
Time is sync'd,  block number same as block number at http://khashier.com/
Plus, the amounts that I have set up total above 360 and are split up in different addresses, so I'm not waiting for any maturing.

I don't know.. wallet is unlocked, icon says its staking.
Just seems strange.  

I estimate that each 360 CLAMs in your wallet should stake about once per day on average at the moment. This is based on a single datapoint (JD has 360k CLAMs and stakes 1k times per day). More datapoints from other large stakers would be appreciated.

There's another ~100k CLAMs staking outside of JD (since 400 blocks per day are being staked outside of JD) so I guess there are other big stakers out there.

Just-Dice.com acts as an online CLAM wallet service, so long as you can trust yourself not to gamble.

(much)


I think the point was that 10M of the 15M undug CLAMs could be in addresses you control. You just didn't dig them up yet because you "knew" CLAM was eventually going to catch on.

Anyway, my poor laptop spent the night compiling historical day-by-day stats of the total and active supply stats so coinmarketcap.com can fill in the history on their CLAM market cap chart. As a result I was able to generate this chart showing block count and active supply over time:



The raw data is here: http://privatepaste.com/18a59b4f72

The post to the coinmarketcap thread is here: https://bitcointalksearch.org/topic/m.10379165

Is something wrong with the staking?  Because I haven't been getting any clams either..  I used to get around 1 per day, and have a somewhat good amount set for staking.  Haven't been getting anything for the last week.. which seems very unusual.  My time is sync'd, and block numbers seem fine too!

Or, is it just because tons more people are staking??

Clam really needs a stake pool.
Maybe Clam should switch from bitcoin protocol to NXT protocol.

As a few people on JD already know, Iam trying to get something like this running and if everything goes right I might release it ovet the next week

As other senior forum users have pointed out, but repeated for emphasis:

Do not simultaneously use and alter a wallet.dat file on different machines or instances of the client.
Bad things can and WILL happen.

---

A concern that is reasonable, and has been voiced and responded to previously and repeatedly in this thread.
Mostly towards the beginning of this thread, if someone wishes to review them.
All of which still exist.  We don't censor our thread

It is worth noting that the vast majority of the distribution went to holders of BTC. .
More than 95% if I remember correctly (a simple fact of the scale of the networks), though I am not positive on the numbers.

Obviously, BTC would be the most cost prohibitive network to execute such an "attack" on, due to the value of the coin itself (which was at much higher fiat prices at the time) and the transaction fees themselves.

In addition to dooglus' comments, I would also mention that there are only 500k CLAM currently in circulation.  
Even if you can't trust the motives of us CLAM developers, consider this:

Only 290k of those CLAMS were "dug" (the rest are staked coins).
Even if every single claimed CLAM, i.e. every single claimed BTC, LTC, DOGE output, was evil;
That would still only be something like ~2% of the total distribution.  

In fairness, there is no way of knowing ultimately how many will be claimed and the current total supply is much less than that.
Just making the point that even if you assume the ABSOLUTE worst, think the Devs claimed every CLAM ever claimed, trust absolutely no one, and think we are the most patient scammers in the history of the internet.......... well, even then the argument isn't all that impressive, large, or frightening.

---

On a side note, I access the internet on a potato laptop with uncertain internet access.
We must be doing it wrong.

Not everyone sells their soul for money; idealism is still alive and strong.

It'd be a great and fun try