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

[dy2k]

Have you tried the system file checker? It could be that there's a corrupt cached file somewhere caused by the BSOD?

Code:

sfc /scannow

Tried system file checker and unfortunately it didn't work. Same error and wallet hangs on open.

[1713898265]

1713898265

[1713898265]

1713898265

[Hippie Tech]

Whats up with the client hanging on start up ?

I haven't been able to get it to work since the the BSODs caused by the cpu overclock.

It happened to one of my mining rigs also. Windows 7 crashed and restarted while wallet was staking and now it hangs/crash at open. No even deleting everything and re-installing works. Any one knows whats causing this? I get this error every time I open it.

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:   AppHangB1
  Application Name:   clam-qt.exe
  Application Version:   1.4.2.0
  Application Timestamp:   4d44aa00
  Hang Signature:   f651
  Hang Type:   0
  OS Version:   6.1.7600.2.0.0.256.1
  Locale ID:   1033
  Additional Hang Signature 1:   f651dae909a6f55fbff1657b14800280
  Additional Hang Signature 2:   40fd
  Additional Hang Signature 3:   40fd2af9d902d42e23e9aac756a4be35
  Additional Hang Signature 4:   f651
  Additional Hang Signature 5:   f651dae909a6f55fbff1657b14800280
  Additional Hang Signature 6:   40fd
  Additional Hang Signature 7:   40fd2af9d902d42e23e9aac756a4be35

Are you seeing 5-10% cpu and 100+ mb memory usage while it is starting up ?

Try this :

- uninstall any 2005-2008 Microsoft Visual C++ and related apps
- run a windows error check
- backup the wallet and the .bak, delete the roaming folder and qt
- delete CLAM's registry folder located at HKEY_CURRENT_USER/SOFTWARE/Clam and reboot
- if the client continues to hang after 1-3 attempts, delete the peers.dat file and try again

EDIT

Tbh.. I don't know what got the client running again. lol

[dy2k]

Are you seeing 5-10% cpu and 100+ mb memory usage while it is starting up ?

Try this :

- uninstall any 2005-2008 Microsoft Visual C++ and related apps
- run a windows error check
- backup the wallet and the .bak, delete the roaming folder and qt
- delete CLAM's registry folder located at HKEY_CURRENT_USER/SOFTWARE/Clam and reboot
- if the client continues to hang after 1-3 attempts, delete the peers.dat file and try again

EDIT

Tbh.. I don't know what got the client running again. lol

Tried all steps and it stills hangs. I get this error while opening it the first time and then the same hang error when I open it again.

https://i.imgur.com/llIW2lO.png
https://i.imgur.com/FeLF4OV.png

[paulc010]

Maybe the wallet.dat is corrupted?

Have you tried using the --salvagewallet option for the client, or tried using a backup of wallet.dat? When you reinstalled did you delete everything in the AppData/Roaming/Clam directory (EXCEPT wallet.dat, of course)?

[dy2k]

Maybe the wallet.dat is corrupted?

Have you tried using the --salvagewallet option for the client, or tried using a backup of wallet.dat? When you reinstalled did you delete everything in the AppData/Roaming/Clam directory (EXCEPT wallet.dat, of course)?

I tried running without importing any wallets and still same error. I tried deleting everything even in regedit and still no luck. I am guessing the error has to do with the core software running the wallet. Does any one know what is required in windows to run this wallet. For example Microsoft Visual C++?

[undergroundgeek]

Confirmations are slowing to a crawwwl....

Agreed.

This is totally painful. We haven't heard from SuperClam in a couple of days now, I'm starting to get concerned/worried/doubtful.

[SuperClam]

Confirmations are slowing to a crawwwl....

Agreed.
This is totally painful. We haven't heard from SuperClam in a couple of days now, I'm starting to get concerned/worried/doubtful.

Nothing at all to be worried about

Just busy trying to get things done!

Give a bit here, and I will have responses to all of the posts since the last response!

[phzi]

Tried all steps and it stills hangs. I get this error while opening it the first time and then the same hang error when I open it again.

[img ]https://i.imgur.com/llIW2lO.png[/img]
[img ]https://i.imgur.com/FeLF4OV.png[/img]

That error is very odd, because the format of that error should be:

Code:

CDB() : can't open database file <filename>, error <number>

It seems to trying to open an empty filename, which is just weird.

Have you looked if there is anything surrounding this error in the logfile?

Have you tried launching with a different (clean and empty) -datadir=<folder> ?

[SuperClam]

wallet is hanging after a launch.. already tried to clean data folder. What can be the reason?

There are a couple posts very similar to this one:

There was an issue that involved out-date deps; it has been fixed and should be included in the no-fork hotfix update coming soon
In the meantime, running CLAMS under a different username, deleting the CLAMS registry entry, and few other methods have been shown to help.

This issue seems to arise especially after a power failure, BSOD.

There is a lot of work going on behind the scenes; getting the entire code base up-to-snuff and eliminating many legacy errors and bugs which were carried over from the other clients/coins which were our descendents/forks.

We appreciate everyone's patience; we have a lot of "balls in the air" at the moment.

Someone is dumping all their clams.

There's some sell activity, but it's hardly a large dump.  Only 215 CLAM volume for the last 24 hours...
A fair number of people bought in around or below .0018, so it makes sense we're seeing some orders filled back down to those levels.
Overall the market looks pretty solid, considering the low volume.

Hopefully, this stability we see is a function of:

• the Multi-Pool @ kHashier.com,
• the peculiarities of the distribution method,
• the people who are already involved, seeing value in CLAMS.

There is no way to know for sure; of coarse.

CLAMs represent one of the extremely rare times that I'm happy people are selling for BTC without care.
Thanks for the cheap CLAMs!  Quite happy to be stocking up and improving my chances at hitting those lotto blocks!
I've broken my pile up into 32 equal stacks now - quite interested to see how staking goes over the next few days.
It is going to be big for CLAMs when Poloniex releases their CLAMs to account holders, I think.  We'll see dumpers that only care about fractions of BTC, sure, but a coin so widely distributed and in the hands of so many crypto-invested individuals is bound to create some significant interest and curiosity.  Hopefully we will have an improved wallet out by then (with a few hard-fork changes that will really help the CLAM network).

I know, right?  Even we didn't have any idea how addictive and fun this Proof-Of-Pearl Lottery update would be
Not sure what you meant by, "when Poloniex releases their CLAMs to account holders"...?

As another member mentioned, Poloniex already did a give away of exchange CLAMS.... might you be speaking of that?

[undergroundgeek]

Confirmations are slowing to a crawwwl....

Agreed.
This is totally painful. We haven't heard from SuperClam in a couple of days now, I'm starting to get concerned/worried/doubtful.

Nothing at all to be worried about

Just busy trying to get things done!

Give a bit here, and I will have responses to all of the posts since the last response!

Thanks for the replies! Any comment on current Network Rate and Dooglas' suggestion?

[phzi]

As another member mentioned, Poloniex already did a give away of exchange CLAMS.... might you be speaking of that?

Indeed.  I stand corrected, as they were already distributed.

Nice to see that exchanges probably didn't end up with the huge collections of CLAMs someone might initially suspect.

[SuperClam]

As another member mentioned, Poloniex already did a give away of exchange CLAMS.... might you be speaking of that?

Indeed.  I stand corrected, as they were already distributed.
Nice to see that exchanges probably didn't end up with the huge collections of CLAMs someone might initially suspect.

No way to be certain of coarse, without a list of addresses.  That said, Busoni over at Poloniex did mention the date/time they had "refreshed" the BTC exchange wallet before ever being given an exact date as to when the dumps occurred.  And it WAS literally the day before the distribution, suggesting honesty.

[Hippie Tech]

Are you seeing 5-10% cpu and 100+ mb memory usage while it is starting up ?

Try this :

- uninstall any 2005-2008 Microsoft Visual C++ and related apps
- run a windows error check
- backup the wallet and the .bak, delete the roaming folder and qt
- delete CLAM's registry folder located at HKEY_CURRENT_USER/SOFTWARE/Clam and reboot
- if the client continues to hang after 1-3 attempts, delete the peers.dat file and try again

EDIT

Tbh.. I don't know what got the client running again. lol

Tried all steps and it stills hangs. I get this error while opening it the first time and then the same hang error when I open it again.

https://i.imgur.com/llIW2lO.png
https://i.imgur.com/FeLF4OV.png

Just keep trying. It should eventually fix itself like mine did.

Delete the peers.dat, start it up and give it a few minutes each time.

Who knows .. a Windows repair might help.

[nikos64]

Nice to see you here SuperClam.
I thought you took my money and run.
A... wait, that was you give me money and run away...
 

[almightyruler]

I wonder if staking has slowed down because a large number of the coins are sitting in sell orders at Poloniex, and the exchange has staking disabled? (I haven't looked too closely at the order book so I'm just guessing.)

[ymod123]

I wonder if staking has slowed down because a large number of the coins are sitting in sell orders at Poloniex, and the exchange has staking disabled? (I haven't looked too closely at the order book so I'm just guessing.)

my wallet just got a stake but very slow confirmation

[almightyruler]

I wonder if staking has slowed down because a large number of the coins are sitting in sell orders at Poloniex, and the exchange has staking disabled? (I haven't looked too closely at the order book so I'm just guessing.)

my wallet just got a stake but very slow confirmation

Yes, because your stake still has to be confirmed by other stakes.

The last 100 blocks have taken approximately 5 1/2 hours to mint, which is an average rate of about one block every 3 mins and 20 seconds.

edit: I can see that potentially causing a bad situation: if no new wallets come online (or no new funds are injected eg via purchase) could this turn into a vicious cycle, where confirms for stakes are taking longer and longer, therefore the time between stakes is increasing, therefore confirms for stakes are taking longer and longer, therefore .......

[SuperClam]

Nice to see you here SuperClam.
I thought you took my money and run.
A... wait, that was you give me money and run away...
 

;D;D

Confirmations are slowing to a crawwwl....

Agreed.
This is totally painful. We haven't heard from SuperClam in a couple of days now, I'm starting to get concerned/worried/doubtful.

Nothing at all to be worried about
Just busy trying to get things done!
Give a bit here, and I will have responses to all of the posts since the last response!

Thanks for the replies! Any comment on current Network Rate and Dooglas' suggestion?

Sure

It isn't a suggestion.  dooglus has already been contributing over on git for some time; expect a fix for block time and difficulty with the next forking update we do

[SuperClam]

I wonder if staking has slowed down because a large number of the coins are sitting in sell orders at Poloniex, and the exchange has staking disabled? (I haven't looked too closely at the order book so I'm just guessing.)

my wallet just got a stake but very slow confirmation

Yes, because your stake still has to be confirmed by other stakes.
The last 100 blocks have taken approximately 5 1/2 hours to mint, which is an average rate of about one block every 3 mins and 20 seconds.
edit: I can see that potentially causing a bad situation: if no new wallets come online (or no new funds are injected eg via purchase) could this turn into a vicious cycle, where confirms for stakes are taking longer and longer, therefore the time between stakes is increasing, therefore confirms for stakes are taking longer and longer, therefore .......

Have some trust in the CLAM   

All is in hand, though it can be painful at the beginning like this.
In fairness, the % return right now, even for a 0.1 CLAM block, is WELL worth the wait.

[nikos64]

Have some trust in the CLAM   

All is in hand, though it can be painful at the beginning like this.
In fairness, the % return right now, even for a 0.1 CLAM block, is WELL worth the wait.

Yes, but after 9 0.1 CLAM blocks I want that 999 CLAM block