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

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: casinobitco on July 25, 2015, 07:00:14 AM

Thanks doog!

Quote from: dooglus on July 25, 2015, 04:48:52 AM

Quote from: casinobitco on July 19, 2015, 03:40:17 PM

Thanks Doog - We'll keep an eye out for a fix, then it should be pretty easy for us to integrate into PeerBet!

Quote from: dooglus on July 16, 2015, 02:39:05 PM

I opened a github issue about this: https://github.com/nochowderforyou/clams/issues/202

I fixed the issue today and made a new release:

https://github.com/nochowderforyou/clams/releases/tag/v1.4.15

I'm guessing that official binaries will be linked from the OP soon.

I uploaded binaries here: https://github.com/nochowderforyou/clams/releases/tag/v1.4.15

I don't know how to make OSX binaries with access to a Mac, so I only made Linux and Windows binaries.

Edit: xploited uploaded an OSX binary there too.

brettbarth

newbie

Activity: 24

Merit: 0

I added clamcoin last night to my staking portfolio. Are there any tweaks I need to do to the wallet or is it a "set it and forget it" stake coin?

Any help is greatly appreciated.

-Brett

Cyrax89721

sr. member

Activity: 321

Merit: 250

I visited Dooglus' new www.clamaddress.org site and printed & laminated myself a paper wallet.

Looks sexy.

GordoZ

full member

Activity: 145

Merit: 110

Hi. I wold like to invite you to see a Counterparty asset based on CLAM distribution. XCLAM.
https://bitcointalksearch.org/topic/ann-xclams-counterparty-clams-distributed-to-asset-holders-1133581
Thanx for reading! Wink

casinobitco

legendary

Activity: 1833

Merit: 1030

Thanks doog!

Quote from: dooglus on July 25, 2015, 04:48:52 AM

Quote from: casinobitco on July 19, 2015, 03:40:17 PM

Thanks Doog - We'll keep an eye out for a fix, then it should be pretty easy for us to integrate into PeerBet!

Quote from: dooglus on July 16, 2015, 02:39:05 PM

I opened a github issue about this: https://github.com/nochowderforyou/clams/issues/202

I fixed the issue today and made a new release:

https://github.com/nochowderforyou/clams/releases/tag/v1.4.15

I'm guessing that official binaries will be linked from the OP soon.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: casinobitco on July 19, 2015, 03:40:17 PM

Thanks Doog - We'll keep an eye out for a fix, then it should be pretty easy for us to integrate into PeerBet!

Quote from: dooglus on July 16, 2015, 02:39:05 PM

I opened a github issue about this: https://github.com/nochowderforyou/clams/issues/202

I fixed the issue today and made a new release:

https://github.com/nochowderforyou/clams/releases/tag/v1.4.15

I'm guessing that official binaries will be linked from the OP soon.

thefix

legendary

Activity: 1049

Merit: 1001

Quote from: dooglus on July 24, 2015, 06:53:29 PM

Quote from: thefix on July 24, 2015, 06:27:08 PM

Is this talk about a new coin distributed to Clam addresses?

Yes. But there's no reason to believe it will happen.

Bummer, I was picturing Pearlcoin with a chance of finding one in every Clam!

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: thefix on July 24, 2015, 06:27:08 PM

Is this talk about a new coin distributed to Clam addresses?

Yes. But there's no reason to believe it will happen.

thefix

legendary

Activity: 1049

Merit: 1001

Quote from: SuperClam on July 22, 2015, 05:52:49 AM

Quote from: dooglus on July 22, 2015, 12:05:39 AM

Quote from: SuperClam on July 21, 2015, 11:40:54 PM

Quote from: Crestington on July 21, 2015, 04:41:19 PM

Ok thanks for the help, I'll send them a message and see if they may be able to point me in the right direction.

Include the CLAM community into your distribution - and we will go so far as to provide scripts or even do it for you

Before you take the CLAM snapshot give me a second to split the JD staking wallet into 100,000 different addresses...
ftw
Edit: and by that I mean you should make sure the snapshot date is some time before now. Because otherwise people will abuse it.

Or, distribute based proportionally to balance.
Or, alternatively, distribute at a minimum balance that is high enough to make splitting likely negative expected value.

Is this talk about a new coin distributed to Clam addresses?

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: SebastianJu on July 24, 2015, 01:10:43 PM

Oh, is bitaddress.org yours too or did you rip their design only? Tongue

I used bitaddress quite some time already.

No, bitaddress.org isn't mine. It's open-source, so I forked it and made a CLAM version. I also used a small bit from https://bitcoinpaperwallet.com/bitcoinpaperwallet/generate-wallet.html (which itself is based on bitaddress.org) to allow skipping of the entropy collection.

Could this be the first CLAM paper wallet in the world?

He used photoshop to replace the low-resolution image produced by clamaddress.org with a higher resolution version. I wonder how best to allow clamaddress.org to produce print-ready images itself, while still fitting on the screen. Any ideas?

SebastianJu

legendary

Activity: 2674

Merit: 1083

Legendary Escrow Service - Tip Jar in Profile

Oh, is bitaddress.org yours too or did you rip their design only? Tongue

I used bitaddress quite some time already.

Quote from: dooglus on July 23, 2015, 02:00:47 PM

Quote from: dooglus on July 22, 2015, 12:42:32 PM

I forked bitaddress.org and changed it to work with CLAM addresses:
https://github.com/dooglus/bitaddress.org

I need the graphics updated if anyone has the time and skills required.

It's up at:

https://clamaddress.org

I made some crappy 'art' for the logo and wallets. I'm happy to accept better versions.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: daxxog on July 23, 2015, 11:28:48 AM

Here is some info from my debug.log file that might help. If you want the whole thing I can get that for you too.

Code:

$ cat debug.log | grep ORPHAN > debug_orphans
$ cat debug_orphans | curl -F 'clbin=<-' https://clbin.com
https://clbin.com/FTBHj

I tried syncing from scratch. It worked flawlessly. I only saw 414 orphans in total, so never hit the 750 limit:

$ grep ORPHAN debug.log | wc -l
414

I guess it depends which peer you're downloading from.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: dooglus on July 22, 2015, 12:42:32 PM

I forked bitaddress.org and changed it to work with CLAM addresses:
https://github.com/dooglus/bitaddress.org

I need the graphics updated if anyone has the time and skills required.

It's up at:

https://clamaddress.org

I made some crappy 'art' for the logo and wallets. I'm happy to accept better versions.

daxxog

jr. member

Activity: 42

Merit: 1

Quote from: dooglus on July 23, 2015, 11:17:46 AM

Quote from: daxxog on July 23, 2015, 10:13:17 AM

Quote from: almightyruler on December 11, 2014, 07:22:16 PM

Syncing a virgin db, and clamd seems to be getting "stuck" on orphan blocks...

ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(31c8d98ed4, 1), 1409328810) for orphan block ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8 ProcessBlock: ORPHAN BLOCK 751, prev=ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(4b4c0aacd4, 2), 1409328811) for orphan block e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6 ProcessBlock: ORPHAN BLOCK 751, prev=e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(df96fd5846, 1), 1409328935) for orphan block 331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0 ProcessBlock: ORPHAN BLOCK 751, prev=331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(d93414f7d2, 1), 1409328928) for orphan block f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656 ProcessBlock: ORPHAN BLOCK 751, prev=f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(3f2c6d206d, 1), 1409329004) for orphan block 6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec ProcessBlock: ORPHAN BLOCK 751, prev=6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(7b54b4e3b6, 1), 1409329082) for orphan block a9ad274839def4b39c0d2e8a44fa14f9d15a7665f37f202d1f9ab80edf56fc85 ProcessBlock: ORPHAN BLOCK 751, prev=e8be94c3aa50abd60dbe64dde7b76672b5a97c8d4ec50da9afa9b70dc10f3550 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(770d08c5c8, 1), 1409335177) for orphan block ebb678b09629ae0657500521b73aafd4fa66f441458a14c70380c0ca05eccfbb

At this point it's just a bunch of "ORPHAN BLOCK 751" messages, although the block hashes for each seem to be different. It doesn't seem to be accepting new blocks. Is the client hitting some sort of limit? I have to stop and restart it in order for it to accept more network blocks. Once it hits 751 orphan blocks it gets stuck again. This has happened about 5 times now.

The phrase "ORPHAN BLOCK 751" currently appears 51327 times in my debug log. Now on 6th restart.

Guys I'm getting this same problem. ORPHAN BLOCK 751 and gets stuck. I am running the latest clamd built from the source code on an AWS micro instance (ubuntu).

What version of the source code did you build from?
What block number did it get stuck on?

As a workaround, see https://bitcointalksearch.org/topic/m.9772191 for a bootstrap.dat file that will get you all the blocks. I'll see if I can reproduce and hopefully fix this orphan problem.

I built from commit: 4ce28b171d1674b1c170fe97b2f5ad5683fb5c51.

Here is some info from my debug.log file that might help. If you want the whole thing I can get that for you too.

Code:

$ cat debug.log | grep ORPHAN > debug_orphans
$ cat debug_orphans | curl -F 'clbin=<-' https://clbin.com
https://clbin.com/FTBHj

EDIT: I had to restart clamd whenever it got to 751 loop to fix it. Climbs right back up to 751.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: daxxog on July 23, 2015, 10:13:17 AM

Quote from: almightyruler on December 11, 2014, 07:22:16 PM

Syncing a virgin db, and clamd seems to be getting "stuck" on orphan blocks...

ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(31c8d98ed4, 1), 1409328810) for orphan block ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8 ProcessBlock: ORPHAN BLOCK 751, prev=ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(4b4c0aacd4, 2), 1409328811) for orphan block e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6 ProcessBlock: ORPHAN BLOCK 751, prev=e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(df96fd5846, 1), 1409328935) for orphan block 331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0 ProcessBlock: ORPHAN BLOCK 751, prev=331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(d93414f7d2, 1), 1409328928) for orphan block f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656 ProcessBlock: ORPHAN BLOCK 751, prev=f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(3f2c6d206d, 1), 1409329004) for orphan block 6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec ProcessBlock: ORPHAN BLOCK 751, prev=6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(7b54b4e3b6, 1), 1409329082) for orphan block a9ad274839def4b39c0d2e8a44fa14f9d15a7665f37f202d1f9ab80edf56fc85 ProcessBlock: ORPHAN BLOCK 751, prev=e8be94c3aa50abd60dbe64dde7b76672b5a97c8d4ec50da9afa9b70dc10f3550 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(770d08c5c8, 1), 1409335177) for orphan block ebb678b09629ae0657500521b73aafd4fa66f441458a14c70380c0ca05eccfbb

At this point it's just a bunch of "ORPHAN BLOCK 751" messages, although the block hashes for each seem to be different. It doesn't seem to be accepting new blocks. Is the client hitting some sort of limit? I have to stop and restart it in order for it to accept more network blocks. Once it hits 751 orphan blocks it gets stuck again. This has happened about 5 times now.

The phrase "ORPHAN BLOCK 751" currently appears 51327 times in my debug log. Now on 6th restart.

Guys I'm getting this same problem. ORPHAN BLOCK 751 and gets stuck. I am running the latest clamd built from the source code on an AWS micro instance (ubuntu).

What version of the source code did you build from?
What block number did it get stuck on?

As a workaround, see https://bitcointalksearch.org/topic/m.9772191 for a bootstrap.dat file that will get you all the blocks. I'll see if I can reproduce and hopefully fix this orphan problem.

daxxog

jr. member

Activity: 42

Merit: 1

Quote from: almightyruler on December 11, 2014, 07:22:16 PM

Syncing a virgin db, and clamd seems to be getting "stuck" on orphan blocks...

ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(31c8d98ed4, 1), 1409328810) for orphan block ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8 ProcessBlock: ORPHAN BLOCK 751, prev=ab81478d442bbc067c091b86ddd81d8c415b7fba4cea652a78f7549a515b70a8 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(4b4c0aacd4, 2), 1409328811) for orphan block e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6 ProcessBlock: ORPHAN BLOCK 751, prev=e9f85e1f3d10894e42aa0982b22e1a1a74d3c22e1847adc2b801fdbd70fea9f6 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(df96fd5846, 1), 1409328935) for orphan block 331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0 ProcessBlock: ORPHAN BLOCK 751, prev=331a1a344def2ff02b76726b37a5ad1cc03af2f9c85b084ba31de073a9cf09f0 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(d93414f7d2, 1), 1409328928) for orphan block f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656 ProcessBlock: ORPHAN BLOCK 751, prev=f09b4a9d0f0d1d060b256805248696fc38ecf9ff26c06119d653af9b3bb7a656 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(3f2c6d206d, 1), 1409329004) for orphan block 6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec ProcessBlock: ORPHAN BLOCK 751, prev=6795a64418eb9b18880e4d7ec125552be3ff73d8f9de7f825ebc311d276d02ec ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(7b54b4e3b6, 1), 1409329082) for orphan block a9ad274839def4b39c0d2e8a44fa14f9d15a7665f37f202d1f9ab80edf56fc85 ProcessBlock: ORPHAN BLOCK 751, prev=e8be94c3aa50abd60dbe64dde7b76672b5a97c8d4ec50da9afa9b70dc10f3550 ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(770d08c5c8, 1), 1409335177) for orphan block ebb678b09629ae0657500521b73aafd4fa66f441458a14c70380c0ca05eccfbb

At this point it's just a bunch of "ORPHAN BLOCK 751" messages, although the block hashes for each seem to be different. It doesn't seem to be accepting new blocks. Is the client hitting some sort of limit? I have to stop and restart it in order for it to accept more network blocks. Once it hits 751 orphan blocks it gets stuck again. This has happened about 5 times now.

The phrase "ORPHAN BLOCK 751" currently appears 51327 times in my debug log. Now on 6th restart.

Guys I'm getting this same problem. ORPHAN BLOCK 751 and gets stuck. I am running the latest clamd built from the source code on an AWS micro instance (ubuntu).

daxxog

jr. member

Activity: 42

Merit: 1

I built a simple RPC client for clamd. Untested alpha version.

https://github.com/daxxog/clam-rpc

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: dooglus on July 22, 2015, 09:59:35 AM

bitaddress.org's 'vanity wallet' tab does all the hard work for Bitcoin addresses, but I don't know of a CLAM version. Maybe I should host one...

That's a good idea!

I forked bitaddress.org and changed it to work with CLAM addresses:
https://github.com/dooglus/bitaddress.org

I need the graphics updated if anyone has the time and skills required. There are 3 images: the logo, the paper wallet for encrypted keys, and the paper wallet for unencrypted keys.

logo:

unencrypted wallet:

encrypted wallet:

The wallets have the address, privkey, and QR codes printed over them like this:

so it's best to leave the design clear in those spots.

I think it would be best to keep all the images the same size they currently are so as not to mess with the site's layout. PNG format please.

Edit: it was pointed out to me that http://www.bitcointrading.com/files/btcaddress-alpha.zip could be useful. It contains bigger versions of the BTC images. It also contains .exe and .dll files, so be careful!

Edit2: DNS is taking forever to update, so in the meantime: https://just-dice.com/clamaddress

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: 15263524 on July 22, 2015, 12:19:14 PM

Is there any way to check how many of your clams are currently staking?

Go to the Console (last entry in the list down the left hand side). Type "getstakinginfo" (without the quotes). Hit return. The reported "weight" is the number of CLAMs currently trying to stake:

I have none in this wallet.

15263524

newbie

Activity: 1

Merit: 0

Is there any way to check how many of your clams are currently staking?

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