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

[ymod123]

I still got the error message when unlocking my wallet "
even i added server=1 to clam.conf      I cant unlocked my wallet

Error: RPC server was not started, use server=1 to change this. (code -18)

[1713459914]

1713459914

[1713459914]

1713459914

[1713459914]

1713459914

[SuperClam]

I still got the error message when unlocking my wallet "
even i added server=1 to clam.conf      I cant unlocked my wallet
Error: RPC server was not started, use server=1 to change this. (code -18)

I saw your post earlier -please, stop into freenode IRC #clams

http://clamclient.com/irc

We will try to figure out what has went wrong.


These issues are usually based on a problem with the user or password.
Newer versions of the code base have imposed restrictions on what is an acceptable user/pass combination.
Unfortunately, the error messages that result are not always very descriptive.

[ymod123]

I still got the error message when unlocking my wallet "
even i added server=1 to clam.conf      I cant unlocked my wallet
Error: RPC server was not started, use server=1 to change this. (code -18)

I saw your post earlier -please, stop into freenode IRC #clams

http://clamclient.com/irc

We will try to figure out what has went wrong.


These issues are usually based on a problem with the user or password.
Newer versions of the code base have imposed restrictions on what is an acceptable user/pass combination.
Unfortunately, the error messages that result are not always very descriptive.

i sent you message in IRC

[ymod123]

I still got the error message when unlocking my wallet "
even i added server=1 to clam.conf      I cant unlocked my wallet
Error: RPC server was not started, use server=1 to change this. (code -18)

I saw your post earlier -please, stop into freenode IRC #clams

http://clamclient.com/irc

We will try to figure out what has went wrong.


These issues are usually based on a problem with the user or password.
Newer versions of the code base have imposed restrictions on what is an acceptable user/pass combination.
Unfortunately, the error messages that result are not always very descriptive.

I manage to unlock it ... by going to settings  not in console..
tnx..

[tryphe]

I manage to unlock it ... by going to settings  not in console..
tnx..

Awesome! Btw I saw your message to SuperClam in channel a bit late (it's our IRC bot) and you had left already =/ So glad you got it sorted!

[BayAreaCoins]

yo

Looking to buy a few BTC worth of dem CLAMS

Can pay or trade. BTC cash ect.

[LtPaxIV]

hi i cant download the client,the website it is hosted on wants a decrytion key wich i dont have

[garthkiser]

hi i cant download the client,the website it is hosted on wants a decrytion key wich i dont have

What download link did you use?

Assuming you are using Windows, use this: https://mega.co.nz/#!MZtThQrS!qEN95et8yJSiOqHAMW3-r1RdRSb_piM0TGljxMRFpoc

It just worked fine on my end.

[vpsmmoforall]

what is the rules?... i really don't understand

[garthkiser]

what is the rules?... i really don't understand

The rules? Not sure what you mean. Stop by the IRC channel and somebody will be glad to help you: http://webchat.freenode.net/?channels=clams

Long Live the Great CLAM!!!

[mcdoom432]

what is the staking specs on this coin? How do you get clams?

[dooglus]

what is the staking specs on this coin?

It targets one block per minute, and pays 1 CLAM reward per block (plus transaction fees from included transactions).

Every 16 seconds each of the outputs in your wallet that hasn't moved for 4 hours and is mature (over 510 blocks since last staking) gets a chance to stake that is proportional to its size.

The network difficulty target is around 2000*2^200 at the moment. Each 16 seconds, each eligible output gets sha256 hashed, and has to get a value less than the difficulty target times its value in satoshis to qualify for staking.

That means that an output of around 66 CLAMs should stake once per day on average. Note that once it stakes, it takes 4 hours or 510 confirmations (whichever takes longer) before it is eligible to stake again. For that reason people tend to break their outputs up into smaller pieces, so that when one stakes the rest can continue attempting to stake without the delay.

Edit: here's the math I did to come up with 66 CLAMs as the size you need to average 1 stake per day. It might be wrong or at least inaccurate:

Code:

>>> 2**256 / 1e8 / (2000 * 2**200) * 16 / (60 * 60 * 24)
66.71999447956291

2**256 is the number of different outputs from sha256
1e8 is to get an answer in CLAMs, not satoshis
2000 * 2^200 is the network difficulty target
16 is the number of seconds between 'attempts' at staking
60*60*24 is the number of seconds in a day

How do you get clams?

Three ways:

1) buy them - from someone who has some - they're listed on poloniex here: https://www.poloniex.com/exchange/btc_clam

2) dig them - from the initial distribution - everyone who had a non-dust amount of BTC, LTC, or DOGE in May 2014 was given 4.6 CLAM as part of the initial distribution. Import your old BTC, LTC, or DOGE wallet into the CLAM client to import your old private keys. You might want to make sure that the keys are "empty" first if you don't trust the CLAM client. There are over 15 million CLAMs that were given away in this way which haven't been "dug" yet.

3) stake them - as described above staking currently returns a little over 1% growth per day for those actively staking. The growth will continue to be 1440 CLAM per day, but as the active coinbase grows, that will come to represent a smaller percentage growth for each staker.

[jd1959]

Thanks dooglus

I love your tech talk please keep it going. I find it both informative and thoughtful.

Jon 

[dooglus]

I just ported my 'dumpbootstrap' RPC command to the new version of the client, dumped a new bootstrap.dat file, and uploaded it to Amazon S3. I updated my old post about it:

I'll post a torrent link once it's done.

Here:

  https://s3.amazonaws.com/dooglus/bootstrap.dat?torrent

and here, if you want a direct link, rather than a torrent:

  https://s3.amazonaws.com/dooglus/bootstrap.dat

Download that, copy it to your clam folder (where the wallet.dat lives) and restart the CLAM client. It will notice the bootstrap.dat file, and import the blockchain up to block 176750 219000 from it. Then it will connect to peers and carry on from there.

To check, see if the sha256 hash matches mine:

$ sha256sum /tmp/bootstrap.dat
3965815c11e4cbdafe99ebb55448c7a4abe730e0e8bd6fc42cf2b031cef32443  /tmp/bootstrap.dat
76d9481ac6bd5ec48fb71f0fd306f9fe9b82c4a9a957f64ffa05226e5abe1abe  /tmp/bootstrap.dat

Edit: I ran:

clamd dumpbootstrap /tmp/bootstrap.dat 219000

If someone is willing to run the same command after rebuilding with my patch and verify that the sha256 hash is the same, that would be helpful.

[Nthused]

I've just downloaded 2 separate CLAMS Windows clients from 2 different Official links, both stated they are CLAMS 1.4.3.0 but when I look inside the wallet it shows v1.4.2.1 is there something I'm missing or did the Dev just not update that part ?

[dooglus]

I've just downloaded 2 separate CLAMS Windows clients from 2 different Official links, both stated they are CLAMS 1.4.3.0 but when I look inside the wallet it shows v1.4.2.1 is there something I'm missing or did the Dev just not update that part ?

My client says 1.4.2.1 in the Help->About CLAM dialog too, and I know I'm running 1.4.3.0.

I don't know where it gets that version string from.

[xploited]

I've just downloaded 2 separate CLAMS Windows clients from 2 different Official links, both stated they are CLAMS 1.4.3.0 but when I look inside the wallet it shows v1.4.2.1 is there something I'm missing or did the Dev just not update that part ?

My client says 1.4.2.1 in the Help->About CLAM dialog too, and I know I'm running 1.4.3.0.

I don't know where it gets that version string from.

It depends on how its built. The version string can be pulled from git, and a few other places. It will be updated in the next client release which should be tomorrow.  The version slipped through the crack on the most recent update.

[LuckyAlt]

I have added the following services for CLAM to my webiste.

Explorer: http://blocks.luckyalt.com:3003

Dice: http://www.luckyalt.com/clamcoin

Faucet: http://www.luckyalt.com/clamcoinfaucet

[SuperClam]

I have added the following services for CLAM to my webiste.
Explorer: http://blocks.luckyalt.com:3003
Dice: http://www.luckyalt.com/clamcoin
Faucet: http://www.luckyalt.com/clamcoinfaucet

Please ensure that you are building the correct version of the CLAMclient and have a working block chain for your services.
The block data appears to be incorrect on the explorer linked.

[xploited]

I have added the following services for CLAM to my webiste.
Explorer: http://blocks.luckyalt.com:3003

Not that we don't appreciate the services (cause we do!) but your block explorer doesn't work correctly.


Porting our coin to ABE has proved to be quite the challenge due to our last fork. I don't have the necessary python skills to do what I need to. Annoyingly I know exactly what needs to be done, just unsure how to do it in the mess known as Abe.

The problem is we switched to sha256 block hashing in the new fork for performance reasons but ABE alloys no easy way to switch the way it parses the headers for a chain.  

I have the current code updates I've made if anyone wants to take a shot. It almost works but after 203500 it parses the block headers incorrectly

you can reach me on our IRC channel