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

Note that you only need to install clamd, and don't need to let it sync any of the blockchain. The script provided by Just-Dice contains all the information the offline machine needs to sign a transaction that digs your CLAMs. You can make a virtual machine on the offline machine, install clamd in there, then blow it away after you've signed the message. Or just boot into a Linux LiveCD environment that can't even write to the hdd. There are plenty of ways of safely doing this without needing to worry about a malicious clamd doing any damage.

I guess you still need to trust that a malicious clamd and the pushtx page aren't working together, such that the clamd creates what looks like a signed tx, but actually has your private key appended, and the pushtx page strips off the private key before broadcasting the transaction. That would be a way of stealing your private key - unless you tried decoding the transaction by hand to check that it didn't have anything extra in it.

I guess what it comes down to is that you can't 100% trust software you didn't examine thoroughly.

Still having problems with ORPHAN BLOCK 751

I think I've figured out what has happened this time. The client accepted block 516305, but seems to have completely ignored block 516306... and only that block. Subsequent blocks were received, but have been marked as orphans, since there is the gap between 516305 and 516307.

SetBestChain: new best=8850af0c8791a1b29ffb871852d37e802918fe2115f4a1488a198bb29d71a6ac  height=516304  trust=45728299117685894742  blocktrust=202424519897173  date=06/18/15 03:27:12
ProcessBlock: ACCEPTED
SetBestChain: new best=e29741fec7fa3884b76d4afa76fcd3f60ae3ada6ecca43dd8e263f4bd8ad2b9b  height=516305  trust=45728501751223256301  blocktrust=202633537361559  date=06/18/15 03:27:44
ProcessBlock: ACCEPTED
ERROR: CheckProofOfStake() : VerifySignature failed on coinstake bee2879550e872894ea688f8d02e0069276e9610fd8007e2997e53cedcb66ead
ProcessBlock: ORPHAN BLOCK 5, prev=009d1a341e28bb890481b0fd3381455372134942b748f1905c6d0cf9eb3dc211  <-- this points to block 516306, which hasn't been accepted!!
ProcessBlock: ORPHAN BLOCK 6, prev=0844844a172027d3ec74dc24ab61b87dc8cbb4aea9bbf55bb84aecb01c549f3a
ProcessBlock: ORPHAN BLOCK 7, prev=46b8f1a83e0c918a70325e8ec8f5356e43327bda3874dfba2edf805a141b26ae
ProcessBlock: ORPHAN BLOCK 8, prev=5b2f49ba9d4a618b209b795e0fd2af537a4a130a4cc49269dc507833ec6a9ae1
ProcessBlock: ORPHAN BLOCK 9, prev=e7fce98d440a2e9692236826b30228380251cdd6ccd0733092af3ea9457a0192
ProcessBlock: ORPHAN BLOCK 10, prev=e04ff93bf7348311079e22e6f867eeb0048f1febddfe470498acf22316b576e1
ProcessBlock: ORPHAN BLOCK 11, prev=d5818ffeab30732739d8f9e8a4f30ad683d7b8a7d952da8593591077c4aa5e3f

- Block 516305 is in the chain, but the forward link is broken.
- Block 516306 does not appear to be known about by the client.
- Block 516307 links back to block 516306, and here the reverse link is broken. There's a chain of 700+ blocks extending from 516307, but since it cannot be linked to the main chain, they are all considered orphans.

I've restarted the client several times, including with -rescan, but it's still stuck at 516305. The "ORPHAN BLOCK" count is slowly climbing, and will reach 751 in less than an hour. I guess at that point it will discard any further blocks offered by peers.

Any ideas on how I can force the client to request and properly process that block? This is an ARM CPU so I'd rather not spend another 2 days syncing from scratch.

Hopefully this will also give some hints on what is causing the ORPHAN BLOCK 751 problem.

edit: looks like this may be the cause...

ERROR: CheckProofOfStake() : VerifySignature failed on coinstake bee2879550e872894ea688f8d02e0069276e9610fd8007e2997e53cedcb66ead

I checked on a fully synced client, and this transaction appears in... dun, dun, DUN: block 516306.

edit 2: now stuck in the 751 orphan block loop, where the client repeatedly requests the same set of blocks (perhaps because it's not storing them locally?). No other choice but to close the client right now.

Alas, it's just 1.  Anyway, thanks for the clarification

That's very cool, Doog.  I'm glad I can grab those 4 clams without broadcasting a private key.  However, this means I have to install clamd.  I'm not complaining (this is a very nice option), but I may not act on this at the moment either (laziness).  I'm surprised no one dropped the current price of a clam in BTC on me.  ha!

It actually isn't decentralized at the moment.

Dooglus has way over 51% of the staking power and I believe it will continue to grow until about 90-95% unless someone makes a service that can compete with the daily returns.

I think Doog having the right to veto at this point is a good thing.

With PoS you kind of elect who you want to trust directly with your wealth & the person elected chooses it by accepting over 51% of the staking network... Kinda cool. 

If CLAMS really wanted to be decentralized so that all this pressure was off Just-dice the service for Clamcoin... I think it would be wise to cap invest at JD and set up a simple code on the site that allows more CLAMS to be invested as the money supply grows.  This would:

A:  Decentralize CLAMS through force rather than hope.  The first few cracks at it where in the hope of people divesting to do the "right" thing (leverage system.)
B:  Takes the keys out of any one mans hand.  Doog has already given plenty of keys back to people and I have faith he will continue.
C:  Unnecessary pressure on Just-Dice. 
D:  Encourage people to get people to dig their CLAMS.  More digs = more room to squeeze into Just-Dice invested.
E:  Dooglus keeps his right to veto, but through consensus.  If he needed the ban hammer Doog could just open up the deposit button.
F:  Encourage chat trade.  This may or may not be a good thing, but I always enjoyed the hustled and it would be funny to see the market determine what it was worth! "You got CLAM CLAMS or JD CLAMS?  JD CLAMS trade 50% over spot."

I really don't think this would result as negatively as I thought once upon a time.  After messing around with PoS a little on my own and what not I believe the average crypto user can handle it.  I really do wish there was one exchange that was doing it "right" as far as holding customers coins.

This could also stimulate the development community because Just-Dice is a fucking whale and a half lol... It's orphaning blocks for the little guys and all types of shit.  I'm all for big business... but I can also see the "being fair" part of the distribution side of it.

Services such as Shapeshift.io allow you to pay invoices with CLAM.
There was talk of adding a feature similar to "veribit"; however, if I remember correctly, there was concern about implementing a centralized service in the core wallet (where it likely does not belong).

Currently, the primary usage of CLAM involves gambling, trading and staking.

Brick-and-mortar good merchants are certainly welcome and needed - and we are happy to help with any implementation details.

Brilliant move switching Just-Dice to CLAMs and bringing it back online dooglus. I only wish I'd realized you'd done it sooner so I could have tried to invest in some of the bankroll at an earlier point in time.

I know CLAMs is a decentralized currency, however, in a way it is sort of hanging in the fate of Just-Dice, in my opinion. If for some reason JD was ever shut down and could no longer operate on CLAMs, I think this would deal a heavy blow to the currency. I would think some merchant support starting early and growing could balance out any negative effects in the future if for some reason JD went down. Which, I don't see any reason this would happen, just thinking ahead. Do any merchants accept CLAMs for payment?

There's only the 4.6 level. I guess he means if it's only one address maybe it's not worth it, but if it's 100 addresses it is...

You don't have to give away the private key. I recently added a command to Just-Dice that will allow you to 'dig' your CLAM by signing a transaction on an offline machine.

For example, if I type this in the chat box:


It tells me:


ie. it gives me a command that I can run on an offline machine that will sign a transaction that (when broadcast) sends the dug up CLAMs to an address of my choosing.

For more information, see this post that I made when I first implemented the command.

here you go. i will make sig better. just wanted to bump thread and get credit


JD user 993427 CBI INDEX

thanks

Well the why not is that it's an address I was using for cold-storage and since I don't want to keep my savings in an address that I've given away the private key for then I'd have to first move the coins that are there.  I'd do it if CLAM is high, but not worth the trouble if CLAM is low.  But hey, I thought all the addys that were funded were funded at the 4.6 level.  What other level is there?

why not dig it? idk about selling though, price has been stable and unless you need the money right away could very well be higher at some point. on the other hand if it's only the 4.6 it might not be worth your trouble to keep. in any case, dig away we need more clams

Heya clammers!  How's the CLAM price in BTC these days?  I've still got one more address which I'm sure was funded and which I haven't dug yet, wondering if it's time for me to move   I know you guys have the scoop.

   Your either on a VERY slow computer, or your doing something wrong.  The bootstrap.dat should bring you up to some time in May or early June. 
Did you put the bootstrap.dat file in your clams roaming folder?

Strange, i didn't do anything special....and i'm on a mac

mines been synching for 3 nights already and im only up to 30th Dec 2014.

neither the additional nodes nor the bootstrap.dat made a noticeable difference.

Mine was ready within a few hours and that was two days ago.

oooh, 9 hr download .dat file

only 6h to go.. until i can start synching again...

dooglus provides a bootstrap file, which should be linked in the OP post.  This can speed up sync time considerably.

I will look to update the peer list in the OP post as well - it has been some time.

If you look in your debug and notice any connect block or orphan issues, these can sometimes be resolved with a simple restart of the client.

Specific problems with accompanying debug information should be reported at the repository, here: https://github.com/nochowderforyou/clams/issues

god damn this is the slowest synching client ever!

You can build it from source or use a binary from the OP.

i installed clam client and it is working on my localhost , now how to install that on my centos linux server any help ?