 Show Posts
|
|
Pages: [1] 2 3 4 »
|
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 B A S E D |
|
|
|
Also, the estimated price says 'excluding tx fees', how much fees will be paid? I don't want to estimate something and then it goes busted in fees.
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!
Wow, that was soon. It sounds feasible and useful to me. You can pretty much assume the fee is 0.0001 for a dig. |
|
|
|
We now support uploading MultiBit export files in our ClamChecker. You can find the details about it here. Basically, you can upload the file created by MultiBit's "Export Private Keys" action. The caveat is that we currently only support private key files that are not encrypted. Support for encrypted files will come later. We haven't tested it with MultiLite or MultiDoge but those should work too. |
|
|
|
In fact, the current claim per minute is very low and you should do something about it. You all know how annoying it is solving these recaptcha stuffs and after that you get paid something which is even less than 1 satoshi btc.
I don't want to do comparison but whatever you people have for us should come fast.
People aren't using the faucet as intended right now. I believe the most profitable way is to use our faucet + Just-Dice and run the drops up as high as possible. Have some faith.  How to run the drops? Get a deposit address from Just-Dice.com and then you're two clicks away. Deposits take 6 minutes. We periodically (hourly, when this post was written) check to see if addresses are Just-Dice.com deposit addresses. If so, we tip you directly on Just-Dice instead of on the CLAM blockchain. You get your tips much quicker that way since you don't have to wait for confirmations. |
|
|
|
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.
We currently only support Core wallets at the moment, which are named "wallet.dat." Multibit support is a possible future feature. 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? Apparently Multibit supports exporting wallet keys in bulk, which would be easier to process than wallet.dat files. To use a Multibit wallet on our site manually, you would go through the list of private keys and dig each one individually. It doesn't look like Multibit outputs the address for each private key, so that may be an obstacle for some users (generating the address that you would tell us to dig). These private key dumps can also be password-encrypted, so we'd need to be able to decrypt them given the user's password if we supported Multibit wallet digging. |
|
|
|
Faucet is working again! Thank you very much for waiting. Out Bitcoin buying program is working fine as well . Sorry for the delay everyone; all of the pending tips (around 11k) were paid out last night so no tips were lost. 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.
We currently only support Core wallets at the moment, which are named "wallet.dat." Multibit support is a possible future feature. 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
Your IP is probably the same (as far as the Internet is concerned) as some other faucet user's IP. We've received a good amount of reports with the same issue. Not sure when we'll have that fixed though. We've tended to err on the side of caution in that area. |
|
|
|
Since the day the OP was created, we've had 27 wallets uploaded to our ClamChecker. Nine of those wallets have had diggable addresses. Those nine wallets had an average of 3.88 diggable addresses each. |
|
|
|
hi
is the hourly reward will come back?
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! I've enabled the drops feature. The /ask/ page will display the number of drops you need to enable hourly payouts. Once you get an hourly payout, that number will reset and you'll have to get more drops to unlock the hourly payout again. The number is currently set at 10 drops, but this may change wildly as we find the right spot. This feature may also be entirely removed so...enjoy! |
|
|
|
|
We want to verify empirically that our wallet dig covers all diggable keys in a wallet. Help us for great profit!
We don't store wallets after digging them, but we do store the hash of wallets we dig (to prevent duplicate uploads, etc.), so we'll be able to verify that you submitted your wallet for digging and that we failed to fully dig it. Be sure not to use your wallet after submitting it for digging, as that will change the hash of the file. Also, we'll need your wallet passphrase if it's encrypted. (We delete that after digging a wallet too.)
|
|
|
|
<...>
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.
Yes, I don't think that will be too much trouble. |
|
|
|
On the blockchain I see 2 formats
1. Base58
2. WIF
By 1 format, it says that it is not for this key
2 format just do not right
On my wallet I have 9000 Satoshi. Maybe that's why?
I believe Bitcoin "dust" starts at 10k satoshi. That's probably why. Hi. Why can not I sell my address? Writes Invalid Bitcoin private key. I enter the correct key. The address must be completely empty? What is the address you are trying to dig? Let me verify that it actually has CLAMS first and then we will see about private key format. Do you maybe have a password on your wallet? This address - 12ne4dJkrGY6rLLnuurweCKocKSLtLipeE That's a valid address for sure. Perhaps try digging the entire .dat automatically. This will also harvest CLAMS that you were unaware of hidden in change-addresses. https://freebitcoins.com/clamchecker/dig_wallet/How do I create a backup copy of my wallet for my blockchain? That address (12ne4dJkrGY6rLLnuurweCKocKSLtLipeE) can be dug. It sounds like you are using blockchain.info wallet? I don't know if they support exporting your entire wallet in the format we currently require. If FreeBitcoins.com says "The supplied key is not for the supplied address." then the private key you entered does not go to the address you are digging. Based on that address's history, it appears to be an "uncompressed" public key. This means your private key should start with "5". If your private key starts with "K" or "L", that is incorrect. On blockchain.info to this address I have only 2 secret keys. format Base58 - MoL4zV1Jxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx format WIF - KwQ4uDR7xxxxxxxxxxxxxxxxxxxxxxxxxxxx this is a problem with blockchain.info wallets. You can get the right WIF using bitaddress.org. Here's an example I made using a key I just generated. Put your key (KwQ4uDR7xxxxxxxxxxxxxxxxxxxxxxxxxxxx) in and it will give you the WIF key that should work. I highlighted the key that you should use in the screenshot below:  |
|
|
|
On the blockchain I see 2 formats
1. Base58
2. WIF
By 1 format, it says that it is not for this key
2 format just do not right
On my wallet I have 9000 Satoshi. Maybe that's why?
I believe Bitcoin "dust" starts at 10k satoshi. That's probably why. Hi. Why can not I sell my address? Writes Invalid Bitcoin private key. I enter the correct key. The address must be completely empty? What is the address you are trying to dig? Let me verify that it actually has CLAMS first and then we will see about private key format. Do you maybe have a password on your wallet? This address - 12ne4dJkrGY6rLLnuurweCKocKSLtLipeE That's a valid address for sure. Perhaps try digging the entire .dat automatically. This will also harvest CLAMS that you were unaware of hidden in change-addresses. https://freebitcoins.com/clamchecker/dig_wallet/How do I create a backup copy of my wallet for my blockchain? That address (12ne4dJkrGY6rLLnuurweCKocKSLtLipeE) can be dug. It sounds like you are using blockchain.info wallet? I don't know if they support exporting your entire wallet in the format we currently require. If FreeBitcoins.com says "The supplied key is not for the supplied address." then the private key you entered does not go to the address you are digging. Based on that address's history, it appears to be an "uncompressed" public key. This means your private key should start with "5". If your private key starts with "K" or "L", that is incorrect. |
|
|
|
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.)
WIF prefix is 133 instead of Bitcoin's 128. I have this change for pycoin: diff --git a/pycoin/networks/legacy_networks.py b/pycoin/networks/legacy_networks.py
index 98132a9..1770689 100644
--- a/pycoin/networks/legacy_networks.py
+++ b/pycoin/networks/legacy_networks.py
@@ -81,5 +81,7 @@ NETWORKS = (
# DCR Decred testnet : tprv/tpub
NetworkValues("Decred", "testnet", "DCRT", b'\x23\x0E', b'\x0F\x21', b'\x0E\x6C', h2b('04358397'), h2b('043587D1')),
+
+ NetworkValues("Clams", "mainnet", "CLAM", b'\x85', b'\x89', b'\x0d', h2b("0488ADE4"), h2b("0488B21E")),
)
Then do $ ku <Bitcoin WIF> --override-network CLAM to output the CLAM WIF given a BTC WIF. |
|
|
|
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. Unfortunately, the two biggest factors in this problem are results of features we advertise: 1. No waiting for payouts. 2. Instant commission for referrals. In other words: We send a payout every minute as long as the previous payout has a confirmation, and we pay commission in the same transaction that we pay a referral in. We also consolidate outputs to the same address into one output for each transaction. We may be able to come up with some feature in which a user consents to not receiving the payouts so quickly, maybe in exchange for a small bonus. The first problem I see with that is that we don't give users wallets, they give us an address. So you could enter someone else's address and they wouldn't get what they expect, etc. In the meantime, our payout transactions have ClamSpeeches starting with "FreeBitcoins.com payout ", in case any service wants an easy filter. |
|
|
|
|
There's no option for Doge-Dice, Just-Dice's "sister site" of sorts. It's less well-known, but does provide insight into why CLAM may have been chosen as the new Just-Dice coin: Users of the two old sites are likely to already have the new coin, so they don't have to buy it.
|
|
|
|
|
It's evident to me that KLYE has a lot of drive regarding KLYEMAX. He's been working at getting it ready for a while now. I personally think that KLYEMAX will do well. I've applied, because I think that KLYE can make something impressive of this if he doesn't have to spend time keeping order all by himself.
|
|
|
|
I have a question - I deposited some clam into my wallet. a few months later, I sent that balance to another address and it said the transaction came from a new address. how is this possible? does my wallet have multiple addresses, or does it change the address regularly? I had one address a few months ago, and now I have a different one. Confusing.
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. Commendable that you explained it in full instead of linking to this explanation. bugsywugsy, the link I just posted applies directly to CLAM as well as BTC. |
|
|
|
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/e4d5c2f48e8da1c0ed800edf87281dddb9b8d1c5e612e18b173015c7946707b0Looks like some kind of command line encoding problem on my Linux machine or in the clamd command line program. Isn't it technically possible to use any character encoding in clamspeech? Whether or not UTF8 is supported seems to be an issue for whatever is parsing/presenting the clamspeech. After all, the bytes are there, it's just a matter of encoding them as characters for human consumption. |
|
|
|
But when I start ./clam-qt I get this error: error initializing wallet database enviroment /home/username/.clam!
Do you have an existing wallet.dat in that folder, created using an incompatible version of the Berkeley DB? That's what it looks like to me. Try renaming wallet.dat and trying again. It should make a new one. Use your old client to move any coins from the old wallet to an address in the new one. 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 Does it work to run 'clam-qt' from the terminal when not in the directory that clam-qt is in? You may have forgotten to run 'sudo make install'. I'm not sure what lengths you went to to delete all CLAM things, but there could be an invalid symlink or some such. |
|
|
|
I have bought coffee from CryptoMercado many times. Shipping is fast, coffee is bomb. LLTGC. Here are pictures of my last order:   That could be anything in that package. Where's the beans? Really, doog? ;( Also, by default we ship the beans ground, as you saw in the coffee can pic. I wouldn't take that as a personal insult. Also, it may have been a reference to this:  |
|
|
|
|
