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

[grunt]

I don't have skills to check the source myself. Since there is a risk BTC from the wallet I'm still using could be stolen, it's not worth the risk for me.

It's good to be skeptical. If you find the specific private keys which have Clams to be dug you can export those and delete them from your BTC wallet. You can claim the clams at just-dice or by importing the keys into a clam client running on your computer. So there are ways to insulate yourself and your btc.

[1714178495]

1714178495

[1714178495]

1714178495

[1714178495]

1714178495

[JWU42]

I am running HEAD from Git and can't seem to get things "right".

1.  Encrypted the wallet
2. Ran

Code:

clamd walletpassphrase passwordhere 999999 true

to allow stakingonly

3.  I get the following result -- see below (i.e., Weight seems wrong)

4.  balance is > 150 clams

Code:

user@HOST:~$ clamd getstakinginfo
{
    "enabled" : true,
    "staking" : false,
    "errors" : "",
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "pooledtx" : 0,
    "difficulty" : 28234.19972784,
    "search-interval" : 16,
    "weight" : 0.00000000,
    "netstakeweight" : 305129.11962176,
    "expectedtime" : -1
}

As Dooglus mentioned above, just needed more time for the staking to kick in.  All appears normal now.

[MikkisJ]

I don't have skills to check the source myself. Since there is a risk BTC from the wallet I'm still using could be stolen, it's not worth the risk for me.

It's good to be skeptical. If you find the specific private keys which have Clams to be dug you can export those and delete them from your BTC wallet. You can claim the clams at just-dice or by importing the keys into a clam client running on your computer. So there are ways to insulate yourself and your btc.

I still use the same addresses and private keys that have CLAMS distributed to. Using a different address for each transaction is very troublesome and annoying, because you need to back-up every single one of them.

I use only a couple of addresses, they are all back-uped and I don't have to buck-up the wallet or private keys every time I receive coins.

You can tell that CLAM creators don't care about this or created the system to steal coins, because it's easy to verify owning the address with a signed message without requiring the private keys. But they want your private keys.

[garthkiser]

I still use the same addresses and private keys that have CLAMS distributed to. Using a different address for each transaction is very troublesome and annoying, because you need to back-up every single one of them.

I use only a couple of addresses, they are all back-uped and I don't have to buck-up the wallet or private keys every time I receive coins.

You can tell that CLAM creators don't care about this or created the system to steal coins, because it's easy to verify owning the address with a signed message without requiring the private keys. But they want your private keys.

The CLAMclient is open source software. Every single line of code is a matter of public record at: https://github.com/nochowderforyou/clams

While you nor I can fully examine the code ourselves, plenty of other people can and have. As to your statement that signing a message to verify ownership is "easy"; it also poses a security concern: https://bitcointalk.org/index.php?topic=623147.msg10044191#msg10044191

If you want to dig up CLAMs but have a problem using your keys, then empty the BTC, LTC or DOGE address of coins before claiming CLAMs.

[SuperClam]

I don't have skills to check the source myself. Since there is a risk BTC from the wallet I'm still using could be stolen, it's not worth the risk for me.

It's good to be skeptical. If you find the specific private keys which have Clams to be dug you can export those and delete them from your BTC wallet. You can claim the clams at just-dice or by importing the keys into a clam client running on your computer. So there are ways to insulate yourself and your btc.

I still use the same addresses and private keys that have CLAMS distributed to. Using a different address for each transaction is very troublesome and annoying, because you need to back-up every single one of them.
I use only a couple of addresses, they are all back-uped and I don't have to buck-up the wallet or private keys every time I receive coins.
You can tell that CLAM creators don't care about this or created the system to steal coins, because it's easy to verify owning the address with a signed message without requiring the private keys. But they want your private keys.

We are not a brand new project.

We have been doing this for over 6 months: not a single loss of coins.

Our offer to delete the entire project if someone could show us a single line of malicious code still stands.

Best practices with Bitcoin, or any derivative crypto, requires that you use a new address for each receive.

Empty the wallet into a new wallet/address.
At that point, your previous address(es) are nothing more than random strings of letters and numbers.

Every single funded address is currently worth something like $4 USD at exchange.
I would trade a random string of worthless letters and numbers for that reward -> any day of the week.

[unamis76]

CLAM surprising again, price-wise... Good to see this coin alive

[dooglus]

You can tell that CLAM creators don't care about this or created the system to steal coins, because it's easy to verify owning the address with a signed message without requiring the private keys. But they want your private keys.

You've already told us you don't have the skills required to understand how this stuff works, so what makes you think you're in any way qualified to make such silly statements?

You should pay somebody smarter than you to examine the client code for you, and then you should apologise to the CLAM developers for your rude words.

[crush]

Okidoki,

managed to import my LTC wallet.dat and got my first CLAMS.

Now I can't get my multibit.key file to work.. I go to the console, type "importwalletdump multibit.key" and get a big fat red "-".. The *.key file is in the same directory as the clam-qt.exe.. What could I be doing wrong?

[SuperClam]

Okidoki,
managed to import my LTC wallet.dat and got my first CLAMS.
Now I can't get my multibit.key file to work.. I go to the console, type "importwalletdump multibit.key" and get a big fat red "-".. The *.key file is in the same directory as the clam-qt.exe.. What could I be doing wrong?

Please feel free to stop in to #clams on freenode IRC for additional assistance.

Please ensure that the multibit wallet has been exported with the "encrypted" setting set to false.
The export must not be encrypted in the case of multibit to work.

[crush]

Okidoki,
managed to import my LTC wallet.dat and got my first CLAMS.
Now I can't get my multibit.key file to work.. I go to the console, type "importwalletdump multibit.key" and get a big fat red "-".. The *.key file is in the same directory as the clam-qt.exe.. What could I be doing wrong?

Please feel free to stop in to #clams on freenode IRC for additional assistance.

Please ensure that the multibit wallet has been exported with the "encrypted" setting set to false.
The export must not be encrypted in the case of multibit to work.

Will do cause I can't seem to import my DOGE wallet either :/

[sgk]

Okidoki,

managed to import my LTC wallet.dat and got my first CLAMS.

Now I can't get my multibit.key file to work.. I go to the console, type "importwalletdump multibit.key" and get a big fat red "-".. The *.key file is in the same directory as the clam-qt.exe.. What could I be doing wrong?

I have ran into similar problem in past.

Then what I did was, I imported all private keys into BitcoinQT Core wallet and then imported the wallet.dat file into CLAM wallet. Worked fine.

[picolo]

CLAM surprising again, price-wise... Good to see this coin alive

The price is relatively high at 0.0056 when it has been trading at 0.003 just 4 days ago. It seems like a good time to sell to buy again at 0.003 in 4 days

[sgk]

CLAM surprising again, price-wise... Good to see this coin alive

The price is relatively high at 0.0056 when it has been trading at 0.003 just 4 days ago. It seems like a good time to sell to buy again at 0.003 in 4 days

I sold some CLAM at price of 0.0045 BTC just yesterday. Now the price is at 0.0065 BTC.

Surprising indeed.

[BayAreaCoins]

Looking to buy bulk.

10,000 coins and up only please.

100% confidentual and no exchange needed.

[fast2fix]

CLAM surprising again, price-wise... Good to see this coin alive

The price is relatively high at 0.0056 when it has been trading at 0.003 just 4 days ago. It seems like a good time to sell to buy again at 0.003 in 4 days

i sold some today at 0.006.are you sure i'll go 0.003? if it goes i'm gonna buy it.

[BayAreaCoins]

CoinMarketCap now displays the proper market cap for CLAM

http://coinmarketcap.com/currencies/clams/

[ajw7989]

CLAM surprising again, price-wise... Good to see this coin alive

The price is relatively high at 0.0056 when it has been trading at 0.003 just 4 days ago. It seems like a good time to sell to buy again at 0.003 in 4 days

i sold some today at 0.006.are you sure i'll go 0.003? if it goes i'm gonna buy it.

Its possible it will drop how low not sure but a 50% increase in 24 hours is usually artificial (without huge news) with the exception of bitcoin in the 2013 rise (that just didnt drop at all til after 1k)

[picolo]

CLAM surprising again, price-wise... Good to see this coin alive

The price is relatively high at 0.0056 when it has been trading at 0.003 just 4 days ago. It seems like a good time to sell to buy again at 0.003 in 4 days

i sold some today at 0.006.are you sure i'll go 0.003? if it goes i'm gonna buy it.

Its possible it will drop how low not sure but a 50% increase in 24 hours is usually artificial (without huge news) with the exception of bitcoin in the 2013 rise (that just didnt drop at all til after 1k)

It was at 0.003 just 4 days ago and 0.0039 less than 24H ago. I am selling at the current price even if CLAM could go up a lot in the long term.

[BayAreaCoins]

CLAM surprising again, price-wise... Good to see this coin alive

The price is relatively high at 0.0056 when it has been trading at 0.003 just 4 days ago. It seems like a good time to sell to buy again at 0.003 in 4 days

i sold some today at 0.006.are you sure i'll go 0.003? if it goes i'm gonna buy it.

Its possible it will drop how low not sure but a 50% increase in 24 hours is usually artificial (without huge news) with the exception of bitcoin in the 2013 rise (that just didnt drop at all til after 1k)

There is news right above your post...

CoinMarketCap now displays the proper market cap for CLAM

http://coinmarketcap.com/currencies/clams/

Big thank you to the CoinMarketCap folks, xploited and everyone else who emailed them.

I highly encourage tips to those listed above!

[DLow]

Okidoki,

managed to import my LTC wallet.dat and got my first CLAMS.

Now I can't get my multibit.key file to work.. I go to the console, type "importwalletdump multibit.key" and get a big fat red "-".. The *.key file is in the same directory as the clam-qt.exe.. What could I be doing wrong?

I have ran into similar problem in past.

Then what I did was, I imported all private keys into BitcoinQT Core wallet and then imported the wallet.dat file into CLAM wallet. Worked fine.

Good idea but synching the whole BTC blockchain..?