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

Your wallet is unencrypted and staking=1?

Still having problems.

   "difficulty" : 43742.95218211,
    "search-interval" : 16,
    "weight" : 98.24037299,
    "netstakeweight" : 541828.10622686,
    "expectedtime" : 307566

This is a relatively modest balance, but I'm starting to become concerned about the length of time since I last staked. As I write this message, it has been 2014621 seconds (over 23 days) since my client last minted a block. According to the above estimate, I should mint a block in about 3.5 days.

Each time I check, the client is using zero CPU, and does not seem to be trying to stake.

reservebalance is set to false (amount=0)

I upgraded to the latest version a couple of days ago, but behaviour has not changed.

Any ideas?

Should I be laughing...?

0.0081. i know clam chart like the back of my hand.

$1 million market cap.

Yeah, we're short of peers that accept incoming connections.

Anyone who can should forward port 31174 on their router to help the network.

Thanks doog, i also found out today after being stuck with only 4 connections for days that it is definitely worth forwarding port 31174 if you're firewalled, i did and achieved 28+ connections within an hour.

Estimated time will vary depending on difficulty.

I have a balance of about 100 CLAM, so I should be staking every 3 or 4 days (on average), but in the real world it has been 21 days since I staked. I don't know if that's just bad luck, or there's a problem. I'm starting to think the latter.

Seems CLAM is going on up trend. How much stake is generated on coins kept in wallet. Say I have about 6 days before next lot of stake is generated for me. Yet I see this time going up and down why is this happening or is this due to more coin going into the wallet?

I was making a bunch of changes to the "importwallet" RPC command a few days back, including adding an optional "rescan" parameter, so the user can opt not to rescan after every import if he's doing a bunch of them.

I left all my wallets importing overnight, with no rescan, then wanted to run the rescan in the morning. I made a change to the code so it would only rescan the first 10,000 blocks of the chain, since that's where all the initial distribution happened, and I knew there were thousands of transactions in the chain for my imported addresses after that. I didn't need to see those transactions, I was only interested to see which imported addresses had free distribution CLAMs awarded to them. I was curious to know whether the import I did back in June had missed any.

So I rebuilt the client so it would only rescan the first 10k blocks and ran a rescan. It was pretty quick, and found 52 initial distribution transactions. All my wallets together had 52 funded addresses when the snapshot was taken. That was a nice surprise, because last time I checked, back in June, there were only 48 of them.

To my surprise, when I checked the balance of the wallet, it was around 18 CLAM. Somehow the wallet had figured out that I had already claimed the 48 addresses back in June, and only 4*4.6 CLAM were still available. It did that without rescanning the rest of the chain. I'm not sure how it did it, but it did. Maybe the transactions spending those 48 sets of 4.6 CLAMs were still hanging around in the wallet, although I thought -rescan was meant to clean out the transaction list and start from scratch. Maybe not. Maybe it just looks for new transactions and doesn't delete the old ones.

I forget what point I was trying to make. Probably that just rescanning the first 10k blocks is enough after importing a BTC wallet, because that's where the initial-distro magic happened. Maybe "importwallet" would be quicker if it only scanned those 10k blocks instead of the whole 340k block chain.

These claim to be running v1.4.7:

addnode=14.198.182.209
addnode=23.117.142.67
addnode=24.72.29.207
addnode=24.96.235.190
addnode=31.5.67.30
addnode=37.187.23.184
addnode=46.164.244.204
addnode=54.75.227.85
addnode=67.173.209.32
addnode=68.106.16.219
addnode=69.176.242.196
addnode=72.190.115.106
addnode=73.14.137.202
addnode=75.71.16.15
addnode=76.23.51.224
addnode=76.94.201.185
addnode=79.108.2.227
addnode=79.125.118.251
addnode=79.142.77.44
addnode=80.192.103.179
addnode=80.220.195.5
addnode=82.37.199.233
addnode=85.139.163.132
addnode=87.167.111.253
addnode=91.214.201.54
addnode=93.103.94.38
addnode=93.128.252.86
addnode=93.38.215.132
addnode=96.49.86.100
addnode=97.83.208.155
addnode=98.206.63.41
addnode=104.236.112.118
addnode=108.6.229.172
addnode=116.14.65.236
addnode=124.170.133.237
addnode=144.76.38.132
addnode=174.44.137.168
addnode=174.68.118.184
addnode=188.78.216.39
addnode=192.198.93.86
addnode=194.126.117.170
addnode=200.117.143.13
addnode=200.45.153.29
addnode=203.174.191.230
addnode=208.114.143.195
addnode=220.253.89.142

We are likely as thankful to have you aboard; as you are to be here

---

Absolutely awesome, BAC!
Freedom makes everything taste a bit better; horseradish or not

---

The chain has to be rescanned to identify incoming transactions for each and every key.  It would be completely normal for the client to freeze for quite a while if there are a large number of keys/addresses that need to be rescanned.

I currently have 75+ connections using the following...

Lots and lots of orphans on 1.4.7...   
No connections. Anyone have a good node list?

guys , im trying to import my wallets , the first 10 worked fine.
but when im trying to import my old 45 MB wallet , wallet goes no respond FOREVER

Got dinner with CLAM tonight!!!

Peer to Peer ftw!



Edit:

The fucking bastards forgot my horseradish though, Fuck!

CLAM has been my favorite spot in crypto since Just-Dice adopted it. It doesn't pretend to be anything it's not. It doesn't need marketing, the demand grows on its own based off of word of mouth and the quality of the JD experience. Many people have overlooked it simply based on the silly name and/or the confusing (and scary to some) distribution method. You have to suspend disbelief and spend some time on JD to understand what exactly this beast is... and what it might become in the future. This is a coin of the future and a coin of right now and I'm thankful every day to be part of it at this stage.

I seem to remember a history of trolling.....

That said, I must admit at least he is active on the forum otherwise.
I found some of the troll posts I am speaking of but didn't have the heart to quote them after I found a wealth of more productive posts.
Didn't expect to find any meat behind the growl.

A bit over-zealous on my part, possibly.

Whoa there; still your jerky knee!

It's not at all clear to me which side of this argument picolo was on. He could well have been saying the same as you. His statement leaves that ambiguous.