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

Arauco

newbie

Activity: 4

Merit: 0

Thank you very much Dooglus, much appreciated.
My problem is solved.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: Arauco on June 03, 2015, 12:10:11 PM

Hello Clams,
I installed the Clam client.
I transfered some coins from Poloniex to my new wallet, everything fine.
I made a backup of my wallet on a pen drive.
I installed Clam client on a second computer.
I tried to import my wallet.dat on the second computer.
It doesn't work, I get the message: Error parsing wallet.dat.
What do I wrong, can anybody help me please???
I just want to be sure not to loose my coins in case of a computer crash.
Both computers are mac osx.
Thank you

How did you make the backup?

You shouldn't copy wallet.dat while the wallet is running.

You should either:

1) shut down the wallet, make sure it has fully stopped, then copy the wallet.dat
2) pick 'backup wallet' from the file menu (or wherever it has moved to now) inside the Qt wallet
3) use "clamd backupwallet" to make a backup

I'm guessing that you may have just copied the wallet.dat file while it was in use. That is liable to give you a corrupted wallet.dat file.

Note also that it's not really OK to run the same wallet.dat on two different computers. It's OK if all you are doing is checking to see if the pen drive backup is working, but if you want to run two wallets, you should use two completely separate wallets. Otherwise you'll run into problems once the first 100 addresses in the keypool have been used up, since the two copies will generate different addresses after those first 100. You'll start seeing different balances on the two machines because they have different ideas of which "change" addresses they each own.

Arauco

newbie

Activity: 4

Merit: 0

Hello Clams,
I installed the Clam client.
I transfered some coins from Poloniex to my new wallet, everything fine.
I made a backup of my wallet on a pen drive.
I installed Clam client on a second computer.
I tried to import my wallet.dat on the second computer.
It doesn't work, I get the message: Error parsing wallet.dat.
What do I wrong, can anybody help me please???
I just want to be sure not to loose my coins in case of a computer crash.
Both computers are mac osx.
Thank you

madmartyk

legendary

Activity: 2702

Merit: 1030

Yes I am a pirate, 300 years too late!

Quote from: garthkiser on June 03, 2015, 08:19:30 AM

Quote from: SuperClam on June 03, 2015, 04:52:54 AM

Quote from: dooglus on June 03, 2015, 02:03:52 AM

Are you a witch or something? That's uncanny...

No.
You are nothing, if not thorough and detail oriented.
You are just predictably driven to such mathematical wizardry. (Thankfully Wink

)

In other news, dooglus was turned into a frog today. CLAM bounty will be paid to the princess who kisses him.

SMOOCH!!!!

garthkiser

full member

Activity: 176

Merit: 100

Quote from: SuperClam on June 03, 2015, 04:52:54 AM

Quote from: dooglus on June 03, 2015, 02:03:52 AM

Are you a witch or something? That's uncanny...

No.
You are nothing, if not thorough and detail oriented.
You are just predictably driven to such mathematical wizardry. (Thankfully Wink

)

In other news, dooglus was turned into a frog today. CLAM bounty will be paid to the princess who kisses him.

hcf27

full member

Activity: 257

Merit: 100

Quote from: dooglus on June 03, 2015, 02:03:52 AM

Quote from: SuperClam on June 02, 2015, 10:10:27 PM

CLAM is not % based. dooglus will likely chime in shortly on what one might expect for a "percentage" return, but this return is entirely dependent on difficulty and other factors.

Are you a witch or something? That's uncanny...

Anyway.

Just-Dice has 513k CLAMs and stakes about 1200 times per day:

>>> 1200 / 513e3 * 100
0.23391812865497078

So that's 0.234% per day. (JD investors pay 10% commission on staking rewards, so should get ~0.21%)

You can expect the same, but with higher variance.

And the rate will decline over time, since the global rate is a constant (1 per minute) but the total active staking money supply is growing.

Thanks a lot, will be bought some coins at polo, i am ready to try this out

SuperClam

hero member

Activity: 784

Merit: 1002

CLAM Developer

Quote from: dooglus on June 03, 2015, 02:03:52 AM

Quote from: SuperClam on June 02, 2015, 10:10:27 PM

CLAM is not % based. dooglus will likely chime in shortly on what one might expect for a "percentage" return, but this return is entirely dependent on difficulty and other factors.

Are you a witch or something? That's uncanny...

No.
You are nothing, if not thorough and detail oriented.
You are just predictably driven to such mathematical wizardry. (Thankfully Wink

)

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: enervist on June 03, 2015, 02:54:22 AM

is there a way to participate in JD's staking power without being exposed to the investment risk from gambling?

There's no way of being exposed to no risk, but by default you are exposed to very little risk.

See the FAQ about "offsite investing". Many investors use that feature to increase their risk (and in so doing, to reduce yours).

enervist

newbie

Activity: 14

Merit: 0

Quote from: dooglus on June 03, 2015, 02:03:52 AM

Quote from: SuperClam on June 02, 2015, 10:10:27 PM

CLAM is not % based. dooglus will likely chime in shortly on what one might expect for a "percentage" return, but this return is entirely dependent on difficulty and other factors.

Are you a witch or something? That's uncanny...

Anyway.

Just-Dice has 513k CLAMs and stakes about 1200 times per day:

>>> 1200 / 513e3 * 100
0.23391812865497078

So that's 0.234% per day. (JD investors pay 10% commission on staking rewards, so should get ~0.21%)

You can expect the same, but with higher variance.

And the rate will decline over time, since the global rate is a constant (1 per minute) but the total active staking money supply is growing.

is there a way to participate in JD's staking power without being exposed to the investment risk from gambling?

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: SuperClam on June 02, 2015, 10:10:27 PM

CLAM is not % based. dooglus will likely chime in shortly on what one might expect for a "percentage" return, but this return is entirely dependent on difficulty and other factors.

Are you a witch or something? That's uncanny...

Anyway.

Just-Dice has 513k CLAMs and stakes about 1200 times per day:

>>> 1200 / 513e3 * 100
0.23391812865497078

So that's 0.234% per day. (JD investors pay 10% commission on staking rewards, so should get ~0.21%)

You can expect the same, but with higher variance.

And the rate will decline over time, since the global rate is a constant (1 per minute) but the total active staking money supply is growing.

SuperClam

hero member

Activity: 784

Merit: 1002

CLAM Developer

Quote from: hcf27 on June 02, 2015, 10:05:08 PM

Hey, I am new to clams... wanted to know how to stake, do I just download the client and leave my wallet open... is there a minimum of coins I need to have?... what is the yearly % for staking clams?

There is no minimum, though smaller outputs(piles) will have harder time of staking regularly than larger piles. Alternatively, a smaller number of piles will have a smaller chance of staking than a larger number of piles, assuming the same total balance.

CLAM is not % based. dooglus will likely chime in shortly on what one might expect for a "percentage" return, but this return is entirely dependent on difficulty and other factors. CLAM operates very similar to the way one might mine a Proof-Of-Work crypto. The primary difference is that you use your outputs(piles) to create hashes instead of a mining rig.

The reward per block, regardless of how big or small the piles staking it is, is 1 CLAM per block.
The network adjusts to target 1 block per minute.

hcf27

full member

Activity: 257

Merit: 100

Hey, I am new to clams... wanted to know how to stake, do I just download the client and leave my wallet open... is there a minimum of coins I need to have?... what is the yearly % for staking clams?

SuperClam

hero member

Activity: 784

Merit: 1002

CLAM Developer

CLAMs has been added to the Margin Trading platform at Poloniex!

https://poloniex.com/marginTrading#btc_clam

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: NeedIfFindIt on June 02, 2015, 01:49:57 AM

Quote from: almightyruler on June 01, 2015, 01:38:22 AM

edit: Tried connect=x.x.x.x to tie to a single peer, but it doesn't seem to have helped. After an hour, the block count has not advanced at all. Sad

In 14-15 hours it has only advanced about 80 to 100 blocks.

Try maxconnections=3 if it does not work then try maxconnections=2 ... maxconnections=1 if it does not work then try http://www.memtest.org/

I've already done that. connect=x.x.x.x is effectively the same as maxconnections=1

I doubt it's anything to do with faulty memory. It seems to be related to not being able to properly link the last known block with new ones that peers are offering.

NeedIfFindIt

full member

Activity: 500

Merit: 100

almightyruler

legendary

Activity: 2268

Merit: 1092

New machine, new client (cloned from github a couple of weeks ago), still experiencing the ORPHAN BLOCK 751 problem. Sad

The client was off for a day or two, and was about 2500 blocks behind when restarted. It's been running for over 12 hours and it still hasn't synced.

debug.log is full of this sort of thing:

ERROR: ProcessBlock() : already have block (orphan) 3bfbb14d04d3233ad92f435fcebe5ae4410b8204379cfea95386f5c841f1aaca ProcessBlock: ORPHAN BLOCK 751, prev=2df7670737bede346ea3db14d4dffd3593eefe7f420dfa322fd3961c5adbfb59 ProcessBlock: ORPHAN BLOCK 751, prev=8950cb42743e3e662559b5194eb2d9c184acc962b84edeed936a5b41495a81f1 ProcessBlock: ORPHAN BLOCK 751, prev=ea350579a7263b93dfb48dd0ddbb6feb0920f760c08c2a03923c9c4dca38d75d ProcessBlock: ORPHAN BLOCK 751, prev=31ed0a21473469cc8432674cd0e0adc6d5ffa7df07073619327c0f167dfd4393 ProcessBlock: ORPHAN BLOCK 751, prev=7f855e7d8e2966c52708ebe19dbfb33e540163789b5cc13fa0e6a1ec9ad79ab6 ERROR: ProcessBlock() : already have block (orphan) 95b62c19857cb6965a1dcb00c2b7ca051d6b2aa13d9533f8014a0ab541997561 ProcessBlock: ORPHAN BLOCK 751, prev=b8aa10a04aa0936ff48a2c5ff8afe2e9e22413a58fe37d7f1da9fc9fc9c7751a ERROR: ProcessBlock() : already have block (orphan) 915a4c8b1e1a66549b1aa8685c1f275e99b4f997abdbf5ddc2a757c8105666ad ProcessBlock: ORPHAN BLOCK 751, prev=9712a237318b877f383561662e6364c372e986486096234e526dba7d278512e2 ProcessBlock: ORPHAN BLOCK 751, prev=a0bd31b2ddf60cc8326bc7c039e089c860145ef27dda3d5f442ba9c82c694228 ProcessBlock: ORPHAN BLOCK 751, prev=96de730164caf6fc2e88f0e25698352cb70651470b2bf1923e0c8c6c43a8f711 ProcessBlock: ORPHAN BLOCK 751, prev=d43ff39545640744c6dec4c5377db4f3a1735f00ed5ee801030463ef0211ae3e ERROR: ProcessBlock() : already have block (orphan) 8c5df9b0a99e4e4cdff6fbe2a598e6d1b305cd204c5733665f945acc45ad6386 ERROR: ProcessBlock() : already have block (orphan) 4f5032c8e9c0630d27eea17e4a3e6c526ff3aa544a8dfb12338f9791c9f94a3b ProcessBlock: ORPHAN BLOCK 751, prev=95b62c19857cb6965a1dcb00c2b7ca051d6b2aa13d9533f8014a0ab541997561 ProcessBlock: ORPHAN BLOCK 751, prev=3cd780252174a199f92364393ccdb7d487f3b72e983a06701b485cd04047d456 ProcessBlock: ORPHAN BLOCK 751, prev=fea5d0a34197f9fd83e2cec812b20b1b7e31c0e1080f5bb31af53e9f910a1815 ERROR: ProcessBlock() : already have block (orphan) 4349ded7e13ab50188e0fab3125822041e921578713f70471c436ff8729f759e ProcessBlock: ORPHAN BLOCK 751, prev=6429eedc53e33fba83b1da9d5c272421537e474fe28ec54a7409683bf73e0d08 ProcessBlock: ORPHAN BLOCK 751, prev=4f1ddeef5eaba68fe6e1d5dcac951d6dc714aab96272064dc22eedb4bc9bc7c8 ProcessBlock: ORPHAN BLOCK 751, prev=f21e4efeaf3ccddb864e9dc2ac6dd4b504c83ace0d83a2cd54cc386540dba734 ERROR: ProcessBlock() : already have block (orphan) 2150ad9d4725a739a70ab5131d63bc03793af0c4827fe733744cb2c8fd374bf7 ERROR: ProcessBlock() : already have block (orphan) 11f02f8abe0a970780d8a09bd36ecfb98be803a2f9b9724cc2b60a3b24d1b07a ProcessBlock: ORPHAN BLOCK 751, prev=a2f0d4117301caa5b89d44201b637cce36845b3599a88b8e1a559276236b68ec ProcessBlock: ORPHAN BLOCK 751, prev=7fa2587cd2dba701b499c8ec43f21e9f14a0090c4a71e9396a312c0ef4460ea8 ERROR: ProcessBlock() : already have block (orphan) 398b127ace5137d805a99be5391328c0b30edfd0b8635bd124da636eace14280 ProcessBlock: ORPHAN BLOCK 751, prev=3759347ddc78429dc87e71c4974bdfa026a3a66a87674489dab967d6d865610b ProcessBlock: ORPHAN BLOCK 751, prev=c19dde16334c81610b0422bf94a3de9ab56efaced99fb1c814d27adefe2c4379 ProcessBlock: ORPHAN BLOCK 751, prev=66544aa53979b96ee620db3b49cf8f779806cdb7c58e954abf1742a94b9f59f2 ProcessBlock: ORPHAN BLOCK 751, prev=fc24a212b46224796226e08317a70e352a9e64a6382241290787f71cae2b9825 ERROR: ProcessBlock() : already have block (orphan) 253abaea08bbb1780e8650a02ecc1abf40a996bc24bbe9b458477c7e6cda2040 ERROR: ProcessBlock() : already have block (orphan) b5cab51e120e0aae39acbf0d832952b4f664396a6759493c2127a8673f9020bd ERROR: ProcessBlock() : already have block (orphan) 1975ef3df7b8f27c825578d337c61c4ea5771afe7d70be64fbe67cdb89eedcb1 ProcessBlock: ORPHAN BLOCK 751, prev=98dfe9d223da4d46e2f977b2d0789a838c4ae349b4a4770b3338907d79caed4c ProcessBlock: ORPHAN BLOCK 751, prev=cfd6096464e5be31998e71df024dc0c9594cdf20eaa29c200eeb6e4609efe0af ERROR: ProcessBlock() : already have block (orphan) 4dfc0628bfc070054171d8754944947c5fc6fa68997241bde3aceb0a20c3d143 ProcessBlock: ORPHAN BLOCK 751, prev=45abb19a333d89bfda44f843b3bcc09db8e6b5b8489b56a2e5c273030a81c59f ERROR: ProcessBlock() : already have block (orphan) da5acc7d083acb46de7e790a3bbca6f771cc602b354965a0acef1d29faf8ea48 ERROR: ProcessBlock() : already have block (orphan) 52fd2e967a00f81fa21761b6a885bff5114245d41ba3928c5b8345b91d375b56 ProcessBlock: ORPHAN BLOCK 751, prev=de87be6d999160f205b7989adb9035ee9fc4656e40f2e0b851fb7e5ea62acb3f ProcessBlock: ORPHAN BLOCK 751, prev=5c52de11d6aeba3236dd94a5fba79c09de07a43af4199a890d748365f255c84c ERROR: ProcessBlock() : already have block (orphan) 5ade171a63dfbdcdf2f3d8e9a592c7d442d92cdc7a0ea3265e27a96b0a6d4c2a

Seems to be caught in a loop - the string (for example) "5ade171a63dfbdcdf2f3d8e9a592c7d442d92cdc7a0ea3265e27a96b0a6d4c2a" (the last block from the above log snippet) appears 88 times in debug.log

Here's my earlier experience with this issue (different machine, different OS) - https://bitcointalksearch.org/topic/m.9812672

And this seems to suggest it's not specific to CLAM - https://bitcointalksearch.org/topic/processblock-orphan-block-in-debuglog-meaning-746840 :::: https://github.com/bitcoin/bitcoin/issues/4353

edit: Tried connect=x.x.x.x to tie to a single peer, but it doesn't seem to have helped. After an hour, the block count has not advanced at all. Sad

In 14-15 hours it has only advanced about 80 to 100 blocks.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: TrevorS on May 31, 2015, 06:42:34 AM

FWIW -- I first tried dropping in the bootstrap w/o deleting the existing blockchain files (was pretty sure I needed to having used a bootstrap once before, but deletion wasn't apparent in the instructions), but it didn't import, just continued normally. So I stopped, deleted the files, restarted, and then it announced it was importing blocks. That may have been what happened with others.

Hmmm. It should import blocks from bootstrap.dat whenever it exists, without having to delete the existing blockchain. I guess it could take a while to get to the new blocks, since it will start at the beginning, and have to skip all the blocks it already has, but it should still work.

Quote from: TrevorS on May 31, 2015, 06:42:34 AM

I think a little more clarity in the instructions would help a lot with this.

OP recently said she needs to tidy up the first post. I'm sure your feedback will be helpful in that regard.

TrevorS

sr. member

Activity: 1050

Merit: 377

Quote from: dooglus on May 30, 2015, 11:10:40 PM

Quote from: TrevorS on May 30, 2015, 07:52:20 PM

Thanks for the follow up! Took near an hour to download the file, but then made a new backup directory (now at "9 weeks behind"), deleted the blockchain associated files, dropped in the bootstrap, and fired off the QT again. Appears to be importing the weeks at a two to three minute clip, a huge improvement. Will update when it's done.

I'm glad to hear it.

Wallet is up and running and reports a total of .000109 of dust thanks to faucets -- a start anyway!

Quote from: dooglus on May 30, 2015, 11:10:40 PM

I see a lot of people complain that "bootstrap.dat doesn't make any difference". I think they must all be doing it wrong somehow, but they rarely stick around long enough for me to help them.

FWIW -- I first tried dropping in the bootstrap w/o deleting the existing blockchain files (was pretty sure I needed to having used a bootstrap once before, but deletion wasn't apparent in the instructions), but it didn't import, just continued normally. So I stopped, deleted the files, restarted, and then it announced it was importing blocks. That may have been what happened with others.

What originally confused me was on page one where the addnodes are listed, I didn't see mention of them being for the .conf file, though seemed to me they had to be and first guessed "clamcoin.conf" (later discovered it should be "clam.conf"), however, just above that was a bootstrap reference, but it struck me as a source for the addnode list (one appearing subsidiary to the other in the page format with no explicit ID), and so I guessed the Clamcoin bootstrap format was the same as the .conf -- and went with the .conf file I'd just made and misnamed.

I think a little more clarity in the instructions would help a lot with this.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: TrevorS on May 30, 2015, 07:52:20 PM

Thanks for the follow up! Took near an hour to download the file, but then made a new backup directory (now at "9 weeks behind"), deleted the blockchain associated files, dropped in the bootstrap, and fired off the QT again. Appears to be importing the weeks at a two to three minute clip, a huge improvement. Will update when it's done.

I'm glad to hear it.

I see a lot of people complain that "bootstrap.dat doesn't make any difference". I think they must all be doing it wrong somehow, but they rarely stick around long enough for me to help them.

TrevorS

sr. member

Activity: 1050

Merit: 377

Thanks for the follow up! Took near an hour to download the file, but then made a new backup directory (now at "9 weeks behind"), deleted the blockchain associated files, dropped in the bootstrap, and fired off the QT again. Appears to be importing the weeks at a two to three minute clip, a huge improvement. Will update when it's done.

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