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

[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.

[Zer0Sum]

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

Yup...

If you guys are serious about mining; I can bump it up on the list of TODO's.
Take a look at it tonight.

Been trying to delegate and divide up time as efficiently as possible... given the lack of interest in the Multi-Pool, adding an additional algorithm to dilute hash was not a priority (though still planned).

Speculative GPU miners I think are a lot more common then speculative scrypt miners. 
And nscrypt profitability has dropped a lot lately, it's just not worth mining compared to X11 or X13.

I mined for a bit with nscrypt when it was worthwhile, but am waiting to point my rigs at khashier until we have some new algos.  And I think you'll see there are others in the same boat as me.

Also, as someone else said, people really like stats.  More stats would probably help the multi-pool more then anything.

Yes, miners love stats more than anything except one thing.

You get an idea of general MultiPool demographics by checking the BlackCoin Pool:

Scrypt......818
X11..........542
SHA256.....157
Scrypt-N...12

http://blackcoinpool.com/dashboard

The world is awash in cheap Scrypt ASICs...
And the CLAM MultiPool will get more and more important as CLAM cap grows...
So there have to be promotions for new people to go on Clam Hunts.

As for the current Stake rate annualized.. here's my numbers for last 6.6 days:

320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

[whatsabitworth]

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

This worked for me. wallet synced and I'm back in Clams
thank you.

[phzi]

As for the current Stake rate annualized.. here's my numbers for last 6.6 days:

320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

Uh, (3.80/320) ^ (365/6.6) = 0.  Not so sure about your math there.

[dooglus]

As for the current Stake rate annualized.. here's my numbers for last 6.6 days:

320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

Uh, (3.80/320) ^ (365/6.6) = 0.  Not so sure about your math there.

The 1+ is meant to be inside the parentheses:

>>> (1 + 3.80/320) ** (365/6.6)
1.921017101683441

92%

[SuperClam]

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

Yup...

If you guys are serious about mining; I can bump it up on the list of TODO's.
Take a look at it tonight.
Been trying to delegate and divide up time as efficiently as possible... given the lack of interest in the Multi-Pool, adding an additional algorithm to dilute hash was not a priority (though still planned).

Speculative GPU miners I think are a lot more common then speculative scrypt miners. 
And nscrypt profitability has dropped a lot lately, it's just not worth mining compared to X11 or X13.
I mined for a bit with nscrypt when it was worthwhile, but am waiting to point my rigs at khashier until we have some new algos.  And I think you'll see there are others in the same boat as me.
Also, as someone else said, people really like stats.  More stats would probably help the multi-pool more then anything.

Yes, miners love stats more than anything except one thing.
You get an idea of general MultiPool demographics by checking the BlackCoin Pool:
Scrypt......818
X11..........542
SHA256.....157
Scrypt-N...12
http://blackcoinpool.com/dashboard
The world is awash in cheap Scrypt ASICs...
And the CLAM MultiPool will get more and more important as CLAM cap grows...
So there have to be promotions for new people to go on Clam Hunts.
As for the current Stake rate annualized.. here's my numbers for last 6.6 days:
320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

Work has already begun to add x11 to the CLAMS Multi-pool

[phzi]

Work has already begun to add x11 to the CLAMS Multi-pool

WIN!  I want to mine me some X11 CLAMs!

[kbroadfoot]

Just curious:

Is that 1.5 BTC buy support @ 0.0015 the 'Clam Shell'?

[dooglus]

Just curious:

Is that 1.5 BTC buy support @ 0.0015 the 'Clam Shell'?

No.

[romerun]

can I just claim my Clam, is it too late ? how to

[dooglus]

can I just claim my Clam, is it too late ? how to

Any BTC, LTC, or DOGE private key which had some non-dust amount of coin on it some time in early May this year will have 4.6 or so CLAM on it too.

Simply export the private key from your BTC (or LTC, or DOGE) client and import it into the CLAM client.

Alternately, you can just copy your wallet.dat from the BTC data folder into the CLAM data folder, then run "clam-qt -rescan" to have it check all the private keys in that wallet.

A natural concern is that the CLAM wallet software will steal the BTC from the private keys you give it. I have given it private keys with hundreds of BTC on, and it hasn't stolen any of them.

If you're concerned, you can make sure the private keys you give it have already been emptied out of BTC - then you don't have to trust the CLAM software.

[sixteendigits]

Damn it.  I just spent the last hour importing all my private keys from blockchain.info and moving all my BTC and any assets I hold tied to a BTC address (maidsafe, XCP, AGS) to new addresses cuz I'll be damned if the clams client is getting any private keys that are worth anything to me.  I'm all set to claim my clams and.......client won't sync.  0 nodes.  Yes, I am using the latest build.  Can someone gives me some nodes?