Deleted everything and started over in case I just screwed up somehow. Still telling me the password is incorrect, but I have double verified that it is the correct one in the original dogecoin wallet. Ideas?
I had no trouble working with encrypted wallets. I just did a 'clamd walletpassphrase $pass 3600' then a 'clamd dumpprivkey $addr' to get the unencrypted private key. Then I could import the private key into my main clam wallet. By the way, I'm new to proof of stake "mining". Does it do any kind of brute-force search to mine blocks? I see stuff about a "target" and see it using a fair bit of CPU. Also, I mined block 31337, bitches.  |
|
|
|
|
I noticed a couple more things about Clams:
1) The clams github repository is a fork of blackcoin and so has no issue tracker of its own; that leaves me nowhere to submit bug reports without bothering the blackcoin people.
2) I experimented with importing various wallets. I found that simply using -rescan instead of -salvagewallet found more funded private keys in almost every case. There's something very wrong with -salvagewallet - so much so that not using it is almost always better than using it.
|
|
|
|
Why my clams are in stake, but not in spendable balance??
It seems like you have to wait for 510 confirmations after "staking your coins before they are spendable again. At 1 confirmation per minute, that corresponds to around 8.5 hours. |
|
|
|
So many scams, so little coin and time!  However they are offering to pay better than BTCjam on pure bitcoin. Still a lot of risk for just a "Trust me!". It's zero risk if you adopt this simple strategy: "don't send them your coins" |
|
|
|
Thanks. Turns out I had heard about it before but hadn't heard the details. It's surprising how many ways there are of copying JD wrongly  |
|
|
|
I would only consider investing if you would be able to transfer .5btc into my wallet and I will return it on top of my 7.5btc deposit.
I also would be willing to invest any coins Neo Nart is willing to send me. It would end up being massively profitable for all concerned, as it would allow Neo to start his magic doubling machine. Please make it at least 10 BTC - let's make lots of money! |
|
|
|
Also, I forgot to mention.
Although the -salvagewallet flag did work, and did end up giving me some clams, while it was running the debug.log was spewing out lots and lots of messages like this:
I just tried again on another wallet. This time clamd exited when it had finished doing the -salvagewallet: ******* exception encountered *******
/home/chris/Programs/clams/src/clamd[0x53a75c]
/home/chris/Programs/clams/src/clamd[0x422647]
/home/chris/Programs/clams/src/clamd[0x426e48]
/home/chris/Programs/clams/src/clamd[0x563543]
/home/chris/Programs/clams/src/clamd[0x5655a5]
/home/chris/Programs/clams/src/clamd[0x567c57]
/home/chris/Programs/clams/src/clamd[0x44e7a4]
/home/chris/Programs/clams/src/clamd[0x4529b9]
/home/chris/Programs/clams/src/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fc217f1bec5]
/home/chris/Programs/clams/src/clamd[0x41d88b]
Flush(false)
DBFlush(false) ended 0ms
StopNode()
Flushed 0 addresses to peers.dat 60ms
Flush(true)
DBFlush(true) ended 0ms
Clam exited I deleted the wallet.dat, copied the same wallet back in, tried again, and the same thing happened. I think previously it carried on running when the -salvagewallet was done. |
|
|
|
We only receive money on an exchange, then sell them instantly and withdraw it to our bank account. Rl cash comes to our bank account in max 24 hours so there is no risk at all. And again, we are not Ponzi.
Btw, could you please remove your negative feedback please? We never made any deal so you are simply lying to other people.
I'm not claiming that we ever made a deal. My feedback says that I risked 0 BTC dealing with you, which is true, and will remain true. I'm claiming that it would be a bad idea to trust you. You make unrealistic unsubstantiated claims about your ability to double people's money. It's incredibly likely that you're running some kind of a scam, and people need to be warned about that. |
|
|
|
How do you make your huge guaranteed returns?
We do not invest all money in one place so if we lose on one investment we can pay everyone from another one.
Does that work in casinos too? Can you go to a roulette wheel and not put all your money on red. Then if you lose, you can make a profit from the bit you didn't lose. Stupid analogy, but appropriate I think. How do you make such huge returns? |
|
|
|
Once again we'd like to ask user MEM to remove negative trust he gave us. He does not respond to any requests, but still. Also we'd like users who make money with us to give us positive trust. Forum trust affects the image of the program, and the image of the program affects the stability of your payouts, since we are a Ponzi after all.
I just left you positive feedback, for what it's worth. I've not used your service, but it does appear that you're running it honestly. |
|
|
|
[...] possible ways to recoup funds later for investors such as SatoshiCarnival is doing.
I missed that one. What's the story there? Did they get exploited too somehow? |
|
|
|
Also, I forgot to mention. Although the -salvagewallet flag did work, and did end up giving me some clams, while it was running the debug.log was spewing out lots and lots of messages like this: ******* exception encountered *******
/path/to/clamd[0x53a75c]
/path/to/clamd[0x422647]
/path/to/clamd[0x47e127]
/path/to/clamd[0x49e975]
/path/to/clamd[0x480011]
/path/to/clamd[0x4a4678]
/path/to/clamd[0x5658fb]
/path/to/clamd[0x56713d]
/path/to/clamd[0x53fe93]
/path/to/clamd[0x4500f3]
/path/to/clamd[0x4529b9]
/path/to/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f406b3bbec5]
/path/to/clamd[0x41d88b]
******* exception encountered *******
/path/to/clamd[0x53a75c]
/path/to/clamd[0x422647]
/path/to/clamd[0x47e127]
/path/to/clamd[0x49e975]
/path/to/clamd[0x480011]
/path/to/clamd[0x4a4678]
/path/to/clamd[0x5658fb]
/path/to/clamd[0x56713d]
/path/to/clamd[0x53fe93]
/path/to/clamd[0x4500f3]
/path/to/clamd[0x4529b9]
/path/to/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f406b3bbec5]
/path/to/clamd[0x41d88b]
******* exception encountered *******
/path/to/clamd[0x53a75c]
/path/to/clamd[0x422647]
/path/to/clamd[0x47e127]
/path/to/clamd[0x49e975]
/path/to/clamd[0x480011]
/path/to/clamd[0x4a4678]
/path/to/clamd[0x5658fb]
/path/to/clamd[0x56713d]
/path/to/clamd[0x53fe93]
/path/to/clamd[0x4500f3]
/path/to/clamd[0x4529b9]
/path/to/clamd[0x41839a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f406b3bbec5]
/path/to/clamd[0x41d88b] |
|
|
|
Sorry, but I am not handing over my private keys. This looks like a risky precedent. You should have thought of some way for the owners to prove they had the required wallet private key by generating a public key, or sequence of public keys, or sending dust or similar. Any protocol that requires the private keys is suspect.
You don't need to hand over your private keys, any more than you hand over your private keys when you run bitcoin-qt. Your private keys are used to sign transactions, the same way as they are in Bitcoin. The difference here is that all private keys which had non-dust balances on some date in May this year were sent 4 clams. |
|
|
|
Indeed, coins involved in, and created by, a coinStake transaction/block do not show up in getbalance until they have reconfirmed.
Is there some way I can get a list of all the addresses which have unspent coins? I can use "listunspent" but it doesn't show the ones that have been involved in staking recently, not even if I use "listunspent 0". I'm guessing I need hundreds of confirmations before I can use those coins again - but I'd like to get a list of the addresses with funds so I can export their privkeys and import them into my main wallet. Will have to check into the double dash; I would have swore the double dash was required but it wouldn't be the first FUBAR I had made.
I've checked. I was surprised the double-dash worked, but it did. And so did the single dash. By the way, thankful to see a member with some clout involved in CLAMS.
You are always welcome.
Anyone who wants to give me free money will generally get my attention. |
|
|
|
Just add "--salvagewallet" (no quotes, with a space separating what is already there) to the end in the field.
The source code says it's -salvagewallet with a single dash. It works whether you use one dash or two. I just imported a dogecoin wallet. Soon after the -salvagewallet finished, I used 'clamd getbalance' to show my balance - there were some clams in there. I waited half an hour for more of the blockchain to sync, checked again, and my balance had decreased. What's that about? Edit: I guess 'getbalance' defaults to showing confirmed balance, and I had staking enabled, which made some of my clams go unconfirmed? |
|
|
|
Once again: Thank you for your services, I hope you had as much fun as we players and investors did "Fun" really isn't the word for it, but I do miss it now that it has stopped. |
|
|
|
Are they using an exchange account for their scam? That seems kind of dumb.
This is an exchange account, not 'private wallet' or whatever it is called.Suggestion for the FAQ: q) I can't decide whether to leave my coins on an exchange or risk them in a Ponzi scheme. What do you advise? a) Send them to us. We're a Ponzi that leaves your coins on an exchange so you can risk your coins while you risk your coins. Double the excitement! |
|
|
|
Appears to be the case which is 100% bullshit.
It's a tough call. Suppose you accidentally run a roulette game where 60% of the numbers are red due to a manufacturing error. Some guy notices and plays for 15 hours non-stop, betting on red over and over, and wins a bunch. Are you obliged to honour all his bets, even after he openly admits "I saw there were more reds than blacks, so I bet on red a lot"? I don't know the answer. I do think it makes sense to refund the people who bet on black and lost due to the error, but it's less clear what to do about people who won a bunch on red. Some of them didn't even notice the error and were just playing 'red' because they like red, but others were clearly playing because they saw they have a positive expectation. I guess the right thing would be to pay him out, and take the hit. Whether to pass that on to investors or not is a separate question. |
|
|
|
Got everything back in full. Dean has quite literally worked non-stop since the issue happened and has made everything good.
Has there been a statement about exactly what bets have been / are going to be rolled back? What's the deal with the sjess account? Is he just out of luck? |
|
|
|
|
Show Posts
