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

@Baljourn @jd1959 @binmon

I had similar problems with version 1.4.4 on linux (32 bit) over the weekend and posted on this thread.

User shawn2025 reported problems last week and posted on this thread.

In my case I first restarted version 1.4.4 (newly downloading the blockchain) but it got stuck again. Then I downgraded to 1.4.3 and it's been working properly now for a few days.

I also recommend downgrading to 1.4.3. In general it's good to stay close to the version Just Dice (dooglus) is using since it's the majority staker. Currently JD is running a variant of 1.4.2.1.

Additional note: You can use "getinfo" to find out the latest block you have and use khashier.com to see if you've fallen behind. If your node has fallen behind, you won't stake.

I'm seeing something very similar with my 64 bit win 7 version 1.4.4 wallet...  when i first start it, it will sync.  and sit there.  after 4 hours, it hasn't updated.  To get it to update, i have to close and re-start the client.  definitely not keeping up with things.

Hi guys

I'm running both 64 bit and 32 bit wallets on different Windows 7 computers the 64 bit shows a block 309812 and thinks it's up to date. The 32 bit  shows block 313277. I am running latest versions downloaded 24/01/2015.

When I look at file dates in package it shows 31/05/2013 in both packages 64 and 32 bit, the previous version showed file dates of 16/12/2014. I might be out of line but it looks wrong to me me...Any ideas?

Jon

Edit I've rolled back to previous version on 64 bit computer and it's sorted, so i would recommend not installing latest 64 bit

I was looking at Poloniex, trying to figure out how to ask its API for the most recently traded CLAM/BTC price.

It turns out there wasn't a way without either asking for the most recently traded price of all their currency pairs, or getting a list the most recent 200 CLAM trades. But now there is:

Just GET:

  https://poloniex.com/public?command=returnTradeHistory¤cyPair=BTC_CLAM&limit=1

It returns:

  [{"tradeID":188881,"date":"2015-01-26 21:44:26","type":"buy","rate":"0.00555597","amount":"0.20668765","total":"0.00114835"}]

which is a lot less data than the previous best way of doing it.

Good option, maybe add the value in $.

Is there anyone else having problems with wallet v. 1.4.4 not staking?  I was doing fine until two days ago, which is the last time the wallet has staked.  Could it be that I just am that unlucky or is there something I'm missing?

Funny video. Overweight middle-aged men acting dumb always make me laugh (do you see what I did there?)

I'm not exactly sure about the 'why' myself. The previous way was being abused by some kind of block-withholding and timewarp attacks, and a whole bunch of upstream changes were merged in to the CLAM client. It's hard to know which of them were brought in because they were a good idea, and which were just merged because they were there.


A block's chance is proportional to its size. It's not true that "each block of clams has the same chance as all the others". If it did, everyone would do best by splitting their 1 CLAM into a million tiny blocks and the blockchain would get very bloated as a result.

If weight increased with age, it might well become not worth staking most of the time. Why waste all that CPU time checking for staking opportunities every 16 seconds if you can just shut staking down and check for staking opportunities once per day? It seems like it's best for the network to have as many people staking as possible, but maybe it doesn't make a difference.


Bear in mind that the whole thing has to work without trust on a decentralised network. How am I to know when your client connected to the network and that you didn't just write a program that fakes it?

Well, thanks for the laugh, uglyvagina.

If you are certain that the given wallet.dat file contains keys corresponding to unspent outputs on May 12th:

The debug.log file should contain a short report concerning the import.  Please ensure no keys were "skipped".
If the keys were imported successfully, try restarting the client with the rescan flag.

If you are still having problems, please stop in to #clams on freenode IRC; haven't had a single claim we haven't been able to figure out yet

I'm trying to claim some clam from my old doge wallet and nothing seems to happen when I import the wallet.dat and enter the password for it. Am I doing something wrong here or am I just too impatient? There definitely were some doge in that wallet on 12th of May

Thanks I can improve upon CLAAMS.com also if you have any feature request cheers

   Excellent explanation Doog.  I knew age was no longer a factor, but not the why piece. 

It's to bad we can't somehow track the time actually staking and make that part of the factor.  Now it's all random, each block of clams has the same chance as all the others.  I believe this is hurting the smaller stakers.  I know eventually it will all even out, but in the shorter term they are not seeing a benefit to staking on their own.
So if you had the weight increase and then reset once a block is staked, more smaller investors might buy into staking.  It wouldn't cause them to get more shares, just more regularity.   

   I don't profess to really understanding how clams actually stake.  But if there was some way to factor in the weight while still keeping it somewhat random, that would be cool.
Maybe have a way to know when the client first connects to the network, and use that as the basis for the stake time weight.  Each time it connected it would reset to 0.   

 This doesn't really affect me, I've just changed my mindset from staking X per day to staking Y per week.  Since Just-Dice started I can no longer expect to stake a somewhat constant amount a day (+/- 30%). but for a week it's pretty regular (+/- 30%). 
     

That is an good option to check it.

You can check the value of your clams and find some other useful links and information on Claams.com

CLAM and just-dice in CLAM are still a work in progress but it is functionning well so far so it should grow bigger and better.

Putting JD chat on the blockchain would be interesting.

Hard to stake if block explorer always 7 blocks ahead.

I made a whole bunch of changes to clamd shortly before launching JD with CLAM. It was missing a lot of the features I needed to do what JD does (manage a shared wallet without disturbing the staking outputs more than necessary, split large deposits into multiple small outputs when staking them, report on the amount earned from staking, track the money supply, etc.) so I added them.

I contributed almost all of my changes back upstream, but apparently not all of them, so at some point I'm going to have to check which of my changes aren't in the latest official release and either merge them in or decide I don't need them. That's a job I've been putting off, but I'll get to it sooner or later.

So currently JD is running something which claims to be "BlackCoin version v1.4.2.1-468-g21ff975-dirty" when I run it with --help. The "BlackCoin" string has presumably been fixed in a recent release. I think what I'm running is based on the last release before ClamSpeech started actually working.

Speaking of which, I don't really understand the concept of ClamSpeech. I don't know if "expression of religious freedom - budhism" is a template which is meant to be replaced by an actual expression of religious freedom, or if that is a self-referential expression of freedom, but I was wondering whether it might be appropriate to use the most recently uttered line from the Just-Dice chat tab in each block that JD stakes. Then the blockchain contains real speech (however dumb), not just canned text, which presumably strengthens the argument that the blockchain is "speech".

Thanks for letting me know. Do you usually announce when JD updates to a new version? It seems like the safest thing for small stakers like me to do is update around the same time as JD. Actually, maybe the version of clam JD is running could be on the JD FAQ.