I know why CLAM is being dumped. Someone finds a bug on Just Dice.

I just entered Just-Dice to see the invest program, and I saw a dude with the nickname "Hogan (2044519)" winning ten times in a row a 45 X bets... THAT´S IMPOSSIBLE!!!!

So he is cheating on Just Dice and dumping all the clam on poloniex. He plays at this hours so nobody can see him, but some people saw it and suddenly he stoped playing.







Here the video:

https://www.youtube.com/watch?v=vu6Ts3fAbQM

Affiliate pay is always flat CLAMS.

100% for faucet use & 0.10545574 CLAM for each address dug.  We pay out on the same block as the person you bring as well.

Tx fees... I'll send kef here for that, but I'm thinking it's like... nothing (CLAM tx fees are cheap.)

I really like your idea about multi single address digging.  I'll talk to kef about implementing that soon... sounds easy enough!

I'll talk to kef about implementing that soon... sounds easy enough!

Get a deposit address from Just-Dice.com and then you're two clicks away.

Deposits take 6 minutes.

How would a Multibit user use our site at the moment I wonder?  (So I can reference that post in the OP or we can add it to the "Features to come list".)

Can they export their stuff or something like that?

Faucet is working again!

Thank you very much for waiting.

Out Bitcoin buying program is working fine as well .

Hello

I am uploading my Multibit wallet and am getting an error that it is not recognized as a valid wallet.

It is version 05.

Any help is appreciated.

Every time that i try to claim appear this message: "Please wait 9 minutes and 11.96 seconds before requesting another tip from this IP address."

Someone knows why? The site have a lot of bugs

Shortly.

You will have to have 10 drops to be able to hit the hourly faucet once... this isn't set in stone yet.

We will also be launching a new faucet option as well!

<...>

Kef,  Could we possibly have our scanner scan both ways automatically for Blockchain users?

1.  Address has clams

2.  So customer puts in private key

3. Address private key fails 

4. We assume this is a blockchain address, so scan the "right" WIF priv key for them using the information given.

5..  Success or failed dig.

On blockchain.info to this address I have only 2 secret keys.

format Base58 - MoL4zV1Jxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

format WIF - KwQ4uDR7xxxxxxxxxxxxxxxxxxxxxxxxxxxx

How do I create a backup copy of my wallet for my blockchain?

What Wallet Import Format (WIF) does CLAM use? I'm trying to import private keys generated by pycoin - in Bitcoin WIF format - but they don't seem to be recognised.

A rescan finds keys that were imported via importwallet (entire wallet), but ignores keys imported via importprivkey (single key, Bitcoin WIF, no error reported.)

It seems the faucet is mostly sending outputs of 0.0001 CLAMs, worth roughly a hundredth of a US cent each. I was wondering how best to deal with it. It costs more to spend than it is worth, and so the logical response is to never spend it, and to set a minimum deposit amount. Any deposit less than the minimum would be considered a donation. I ended up changing the hot wallet client code such that it never spends the dust outputs, but instead merges them whenever the wallet stakes. That is free to do, and so the cost of handling the dust is passed on to all the full nodes in terms of bandwidth and storage, but at least the UTXO set isn't being polluted.

Here's an example of a staking transaction tidying up a bunch of faucet dust.

I spoke to Kef about the dust from the faucet. I recognize that it makes no sense to ask people to stop spamming the blockchain. Maybe Kef/BAC would comply, but the next guy might not. We can't trust that CLAM users are going to be responsible. Better to limit the "damage" they can do, if such limiting is needed. Currently I'm not sure it is. Individual recipients of the dust can refuse to honor the tiny deposits if they don't want to deal with it, and maybe that's enough. If there ended up being enough dust that the blocks fill up a fee market will presumably develop, as it did in Bitcoin.

Personally I wasn't going to even bring the subject up, other than asking Kef if he can aggregate users payings into larger amounts and set a minimum withdrawal amount for the site. But since both the faucet and the subject of fees preventing spam both came up in this thread recently I figured I would mention it.

Edit: I should probably be clear that I have no problem with the faucet site. It's just that a lot of its outputs end up at Just-Dice, and they had been causing technical trouble until I found a way of dealing with them. They'll still be bloating the chain and the Just-Dice hot wallet, but not the UTXO set any more.

When coins are received, they are received in a single 'output' at the address they were sent to.  
That 'output' is a single unit.  

When you make a transaction, every 'CLAM' of that output must be accounted for - not just the amount you are sending.  
For this reason, even if you send a single 0.00000001 'clamoshi', the entire output must be spent.  
So, the remainder, the 'extra', the 'change' is sent to a different address you control.  
This is likely what happened in your situation.  

Receive 10 CLAM at address 'A'.
Send 1 CLAM to address 'X'.
The other 9 CLAM goes to address 'B', your change address (9 + 1 = 10).
Now, all your CLAM is at address 'B', a different address from the one they were sent, initially, to.

Send another 1 CLAM to address 'Z':

"Why did the CLAM come from address 'B', and not 'A'?"

Edit for clarity: 
The entire 'output' doesn't actually have to be sent to an address, though I left this out to keep it simple.
Any amount not accounted for actually goes to fee.

Is it possible to use UTF8 for CLAM speech? I tried the sendtoaddress command (after fixing clamd, pull request issued) on an UTF8 terminal, so clamd should get the UTF8 string. I used this string as the CLAM speech parameter "test2 äöü 象形字", transaction: 2e7d31559f88322bbd66ea361f312c695fb62984ae133b7661cd21dcb2110366. I don't know if the UTF8 characters made it into the transaction, looks like khashier.com doesn't show it, but it looks like the typical 2 bytes UTF8 chars.
Update: khashier supports already UTF8, test with the text 嗨!: http://khashier.com/tx/e4d5c2f48e8da1c0ed800edf87281dddb9b8d1c5e612e18b173015c7946707b0
Looks like some kind of command line encoding problem on my Linux machine or in the clamd command line program.

I deleted all CLAM things. run sudo app-get update and reinstalled Libtool stuff.
Downloaded everything CLAM again, started form scrtach and it works now.

Downloaded bootstrap.dat, synced from HD, restarted clam-qt and the last 20 or so weeks are syncing now from the network.

Only weird things is, when I want to start clam-qt from the GUI it won't start, only by using Terminal window and then run command ./clam-qt

Really, doog? ;(

Also, by default we ship the beans ground, as you saw in the coffee can pic.