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

[SuperClam]

The patience and faith is appreciated.


The issues reported by some users seem to be similar to issues that have been experienced with other chains (including Bitcoin) after hard-forks. 

We had intended to push another update very soon anyway to incorporate some good work dooglus contributed which fixes some of the timestamp and difficulty fudging that has been occurring on the chain. 

In addition, it looks like one of the features we had intended to add at the next update, to help make CLAMS more resistant to censorship and licensing, will be ripe for the picking as well.


Working on getting it all polished and ready to ship.

Again, better we experience these frailties in the protocol now and repair them, adding resilience; than letting 'sleeping dogs lie'.

[istvandv]

also, how about posting a copy of the correct blockchain ready for download to make synching much faster and easier

[tryphe]

@tryphe your node doesn't seem to be running, I'm getting this a few times on the logfile

trying connection 67.35.116.81:31174 lastseen=365146.2hrs

Sorry about that, I had to cap the connections for a bit. It works now, port changed:

Code:

-addnode=67.35.116.81:54545

Make sure you are up to block 170,000

also, how about posting a copy of the correct blockchain ready for download to make synching much faster and easier

It would be fantastic if someone did this to get things rolling again. Unfortunately I don't have the upstream bandwidth available. (Would take 3 days =D)

[dooglus]

also, how about posting a copy of the correct blockchain ready for download to make synching much faster and easier

Not a bad idea.

There's already code in the CLAM client that checks for the existence of a specially formatted file called 'bootstrap.dat' and if it finds it, it uses it to import the blockchain.

There's a blockchain.dat available as a bittorrent download (see this thread). I will try to make a bootstrap.dat for CLAMs too, and make a torrent available.

I don't have much bandwidth available either, but if people are willing to seed a torrent it could work.

Probably the way forward is to add a "dumpbootstrap" RPC call to the CLAM client that makes it dump a bootstrap.dat file, which people can then seed.

I'll see what I can do.

[istvandv]

now that you mention it, ive already used a bootstrap.dat from HYP and it has been very efficient

theirs was 55MB for 119,000 blocks so its pretty small

i have absolutely no idea how to create one though or even if i am on the right chain so ill leave it to the experts 

[dooglus]

now that you mention it, ive already used a bootstrap.dat from HYP and it has been very efficient

theirs was 55MB for 119,000 blocks so its pretty small

i have absolutely no idea how to create one though or even if i am on the right chain so ill leave it to the experts 

Long ago I wrote some code that uses the Armory library to dump a fresh copy of bootstrap.dat, but I don't think Armory works with CLAMs, and so that's not going to work.

I figure it will be quickest to modify CLAM-qt to be able to create a bootstrap.dat from its own copy of the blockchain - which is what I'm currently attempting to do.

[dooglus]

Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?

[istvandv]

Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?

wish i could help
torrent is blocked by my ISP, i use zbigz to download torrent files

[dooglus]

Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?

wish i could help
torrent is blocked by my ISP, i use zbigz to download torrent files

I guess I can upload it to mega or a similar service. I don't really like mega, for it's ugly URLs and weird download system, but I'll find somewhere to host it.

[SuperClam]

Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?

Triple check that it is the correct chain, and then go ahead and possibly upload it to the repository?

[dooglus]

Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?

Triple check that it is the correct chain, and then go ahead and possibly upload it to the repository?

It's the correct chain.

I modified clamd to have a new command, "makebootstrap", which dumps a bootstrap.dat file containing all blocks up to a specified height, then ran:

./clamd makebootstrap /tmp/bootstrap.dat 176750

Then I shut down clamd, renamed my .clam folder so I had no blockchain, made a new .clam folder, but the bootstrap.dat in it, and ran "clamd -connect=127.0.0.1" to prevent it from being able to connect to any peers, and it started very quickly importing blocks from the bootstrap file:

Code:

keypool added key 99, size=99
keypool added key 100, size=100
keypool added key 101, size=101
 wallet                 8471ms
ERROR: ProcessBlock() : already have block 0 00000c3ce6b3d823a352
SetBestChain: new best=00000feca63cbde35071  height=1  trust=2097154  blocktrust=1048577  date=05/15/14 22:25:35
ProcessBlock: ACCEPTED
SetBestChain: new best=0000042f7f9811948352  height=2  trust=3145731  blocktrust=1048577  date=05/15/14 22:25:36
ProcessBlock: ACCEPTED
SetBestChain: new best=00000d732f526fd6dac4  height=3  trust=4203073  blocktrust=1057342  date=05/15/14 22:25:38
ProcessBlock: ACCEPTED

So it seems to be working fine.

I'm now uploading the bootstrap.dat to Amazon S3.

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

[SuperClam]

Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?

Triple check that it is the correct chain, and then go ahead and possibly upload it to the repository?

It's the correct chain.
I modified clamd to have a new command, "makebootstrap", which dumps a bootstrap.dat file containing all blocks up to a specified height, then ran:
./clamd makebootstrap /tmp/bootstrap.dat 176750
Then I shut down clamd, renamed my .clam folder so I had no blockchain, made a new .clam folder, but the bootstrap.dat in it, and ran "clamd -connect=127.0.0.1" to prevent it from being able to connect to any peers, and it started very quickly importing blocks from the bootstrap file:

Code:

keypool added key 99, size=99
keypool added key 100, size=100
keypool added key 101, size=101
 wallet                 8471ms
ERROR: ProcessBlock() : already have block 0 00000c3ce6b3d823a352
SetBestChain: new best=00000feca63cbde35071  height=1  trust=2097154  blocktrust=1048577  date=05/15/14 22:25:35
ProcessBlock: ACCEPTED
SetBestChain: new best=0000042f7f9811948352  height=2  trust=3145731  blocktrust=1048577  date=05/15/14 22:25:36
ProcessBlock: ACCEPTED
SetBestChain: new best=00000d732f526fd6dac4  height=3  trust=4203073  blocktrust=1057342  date=05/15/14 22:25:38
ProcessBlock: ACCEPTED

So it seems to be working fine.
I'm now uploading the bootstrap.dat to Amazon S3.
I'll post a torrent link once it's done.

Quite awesome; and kind.

[dooglus]

Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?

Triple check that it is the correct chain, and then go ahead and possibly upload it to the repository?

It's the correct chain.
I modified clamd to have a new command, "makebootstrap", which dumps a bootstrap.dat file containing all blocks up to a specified height, then ran:
./clamd makebootstrap /tmp/bootstrap.dat 176750
Then I shut down clamd, renamed my .clam folder so I had no blockchain, made a new .clam folder, but the bootstrap.dat in it, and ran "clamd -connect=127.0.0.1" to prevent it from being able to connect to any peers, and it started very quickly importing blocks from the bootstrap file:

Code:

keypool added key 99, size=99
keypool added key 100, size=100
keypool added key 101, size=101
 wallet                 8471ms
ERROR: ProcessBlock() : already have block 0 00000c3ce6b3d823a352
SetBestChain: new best=00000feca63cbde35071  height=1  trust=2097154  blocktrust=1048577  date=05/15/14 22:25:35
ProcessBlock: ACCEPTED
SetBestChain: new best=0000042f7f9811948352  height=2  trust=3145731  blocktrust=1048577  date=05/15/14 22:25:36
ProcessBlock: ACCEPTED
SetBestChain: new best=00000d732f526fd6dac4  height=3  trust=4203073  blocktrust=1057342  date=05/15/14 22:25:38
ProcessBlock: ACCEPTED

So it seems to be working fine.
I'm now uploading the bootstrap.dat to Amazon S3.
I'll post a torrent link once it's done.

Quite awesome; and kind.

It's still uploading, but if you already have a full copy of the correct fork of the CLAM blockchain, you can create your own bootstrap.dat file by building from this branch:

  https://github.com/dooglus/clams/tree/dumpbootstrap

or merging this pull request:

  https://github.com/nochowderforyou/clams/pull/56

and then running this:

  clamd makebootstrap /tmp/bootstrap.dat 176750

It should make an identical file, which you can use to seed the torrent I'll be posting a link to soon without having to download it.

To check, see if the sha256 hash matches mine:

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

[dooglus]

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

[Thirdspace]

need help really bad here... wasted so much bandwith on the last attempt to resynch
the block still stuck @171046 wrong fork and won't fixes itself eventhough I let it run and consumed 300 MB bandwith
my logfile spammed by hundreds of this same errors:

received block 433bcffd6b53c4ddb502
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 7304be6a68b7b41d6a5a3cefd55beeaa05c35bf485ea2f39dc254eb302fdc6e7, hashProof=a0276da97ea53d924999ac3e6b008c310f8245996ca00abc54ce2fc401c22500
WARNING: AcceptBlock(): check proof-of-stake failed for block 433bcffd6b53c4ddb502b539dec840d6823ae052566a6888ca7b0fdd25d9fe67
ERROR: ProcessBlock() : AcceptBlock FAILED

that block 433bcff is block 170622 on correct chain, but why my client is spouting those error messages?
what makes my client downloads so much data & not resync the correct chain?
are there some nodes out there running wrong fork deliberately just to screw us up?
sorry guys... I'm a bit frustrated trying to get my CLAM back on the main chain

is there a way for me to remove a few blocks (something like rollback) from my chain?
if possible I want to try disconnect all blocks starting from 170000+ and try to resynch again
or is it possible to use my own blk0001.dat (maybe rename it first) & import only up to block 170000, then go online and resynch the rest?
something like "-loadblock=oldblk0001.dat" but how do I set it just to import up to 170000?

[paulc010]

I have these in my clam.conf file (from previous sync. issues these were posted in here):

Code:

addnode=24.67.30.88
addnode=198.245.60.38
addnode=65.102.47.162
addnode=24.184.168.36
addnode=93.103.131.59
addnode=85.17.81.164
addnode=142.4.201.123
addnode=84.194.247.232
addnode=220.253.2.201
addnode=188.116.147.85
addnode=85.17.81.169
addnode=109.223.234.123
addnode=173.68.204.192
addnode=198.245.60.38
addnode=107.192.136.116
addnode=24.238.75.8
addnode=184.9.244.44
addnode=79.206.224.49
addnode=207.61.182.125
addnode=216.46.33.120
addnode=99.233.92.9
addnode=85.191.52.188
addnode=67.201.165.63
addnode=82.26.243.220
addnode=24.238.75.8
addnode=65.102.47.162
addnode=75.131.208.152
addnode=76.173.48.220
addnode=84.194.247.232
addnode=85.191.52.188
addnode=93.103.131.59
addnode=107.192.136.116
addnode=142.4.201.123
addnode=173.68.204.192
addnode=184.9.244.44
addnode=188.116.147.85
addnode=203.20.114.252
addnode=216.46.33.120
addnode=220.253.2.201

[istvandv]

need help really bad here... wasted so much bandwith on the last attempt to resynch
the block still stuck @171046 wrong fork and won't fixes itself eventhough I let it run and consumed 300 MB bandwith
my logfile spammed by hundreds of this same errors:

received block 433bcffd6b53c4ddb502
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 7304be6a68b7b41d6a5a3cefd55beeaa05c35bf485ea2f39dc254eb302fdc6e7, hashProof=a0276da97ea53d924999ac3e6b008c310f8245996ca00abc54ce2fc401c22500
WARNING: AcceptBlock(): check proof-of-stake failed for block 433bcffd6b53c4ddb502b539dec840d6823ae052566a6888ca7b0fdd25d9fe67
ERROR: ProcessBlock() : AcceptBlock FAILED

that block 433bcff is block 170622 on correct chain, but why my client is spouting those error messages?
what makes my client downloads so much data & not resync the correct chain?
are there some nodes out there running wrong fork deliberately just to screw us up?
sorry guys... I'm a bit frustrated trying to get my CLAM back on the main chain

is there a way for me to remove a few blocks (something like rollback) from my chain?
if possible I want to try disconnect all blocks starting from 170000+ and try to resynch again
or is it possible to use my own blk0001.dat (maybe rename it first) & import only up to block 170000, then go online and resynch the rest?
something like "-loadblock=oldblk0001.dat" but how do I set it just to import up to 170000?

try the bootstrap provided by dooglus

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

rename clam folder so no blockchain, make a new clam folder, put the bootstrap.dat in it, and run "clam-qt.exe -connect=127.0.0.1" to prevent it from being able to connect to any peers

[dooglus]

is there a way for me to remove a few blocks (something like rollback) from my chain?
if possible I want to try disconnect all blocks starting from 170000+ and try to resynch again
or is it possible to use my own blk0001.dat (maybe rename it first) & import only up to block 170000, then go online and resynch the rest?
something like "-loadblock=oldblk0001.dat" but how do I set it just to import up to 170000?

try the bootstrap provided by dooglus

Using the -makebootstrap RPC command I wrote yesterday you could make a bootstrap.dat containing blocks up to 170000, then make a new clam folder and initialise it from the bootstrap file you made.

That would save you having to download the blockchain over again, but would require you to build the CLAM client yourself.

[Quantum12]

thanx dooglus, I was stuck for ages , but your above method works great

so thanks again!

has staking been disabled now then ?

[dooglus]

thanx dooglus, I was stuck for ages , but your above method works great

so thanks again!

has staking been disabled now then ?

You're welcome.

The lottery has been disabled. It used to be that you got 0.1 CLAM almost every time you staked, but occasionally you got a much bigger reward, up to 1000 CLAM. The long-term average was meant to be 1 CLAM per stake.

It turns out the lottery was exploitable and so now everyone gets 1 CLAM per stake (plus any transaction fees for transactions you include in the staked block).

Some block rewards before the lottery was suspended:



And after: