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

[almightyruler]

it seems my wallet refuses to sync after block 34001

Hard fork. Install the newer client.

[1714198949]

1714198949

[1714198949]

1714198949

[1714198949]

1714198949

[torrantz]

it seems my wallet refuses to sync after block 34001

Hard fork. Install the newer client.

i'm using the 1.4.2b client but it will not go further then 34001



edit: fixed by reloading the chain

[kbroadfoot]

The slow but relentless RISE OF THE CLAM!

https://poloniex.com/exchange/btc_clam

[macorcina]

From what date day and month must be BTC/LTC/DOGE  wallet to receive
CLAM coins ?

[dooglus]

From what date day and month must be BTC/LTC/DOGE  wallet to receive
CLAM coins ?

I don't know the exact date, but I have an address that has been empty since 2014-05-14 01:14:16 UTC and it received CLAMs.

So the date is earlier than that.

[macorcina]

From what date day and month must be BTC/LTC/DOGE  wallet to receive
CLAM coins ?

I don't know the exact date, but I have an address that has been empty since 2014-05-14 01:14:16 UTC and it received CLAMs.

So the date is earlier than that.

how much can I expect CLAM coins
whether for each address in one walet ?
it same for BTC, LTC, DOGE ?
how long after the key import in CLAM walet, coins show in wallet ?

[dooglus]

how much can I expect CLAM coins
whether for each address in one walet ?
it same for BTC, LTC, DOGE ?
how long after the key import in CLAM walet, coins show in wallet ?

Each address which had a "non dust" amount of BTC, LTC, or DOGE at a particular point in time (probably early May, 2014, but maybe earlier I'm not sure) already has exactly 4.60545574 CLAM in the corresponding CLAM address (that is, the CLAM address which has the same private key as the BTC, LTC, or DOGE address).

Coins will show in your CLAM wallet as soon as you import their key. If you import using "importprivkey", it takes a couple of minutes to do the rescan of the blockchain.

If you leave your wallet running, you can expect to see the 4.6... CLAMs growing, something like this:

http://khashier.com:2750/address/xUCggPFxSGHrFsFpXfVavavWcaSA5MmF7X

That's a random example - some stake faster, and some slower. Note how the 4.6 got split into 2.3 + 2.3 at one point, and later recombined into 5.01. The client automatically splits coins if they're staking too fast.

4.60545574 -> 4.61221837 -> 4.61254691 ---> 2.35 -> 2.45 -v-> 4.91254691 -> 5.01254691 ---> 2.55
                                        `-> 2.36254691 ---'                             `-> 2.56254691

[macorcina]

how much can I expect CLAM coins
whether for each address in one walet ?
it same for BTC, LTC, DOGE ?
how long after the key import in CLAM walet, coins show in wallet ?

Each address which had a "non dust" amount of BTC, LTC, or DOGE at a particular point in time (probably early May, 2014, but maybe earlier I'm not sure) already has exactly 4.60545574 CLAM in the corresponding CLAM address (that is, the CLAM address which has the same private key as the BTC, LTC, or DOGE address).

Coins will show in your CLAM wallet as soon as you import their key. If you import using "importprivkey", it takes a couple of minutes to do the rescan of the blockchain.

If you leave your wallet running, you can expect to see the 4.6... CLAMs growing, something like this:

http://khashier.com:2750/address/xUCggPFxSGHrFsFpXfVavavWcaSA5MmF7X

That's a random example - some stake faster, and some slower. Note how the 4.6 got split into 2.3 + 2.3 at one point, and later recombined into 5.01. The client automatically splits coins if they're staking too fast.

4.60545574 -> 4.61221837 -> 4.61254691 ---> 2.35 -> 2.45 -v-> 4.91254691 -> 5.01254691 ---> 2.55
                                        `-> 2.36254691 ---'                             `-> 2.56254691

thanks

And  if i want import privatekey from LTC wallet, DOGE wallet, and BTC wallet in same CLAM wallet ?

[JhoniOne]

my purse is not synchronized, help me please

[gjhiggins]

The client automatically splits coins if they're staking too fast.

Thanks for that analysis.

I haven't enquired deeply into the mechanics, meandthemissus are playing this with a totally straight bat, simply keeping the wallet open to allow staking. She's delighted that she now has 10 clams and I'm pleased to have 20.

From a our adopted naive perspective, CLAMs is functioning exactly as expected. In fact, it's been so painless we're beginning to wonder whether that's it or whether we're missing something. Not that it'd be a problem for either of us if the answer was “Nope, that's it.” but I guess others who don't have the benefit of our technical familiarity might find some reassurance useful.

FWIW.

“They also serve, those who only hold and stake” with apologies to the shade of John Milton.

Cheers,


Graham

[JhoniOne]

Give list node

[dooglus]

And  if i want import privatekey from LTC wallet, DOGE wallet, and BTC wallet in same CLAM wallet ?

I had a few different BTC, DOGE, etc. wallets, all with a few CLAM in them.

What I did was to first get a list of all the private keys which had CLAM in them, and then import all those private keys into a single CLAM wallet.

I got a list of the private keys with free CLAMs on them by running this with each wallet loaded in turn - it's a Linux shell command:

Code:

clamd listtransactions '*' 9999 | grep address | cut -d'"' -f4 | while read x; do echo $x $(clamd dumpprivkey $x); done

(basically, get a list of transactions, and for each one, dump the corresponding private key)

Then I ran a whole bunch of "importprivkey" commands in a new empty CLAM wallet.

importprivkey scans the whole blockchain for every private key you import, so I made a change to the client to stop it doing that:

https://github.com/nochowderforyou/clams/issues/5

I don't think there's an official build with that change available yet, but if there is I'm sure SuperClam will correct me.

[dooglus]

Give list node

A couple of people have been in the IRC channel this morning complaining that they can't find any peers to connect to, and I had the same problem myself.

Any idea why that might be?

In my case the issue was that I had "maxconnections=8" in my clam.conf, which apparently prevents any incoming connections from ever being accepted.

[almightyruler]

Give list node

In my case the issue was that I had "maxconnections=8" in my clam.conf, which apparently prevents any incoming connections from ever being accepted.

Same issue here, except that my limit is 16, and I currently have 16 connections.

I don't like to set it too high because if a coin forks the old peers go absolutely bonkers, repeatedly requesting blocks that they never accept, which wastes a heap of bandwidth.

[maccd123]

I have a Max of 16 Connections also when it was 56 3 days ago.

[SuperClam]

Sorry it has taken me so long to respond; it has been a busy week!


It seems there are quite a few people having sync issues.

The following build is a test build. 
It appears to functioning extremely well (including a few new features), but you should be aware it is currently being tested and is likely to have some flaws. 
If a user is using Windows, I would expect that the vast majority of issues might be solved by using this build:

CLAMClient Windows Test Build 1.4.2d

[dooglus]

Same issue here, except that my limit is 16, and I currently have 16 connections.

According to the source code,

static const int MAX_OUTBOUND_CONNECTIONS = 16;

And when someone tries to connection to you, it checks:

            else if (nInbound >= GetArg("-maxconnections", 125) - MAX_OUTBOUND_CONNECTIONS)


ie. if the total number of inbound connections is greater than or equal to (maxconnections minus 16) then it disallows the inbound connection.

If you have maxconnections set to 16, then "maxconnections - 16" is zero, and so any number of inbound connections is too many. The first 16 of whatever you set as maxconnections is reserved for outgoing connections.

[almightyruler]

If you have maxconnections set to 16, then "maxconnections - 16" is zero, and so any number of inbound connections is too many. The first 16 of whatever you set as maxconnections is reserved for outgoing connections.

I think you're right. I just checked some other coin daemons that are at capacity (16 connections) and the only one which didn't have 100% outbound connections was one with MAX_OUTBOUND_CONNECTIONS set to 8 in the source, rather than 16. Seems rather clumsy to limit inbound connections this way.

I'm going to bump -maxconnections up to 24 or 32.

[maccd123]

If you have maxconnections set to 16, then "maxconnections - 16" is zero, and so any number of inbound connections is too many. The first 16 of whatever you set as maxconnections is reserved for outgoing connections.

I think you're right. I just checked some other coin daemons that are at capacity (16 connections) and the only one which didn't have 100% outbound connections was one with MAX_OUTBOUND_CONNECTIONS set to 8 in the source, rather than 16. Seems rather clumsy to limit inbound connections this way.

I'm going to bump -maxconnections up to 24 or 32.

I now have 45 connections since updating to testbuild wallet.. Everythings fine.

[almightyruler]

My connection mix is also looking a lot better:

Code:

        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : true,
        "inbound" : true,
        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : true,
        "inbound" : false,
        "inbound" : false,
        "inbound" : false,
        "inbound" : true,
        "inbound" : true,

Ironic that people are having trouble finding "valid" peers to connect to with a popular coin.