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

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: ElectronicFerocious on December 03, 2014, 12:00:38 PM

Ok, still no luck with that link, even after an hour the clock continues to drift.

Since i'm running windows Server 2008 i followed the instructions here http://support.microsoft.com/kb/816042

Now set to sync every 60 seconds

OK, fair enough. I reformat Windows partitions on sight, so I'm unable to try it for myself. I'm glad you found something that works, anyway.

Did your client get back on the right fork pretty quickly when you fixed the clock and restarted it?

http://khashier.com/ shows the right fork, btw.

ElectronicFerocious

newbie

Activity: 5

Merit: 0

Ok, still no luck with that link, even after an hour the clock continues to drift.

Since i'm running windows Server 2008 i followed the instructions here http://support.microsoft.com/kb/816042

Now set to sync every 60 seconds

ElectronicFerocious

newbie

Activity: 5

Merit: 0

Quote from: dooglus on December 02, 2014, 04:08:10 PM

ntp takes up to an hour to start doing its thing, but then works very well.

Your clock appears to lose about 2 seconds per minute. So in a 15 minute interval you'll lose 30 seconds, which it enough to harm your chances of successfully staking.

ntp is meant to figure out how much your clock loses, and then speed it up to compensate, so it's always right. That's better than having 15 minutes of drift followed by a sudden correction.

This is good to know, thanks! I'll try it again and report back.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: ElectronicFerocious on December 02, 2014, 03:46:34 PM

I tried that one initially but after inputting some ntp servers I was still over 20 seconds off from time.gov after a reboot.. and I couldn't really tell if it was running.

Now i'm using NetTime sync tool from here: http://www.timesynctool.com

Works like a charm. Will sync your clock every x minutes/hours/days. I'm using the minimum 15 minute interval and it runs in the system tray so you can tell its working. (i'm always within 1 or 2 seconds from time.gov now) Recommended

ntp takes up to an hour to start doing its thing, but then works very well.

Your clock appears to lose about 2 seconds per minute. So in a 15 minute interval you'll lose 30 seconds, which it enough to harm your chances of successfully staking.

ntp is meant to figure out how much your clock loses, and then speed it up to compensate, so it's always right. That's better than having 15 minutes of drift followed by a sudden correction.

ElectronicFerocious

newbie

Activity: 5

Merit: 0

Quote from: dooglus on December 02, 2014, 03:14:14 PM

Quote from: ElectronicFerocious on December 02, 2014, 02:58:24 PM

Quote from: dooglus on December 02, 2014, 08:46:06 AM

If that's you, fix your clock!

Sorry!

Fixed Tongue

From IRC:

16:46 < dooglus> you can probably find ntp for windows to keep your clock right
16:47 < dooglus> see http://www.satsignal.eu/ntp/setup.html
16:51 < ElectronicFeroc> this is perfect, thanks

Did you use that? Did it fix the problem? Was it easy? Etc.

Feedback would probably help others who have trouble stopping their clock drifting.

I tried that one initially but after inputting some ntp servers I was still over 20 seconds off from time.gov after a reboot.. and I couldn't really tell if it was running.

Now i'm using NetTime sync tool from here: http://www.timesynctool.com

Works like a charm. Will sync your clock every x minutes/hours/days. I'm using the minimum 15 minute interval and it runs in the system tray so you can tell its working. (i'm always within 1 or 2 seconds from time.gov now) Recommended

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: ElectronicFerocious on December 02, 2014, 02:58:24 PM

Quote from: dooglus on December 02, 2014, 08:46:06 AM

If that's you, fix your clock!

Sorry!

Fixed Tongue

From IRC:

16:46 < dooglus> you can probably find ntp for windows to keep your clock right
16:47 < dooglus> see http://www.satsignal.eu/ntp/setup.html
16:51 < ElectronicFeroc> this is perfect, thanks

Did you use that? Did it fix the problem? Was it easy? Etc.

Feedback would probably help others who have trouble stopping their clock drifting.

ElectronicFerocious

newbie

Activity: 5

Merit: 0

Quote from: dooglus on December 02, 2014, 08:46:06 AM

If that's you, fix your clock!

Sorry!

Fixed Tongue

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: paulc010 on December 02, 2014, 04:00:02 AM

Interesting article on the ethereum blog regarding proof of stake.

CLAM on!

Ha.

So I read the article, and it scared me. I'm not clear whether CLAMs are vulnerable to such an attack, but I don't see why not. Other than checkpoints (the most recent of which was at block 175000, on Mon Oct 27) I don't see what there is to prevent me from re-writing the blockchain to (for example) not have me transfer a bunch of CLAMs to an exchange a few weeks ago.

So then I happened to look at my debug.log and noticed someone was staking an alternative fork of the CLAM chain, at block heights about 100 below the main chain, but catching up very quickly. I panicked, thinking it was some kind of attack, and spent the next few hours trying to figure out what was going on. He somehow managed to 'trick' the network difficulty into going incredibly low:

Quote

2014-12-02 04:42:50 NotBestChain: hash=f46334f4 difficulty=9195.35438786 height=233400 trust=1151616512706583512 blocktrust=39494349006920 date=12/02/14 03:33:52
2014-12-02 06:59:10 NotBestChain: hash=07d6052f difficulty=8434.12641464 height=233401 trust=1151652737556452057 blocktrust=36224849868545 date=12/02/14 05:51:28
2014-12-02 07:50:20 NotBestChain: hash=c2eea75b difficulty=7293.37664742 height=233402 trust=1151684062848616141 blocktrust=31325292164084 date=12/02/14 06:42:40
2014-12-02 07:52:48 NotBestChain: hash=39e273f4 difficulty=6172.78703038 height=233403 trust=1151710575171582753 blocktrust=26512322966612 date=12/02/14 06:45:04
2014-12-02 08:44:20 NotBestChain: hash=68c4680a difficulty=5219.83578106 height=233404 trust=1151732994537645277 blocktrust=22419366062524 date=12/02/14 07:35:12
2014-12-02 09:36:40 NotBestChain: hash=7bd3ad47 difficulty=4325.83145490 height=233405 trust=1151751574125774107 blocktrust=18579588128830 date=12/02/14 08:27:28
2014-12-02 09:41:55 NotBestChain: hash=accdeb9b difficulty=3511.81309368 height=233406 trust=1151766657478314820 blocktrust=15083352540713 date=12/02/14 08:32:32
2014-12-02 09:42:28 NotBestChain: hash=4bcf9b82 difficulty=2847.41721749 height=233407 trust=1151778887228753186 blocktrust=12229750438366 date=12/02/14 08:33:04
2014-12-02 09:44:57 NotBestChain: hash=e417c33f difficulty=2308.71707651 height=233408 trust=1151788803244398910 blocktrust=9916015645724 date=12/02/14 08:35:28
2014-12-02 09:59:25 NotBestChain: hash=c942864e difficulty=1871.15517176 height=233409 trust=1151796839917297258 blocktrust=8036672898348 date=12/02/14 08:51:28
2014-12-02 10:03:37 NotBestChain: hash=e5cedd20 difficulty=1508.37236402 height=233410 trust=1151803318426125111 blocktrust=6478508827853 date=12/02/14 08:55:28
2014-12-02 10:04:09 NotBestChain: hash=64c59901 difficulty=1213.91948378 height=233411 trust=1151808532250164576 blocktrust=5213824039465 date=12/02/14 08:56:00
2014-12-02 10:06:55 NotBestChain: hash=725450f4 difficulty=977.35060701 height=233412 trust=1151812730003111022 blocktrust=4197752946446 date=12/02/14 08:58:40
2014-12-02 10:08:00 NotBestChain: hash=e101d065 difficulty=786.88428286 height=233413 trust=1151816109696941673 blocktrust=3379693830651 date=12/02/14 08:59:44
2014-12-02 10:10:29 NotBestChain: hash=2e42d199 difficulty=633.27467262 height=233414 trust=1151818829632452888 blocktrust=2719935511215 date=12/02/14 09:02:08
2014-12-02 10:11:56 NotBestChain: hash=e92bb7b5 difficulty=509.24146304 height=233415 trust=1151821016841256588 blocktrust=2187208803700 date=12/02/14 09:03:28
2014-12-02 10:12:09 NotBestChain: hash=3055f5e7 difficulty=409.49377593 height=233416 trust=1151822775630469132 blocktrust=1758789212544 date=12/02/14 09:03:44
2014-12-02 10:14:57 NotBestChain: hash=2025e8ae difficulty=329.69696970 height=233417 trust=1151824191689778921 blocktrust=1416059309789 date=12/02/14 09:06:24
2014-12-02 10:15:30 NotBestChain: hash=f6e577b5 difficulty=265.55907307 height=233418 trust=1151825332274716839 blocktrust=1140584937918 date=12/02/14 09:06:56
2014-12-02 10:16:04 NotBestChain: hash=d8df3407 difficulty=213.89634729 height=233419 trust=1151826250966551325 blocktrust=918691834486 date=12/02/14 09:07:28
2014-12-02 10:16:21 NotBestChain: hash=c57137c2 difficulty=172.28342575 height=233420 trust=1151826990929521523 blocktrust=739962970198 date=12/02/14 09:07:44
2014-12-02 10:18:03 NotBestChain: hash=d6e7dd63 difficulty=138.82350994 height=233421 trust=1151827587181054716 blocktrust=596251533193 date=12/02/14 09:09:20
2014-12-02 10:18:19 NotBestChain: hash=69884ef2 difficulty=111.86206069 height=233422 trust=1151828067632278140 blocktrust=480451223424 date=12/02/14 09:09:36
2014-12-02 10:19:11 NotBestChain: hash=b5c18a0e difficulty=90.28608331 height=233423 trust=1151828455413970304 blocktrust=387781692164 date=12/02/14 09:10:24
2014-12-02 10:19:43 NotBestChain: hash=842f20f9 difficulty=72.84164275 height=233424 trust=1151828768271217528 blocktrust=312857247224 date=12/02/14 09:10:56
2014-12-02 10:19:59 NotBestChain: hash=eef80eae difficulty=58.79205638 height=233425 trust=1151829020785029989 blocktrust=252513812461 date=12/02/14 09:11:12
2014-12-02 10:20:31 NotBestChain: hash=9fd54845 difficulty=47.45232694 height=233426 trust=1151829224594332211 blocktrust=203809302222 date=12/02/14 09:11:44
2014-12-02 10:21:21 NotBestChain: hash=942b65d2 difficulty=38.31554619 height=233427 trust=1151829389160861097 blocktrust=164566528886 date=12/02/14 09:12:32
2014-12-02 10:21:37 NotBestChain: hash=7656e35d difficulty=30.92521488 height=233428 trust=1151829521985674393 blocktrust=132824813296 date=12/02/14 09:12:48
2014-12-02 10:21:53 NotBestChain: hash=9abc73b7 difficulty=24.97069356 height=233429 trust=1151829629235623099 blocktrust=107249948706 date=12/02/14 09:13:04
2014-12-02 10:22:09 NotBestChain: hash=f7b5fc73 difficulty=20.17938611 height=233430 trust=1151829715906749004 blocktrust=86671125905 date=12/02/14 09:13:20
2014-12-02 10:22:26 NotBestChain: hash=4bb28039 difficulty=16.30742044 height=233431 trust=1151829785947655228 blocktrust=70040906224 date=12/02/14 09:13:36
2014-12-02 10:22:43 NotBestChain: hash=341c2353 difficulty=13.17840016 height=233432 trust=1151829842549316602 blocktrust=56601661374 date=12/02/14 09:13:52
2014-12-02 10:22:57 NotBestChain: hash=806aae7c difficulty=10.65860244 height=233433 trust=1151829888328364039 blocktrust=45779047437 date=12/02/14 09:14:08
2014-12-02 10:23:14 NotBestChain: hash=57333068 difficulty=8.62060709 height=233434 trust=1151829925354154518 blocktrust=37025790479 date=12/02/14 09:14:24
2014-12-02 10:23:32 NotBestChain: hash=c2f582ca difficulty=6.97228948 height=233435 trust=1151829955300366747 blocktrust=29946212229 date=12/02/14 09:14:40
2014-12-02 10:24:05 NotBestChain: hash=583b0db3 difficulty=5.64147986 height=233436 trust=1151829979530707952 blocktrust=24230341205 date=12/02/14 09:15:12
2014-12-02 10:24:22 NotBestChain: hash=f9d16850 difficulty=4.56468346 height=233437 trust=1151829999136173297 blocktrust=19605465345 date=12/02/14 09:15:28
2014-12-02 10:24:37 NotBestChain: hash=ef858c0a difficulty=3.69341643 height=233438 trust=1151830014999518112 blocktrust=15863344815 date=12/02/14 09:15:44
2014-12-02 10:24:55 NotBestChain: hash=1f2bfbbd difficulty=2.98968958 height=233439 trust=1151830027840333029 blocktrust=12840814917 date=12/02/14 09:16:00
2014-12-02 10:25:09 NotBestChain: hash=611c038e difficulty=2.42105295 height=233440 trust=1151830038238834942 blocktrust=10398501913 date=12/02/14 09:16:16
2014-12-02 10:25:26 NotBestChain: hash=a62a66b9 difficulty=1.96142105 height=233441 trust=1151830046663202735 blocktrust=8424367793 date=12/02/14 09:16:32
2014-12-02 10:25:42 NotBestChain: hash=3edf771f difficulty=1.58903545 height=233442 trust=1151830053488162162 blocktrust=6824959427 date=12/02/14 09:16:48
2014-12-02 10:25:59 NotBestChain: hash=1860fe48 difficulty=1.28734752 height=233443 trust=1151830059017362010 blocktrust=5529199848 date=12/02/14 09:17:04
2014-12-02 10:26:16 NotBestChain: hash=271fa9a1 difficulty=1.04380027 height=233444 trust=1151830063500518444 blocktrust=4483156434 date=12/02/14 09:17:20
2014-12-02 10:26:32 NotBestChain: hash=593232e3 difficulty=0.84633365 height=233445 trust=1151830067135549266 blocktrust=3635030822 date=12/02/14 09:17:36
2014-12-02 10:26:51 NotBestChain: hash=fb8a8a3f difficulty=0.68650353 height=233446 trust=1151830070084104468 blocktrust=2948555202 date=12/02/14 09:17:52
2014-12-02 10:27:04 NotBestChain: hash=898065e3 difficulty=0.55709040 height=233447 trust=1151830072476826009 blocktrust=2392721541 date=12/02/14 09:18:08
2014-12-02 10:27:21 NotBestChain: hash=b993cc43 difficulty=0.45207152 height=233448 trust=1151830074418488031 blocktrust=1941662022 date=12/02/14 09:18:24
2014-12-02 10:27:38 NotBestChain: hash=2176b4c8 difficulty=0.36685102 height=233449 trust=1151830075994125208 blocktrust=1575637177 date=12/02/14 09:18:40
2014-12-02 10:27:56 NotBestChain: hash=67d5b9ea difficulty=0.29781868 height=233450 trust=1151830077273266206 blocktrust=1279140998 date=12/02/14 09:18:56
2014-12-02 10:28:12 NotBestChain: hash=ff011c32 difficulty=0.24187744 height=233451 trust=1151830078312137764 blocktrust=1038871558 date=12/02/14 09:19:12
2014-12-02 10:28:29 NotBestChain: hash=e4eb2cc2 difficulty=0.19652560 height=233452 trust=1151830079156221684 blocktrust=844083920 date=12/02/14 09:19:28
2014-12-02 10:28:44 NotBestChain: hash=ebd87965 difficulty=0.15974367 height=233453 trust=1151830079842325987 blocktrust=686104303 date=12/02/14 09:19:44
2014-12-02 10:29:01 NotBestChain: hash=b06aec1c difficulty=0.12990012 height=233454 trust=1151830080400251265 blocktrust=557925278 date=12/02/14 09:20:00
2014-12-02 10:29:17 NotBestChain: hash=c478d69b difficulty=0.10563193 height=233455 trust=1151830080853943872 blocktrust=453692607 date=12/02/14 09:20:16
2014-12-02 10:29:33 NotBestChain: hash=0fab0734 difficulty=0.08593345 height=233456 trust=1151830081223030876 blocktrust=369087004 date=12/02/14 09:20:32

Notice how the date on the blocks is more than an hour behind the actual time. This guy's clock was off by so much that the wallet refused to correct it, so he was rejecting all the valid blocks and effectively "solo-staking". This meant he saw very few blocks being staked, and so the difficulty dropped drastically, then overshot, leaving him solo-staking a new block every 16 seconds.

Since the "best chain" is the most trusted one, and trust is based on something like the sum of the difficulties, this rogue forked chain doesn't pose a threat. It might end up longer than the main chain, but it won't have anywhere near as much total trust.

Edit: the peer with the bad clock is coming from this ISP:

OrgName: Net3 Inc.
Address: 8195 Sheridan Drive
City: Buffalo
StateProv: NY
PostalCode: 14221
Country: US

If that's you, fix your clock!

paulc010

member

Activity: 92

Merit: 10

Interesting article on the ethereum blog regarding proof of stake.

CLAM on!

SuperClam

hero member

Activity: 784

Merit: 1002

CLAM Developer

Quote from: romerun on December 01, 2014, 02:13:26 AM

didn't upgrade clam for a while, it crashed at some points. Today I updated and it appears to get stuck at block 173217.
Should I go head to remove all the blocks and rerun ? or there's a better way.

dooglus' recommendation, as usual, is accurate. We are so far past the fork that it may be wise to just load the bootstrap file if you aren't willing to wait for it all to sync. Regardless, you likely have a wealth of blocks that are not valid -> a re-sync or bootstrap resync is definitely in order.

If you continue to have problems, please feel free to step into #clams at freenode irc and say Hi, asking for help

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: romerun on December 01, 2014, 02:13:26 AM

didn't upgrade clam for a while, it crashed at some points. Today I updated and it appears to get stuck at block 173217.

Should I go head to remove all the blocks and rerun ? or there's a better way.

See https://bitcointalksearch.org/topic/m.9365391 for a recent bootstrap.dat.

Edit: but maybe wait a day or two for the new client version before using it.

Edit2: here's a more recent post about the bootstrap.dat file, in case the old date on the above post put you off:

Quote from: dooglus on November 21, 2014, 06:52:30 PM

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:

Quote from: dooglus on October 29, 2014, 01:27:24 AM

Quote from: dooglus on October 29, 2014, 12:52:28 AM

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.

Quote from: dooglus on October 29, 2014, 01:05:38 AM

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.

romerun

legendary

Activity: 1078

Merit: 1002

Bitcoin is new, makes sense to hodl.

didn't upgrade clam for a while, it crashed at some points. Today I updated and it appears to get stuck at block 173217.

Should I go head to remove all the blocks and rerun ? or there's a better way.

garthkiser

full member

Activity: 176

Merit: 100

Quote from: almightyruler on November 28, 2014, 10:57:36 PM

Could a list of nodes be added to the website?

Are we still having problems with nodes hitting their connection cap and refusing connections from new clients?

Indeed, the website needs a tech support section to address common problems. Dooglus' node list is here: http://clamclient.com/#/node-list/

A general FAQ help page is being built here: http://clamclient.com/#/support/

So what should be in the FAQ help section?
- clock syncing issues
- guides will be added for digging distribution CLAMs.
- ???help me help you???

LLTGC

almightyruler

legendary

Activity: 2268

Merit: 1092

Could a list of nodes be added to the website?

Are we still having problems with nodes hitting their connection cap and refusing connections from new clients?

xploited

sr. member

Activity: 304

Merit: 252

CLAM Dev

Quote from: ymod123 on November 28, 2014, 09:19:42 PM

whats the right block now?

http://khashier.com/ will always tell you

ymod123

sr. member

Activity: 432

Merit: 250

Quote from: dooglus on November 28, 2014, 07:47:19 PM

I merged in some more:

Code:

addnode=104.131.59.43
addnode=109.195.211.62
addnode=173.31.55.8
addnode=46.5.84.204
addnode=54.75.227.85
addnode=66.30.80.136
addnode=73.172.149.95
addnode=73.55.207.245
addnode=74.207.230.61
addnode=76.94.201.185
addnode=80.195.253.183
addnode=84.194.247.232
addnode=93.103.131.59
addnode=96.246.211.120

whats the right block now?

dooglus

legendary

Activity: 2940

Merit: 1333

I merged in some more:

Code:

addnode=104.131.59.43
addnode=109.195.211.62
addnode=173.31.55.8
addnode=46.5.84.204
addnode=54.75.227.85
addnode=66.30.80.136
addnode=73.172.149.95
addnode=73.55.207.245
addnode=74.207.230.61
addnode=76.94.201.185
addnode=80.195.253.183
addnode=84.194.247.232
addnode=93.103.131.59
addnode=96.246.211.120

xploited

sr. member

Activity: 304

Merit: 252

CLAM Dev

Quote from: RENDERING on November 28, 2014, 07:17:00 PM

Quote from: ButtCrack on November 28, 2014, 07:05:00 PM

Quote from: LuckyAlt on November 28, 2014, 06:52:26 PM

I need some nodes, my win wallet still will not sync after being opened for 6 days!!!

"addr" : "74.207.230.61:31174",
"addr" : "76.94.201.185:31174",
"addr" : "54.75.227.85:31174",
"addr" : "66.30.80.136:31174",
"addr" : "73.55.207.245:31174",
"addr" : "93.103.131.59:31174",
"addr" : "109.195.211.62:31174",
"addr" : "80.195.253.183:31174",

Thanks, let me fix that for you. :0

Code:

addnode=74.207.230.61
addnode=76.94.201.185
addnode=54.75.227.85
addnode=66.30.80.136
addnode=73.55.207.245
addnode=93.103.131.59
addnode=109.195.211.62
addnode=80.195.253.183

Dev please add this to your main page post, it will save a lot of headaches!

Yes it will, I'll get SuperClam to put it there ASAP. I'm also updating the node list for the new release which will be along VERY shortly. Theres a bunch of fixes going into this one so want to make sure its perfect.

Included updates to the networking itself

RENDERING

sr. member

Activity: 353

Merit: 250

Quote from: ButtCrack on November 28, 2014, 07:05:00 PM

Quote from: LuckyAlt on November 28, 2014, 06:52:26 PM

I need some nodes, my win wallet still will not sync after being opened for 6 days!!!

"addr" : "74.207.230.61:31174",
"addr" : "76.94.201.185:31174",
"addr" : "54.75.227.85:31174",
"addr" : "66.30.80.136:31174",
"addr" : "73.55.207.245:31174",
"addr" : "93.103.131.59:31174",
"addr" : "109.195.211.62:31174",
"addr" : "80.195.253.183:31174",

Thanks, let me fix that for you. :0

Code:

addnode=74.207.230.61
addnode=76.94.201.185
addnode=54.75.227.85
addnode=66.30.80.136
addnode=73.55.207.245
addnode=93.103.131.59
addnode=109.195.211.62
addnode=80.195.253.183

Dev please add this to your main page post, it will save a lot of headaches!

ButtCrack

sr. member

Activity: 432

Merit: 250

Quote from: LuckyAlt on November 28, 2014, 06:52:26 PM

I need some nodes, my win wallet still will not sync after being opened for 6 days!!!

"addr" : "74.207.230.61:31174",
"addr" : "76.94.201.185:31174",
"addr" : "54.75.227.85:31174",
"addr" : "66.30.80.136:31174",
"addr" : "73.55.207.245:31174",
"addr" : "93.103.131.59:31174",
"addr" : "109.195.211.62:31174",
"addr" : "80.195.253.183:31174",

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