Author

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

legendary
Activity: 2940
Merit: 1333
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
legendary
Activity: 2940
Merit: 1333
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
hero member
Activity: 784
Merit: 1002
CLAM Developer
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.
legendary
Activity: 2940
Merit: 1333
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.
hero member
Activity: 784
Merit: 1002
CLAM Developer
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?
legendary
Activity: 2940
Merit: 1333
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.
sr. member
Activity: 342
Merit: 250
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
legendary
Activity: 2940
Merit: 1333
Is there anyone who is willing and able to download a copy of bootstrap.dat from me and make a torrent of it please?
legendary
Activity: 2940
Merit: 1333
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  Grin

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. Smiley
sr. member
Activity: 342
Merit: 250
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  Grin

legendary
Activity: 2940
Merit: 1333
also, how about posting a copy of the correct blockchain ready for download to make synching much faster and easier Smiley

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.
member
Activity: 116
Merit: 10
@tryphe your node doesn't seem to be running, I'm getting this a few times on the logfile
Quote
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 Smiley

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)
sr. member
Activity: 342
Merit: 250
also, how about posting a copy of the correct blockchain ready for download to make synching much faster and easier Smiley
hero member
Activity: 784
Merit: 1002
CLAM Developer
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'.
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
@tryphe your node doesn't seem to be running, I'm getting this a few times on the logfile
Quote
trying connection 67.35.116.81:31174 lastseen=365146.2hrs
I deleted peers.dat, used my previous chain with block @170980 wrong fork
run the clam-qt as you instructed with -rescan -reindex and it still perform like before...
it is continuing to 171046 and stuck (still downloading, perhaps trying to figure out the best fork)
currently with 13 active connections, never drop below 10

I think there are still a few (probably many) nodes running on the wrong fork, and my client keeps connecting to them
what is the use of data inside "txleveldb" dir? I was thinking maybe something left over here that makes it advance to 171046
it keeps downloading data from nodes (by looking at my network activity) but the block stuck at 171046
I'm gonna try let it run and hopefully it fixes itself without actually re-downloading the whole chain without warning to me

is there a way to figure out or indication when my client starts reconnecting to the correct chain?
where can I see that... other than checking my best block hash & comparing with khash Lips sealed
sr. member
Activity: 466
Merit: 250
you might have to delete your chain too due to having no versioning discrepancies.

Why doesn't the longest chain just replace the 2nd longest chain?

Edit: actually, a -reindex should make the client recognise that the blocks on the incorrect fork are no longer valid, right?

I think that's right. I've had a few people fork over successfully just from adding me as a node too.
i install new client,
 download from scratch whole blockchain ,
and
it's again stuk on blok 171001

after that i type
./clam-qt -reindex -rescan -addnode=67.35.116.81:31174
and  its suck again at blok 171001
plese help
sr. member
Activity: 342
Merit: 250
yehey! i finally won a stake lottery of 1 clam!

oh wait... all stakes are now 1 clam Wink

well thats 10 times what i was getting before! hurray for me!
member
Activity: 116
Merit: 10
you might have to delete your chain too due to having no versioning discrepancies.

Why doesn't the longest chain just replace the 2nd longest chain?

Edit: actually, a -reindex should make the client recognise that the blocks on the incorrect fork are no longer valid, right?

I think that's right. I've had a few people fork over successfully just from adding me as a node too.
legendary
Activity: 2940
Merit: 1333
you might have to delete your chain too due to having no versioning discrepancies.

Why doesn't the longest chain just replace the 2nd longest chain?

Edit: actually, a -reindex should make the client recognise that the blocks on the incorrect fork are no longer valid, right?
member
Activity: 116
Merit: 10
I need some help please... my chain is already at block 170980 before I downloaded the new client
and after I ran the new version, instead of reorganizing & reconnecting to the correct fork it keeps continuing up to 171046 and stuck.
what should I do to go from this situation and back to the right fork without re-downloading the whole chain from 0
is there a way to force my client to start re-download from specified block height from 1-3 trusted hand picked nodes only?
would deleting peers.dat helps weeding out the bad nodes with wrong fork?

Deleting peers.dat will definitely help.
Run with "-reindex -rescan -addnode=67.35.116.81:31174" and you should be on the correct chain, although you might have to delete your chain too due to having no versioning discrepancies (most likely you don't have to delete the chain though).
Jump to: