Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 68. (Read 1151252 times)

I also didn't catch your response to this dooglus.

I'm still waiting on a response and I will work with them to get it pushed to the public if they have a solution...


Doog, we are doing the best we can.  It'd be nice if you'd continue to contribute as well rather than just recommending blackballing transactions.  You're one of the most talented humans I've ever met/heard of/read about.  

I'm about to go tits up on my end trying, but I'm going to make it.

I can't imagine my day becoming reduced to fucking Litecoin gambling contests..... what would of 2013 dooglus have said to 2018 dooglus?!  

Thanks for idea! I'm installed Ubuntu on virtual machine and linux-client import bootstrap.dat perfectly!

Yes, the problem was with file extension, thanks!

Did you try on any real operating systems? Windows is mostly for playing games I think. I tried running bitcoind on Windows many years ago and found it didn't work very well at all.


I'm not sure exactly what you're saying, but if you mean it won't load claim.cfg, it's not meant to. It loads "clam.conf" only. You have to spell it like that.


Try renaming the config file to "clam.conf". It goes in the same place as the CLAM wallet.dat file and bootstrap.dat.

Somebody can archive synchronized ..\Roaming\Claim folder without you wallet.dat?

I have issue that bootstrap.dat don't want to apply. I tried on clean ..\Roaming\Claim(only wallet.dat and bootstrap.dat) folder, and tried synchronize about several weeks and after this tried apply bootstrap.dat. Tried turn off internet before do this, tried several clients x32/x64 v1.4.17 on several Windows 7 x32/x34 The symptoms is same -  getblockcount return 88 blocks and I see bootstrap.dat.old file..

Also I have strange issue that client want use claim.cfg with nodes(tried several formats addnode=220.118.173.91:31174 or addnode 220.118.173.91:31174 add). Tried put it in folder with wallet.dat or client exe file. After this I can go to console and write "addnode 220.118.173.91:31174 add"
and there was no error that this node exists. I(and client file) have full access to folders because client can rename bootstrap.dat to bootstrap.dat.old file.

Do you have any idea how they do that? Did they fix whatever it is in the CLAM wallet that makes it get so slow after receiving too many payments?

The CLAM wallet is open source. Patches are welcome. I made all my improvements public when I was adding the features I needed for it to work with Just-Dice. It would be nice if others gave back too.

This is not a shot at you either obviously... you've gone above and beyond allowing us to tip faucet users directly through Just-Dice and everything else you do.

I really do understand it is nothing against me or my site, but what you are saying is things you aren't even sure about (the exchanges being broken.)

All I'm saying is maybe rather than blackball a service... fixing the problem at the core would be a better way to go about it.  

Even if that is raising fees or whatever the fix is.

As an investor... It'd be nice to know that one retard that can't even code could cause such a issue.

Has our faucet ever crashed your wallet? (Just-Dice)  I remember the Bitcoin wallet dying once a week (this is possibly an exaggeration, but those were more stressful times it seems) and people freaking out from 4am-9am, but not once can I recall the CLAM wallet doing that ever.  (This happened so much in Bitcoin that there was a nickname for it "restart the just-dice *potato*" aka the computer or whatever).

I frequently talk to others that accept our deposits and our affiliates play a pretty penny per day there (far exceeding what we give in CLAM for them to try the spot out risk-free. That includes deposits and the action.

Right now we give out .6 CLAMS ish per day and our players bring us about 10-50 CLAM every few days in action from our affiliate stuff... and that is from a single site that chose to use CLAMS! (People play with all sorts of different coins because CLAM users can very easily be "whales" from the "cheap" 2014 days.  I hope this leads to other sites accepting CLAM and helping us grow.)

I mean I do understand from your point of view... you've got "enough" and just want shit to work smooth, but for someone that wants to work hard and get known... our faucet can be a huge player in helping that.

Edit: not trying to sound like earning dick... I'm just saying it pays off for those websites in users to accept CLAM dust for folks to test their site.



This is affiliate earnings from the action on a single coin from a single affiliate in less than 24 hours from some website owner (LuckyGames.co) that has the time and is will to put the effort into running a CLAM wallet that accepts dust deposits to try their site out.  (that was a mouth full )

It's not about saving pennies, it's about not having your CLAM client grind to a halt every time a new block is found as it struggles to update the wallet.dat for each of the thousands of dust outputs it contains.

If you use "mininput=0.001" in clam.conf then the wallet won't recognize the dust deposits at all, and so isn't bogged down by them.

This is nothing against you or your site. It's just a practical matter that once the CLAM wallet has received too many transactions it starts performing horribly. I don't know for sure, but I expect the reason that the various exchanges have their CLAM wallets offline a lot of the time is something to do with this same issue.

Edit: I listened to the voice recording. I probably should have mentioned the off-chain tipping thing we do instead of spamming the blockchain. You should sort out a similar deal with luckybit if they're interested. But again, this isn't about saving the 50 cents it costs to sweep the dust. It's about not having the dust transactions cause the wallet software to grind to a halt. Sweeping a thousand utxos doesn't remove them from the wallet's tx list, and doesn't fix the slowdown issues we see.

Bluetrade is shitty exchange surely. Cryptopia exchange has fixed their technical problems finally as they stated in official announcement on Twitter channel some days ago "The planned upgrades have been successfully completed and we are back online".
Regarding to exchanges, I have a hint for your. There are cycle of exchanges from Poloniex-Bittrex-Cryptopia-Binance and now, it seems right time to go back from Binance-Cryptopia-Bittrex-Poloniex.
Poloniex will be great again. 

Also try next time to change audio recording settings to 192000 Hz/24 bit. It will greatly improve audio recordings.

For some reason, the chat on Luckybits website for Clambling isn't letting me post messages.

I'm horribly tired right now and I'm not trying to pick a fight with dooglus, but what he said in the Clambling Luckybit general chat isn't the whole story and I would strongly suggest services not ignore these small faucet transactions to save literally pennies.

My responds to the public chat @ Luckybits Clambling site: https://vocaroo.com/i/s1ttLTrK9tZs

(Excuse the few bumps in the recording... I made a near perfect recording on my computer, but forgot my fucking mic was blow and it kind of made doing the second recording a bit harder.)

Yes, my clocks are accurate.

Another comment: in the account history it would be useful if the txids were links to a block explorer, such as:

    http://khashier.com/tx/

prolly not an issue but did you synchronize both your computer and mobile phone time settings?

Looks good.

I had some trouble setting up 2FA. The 6 digit code I entered to enable it was rejected - it started with 00, which I thought might have been the problem. But it's also possible that the 30 second window had just changed and you don't accept slightly old codes.

I played about with it a bit and found that I could use the same 6 digit code twice - once to turn 2FA on, and again to turn it off. The codes are meant to be single-use only, so that's a security issue.

After turning 2FA on and off again, I couldn't turn it back on without first reloading the site. It seemed like the 2FA secret had changed on the server, but the client hadn't been updated with the new one. Clicking "Enable 2FA" in that state didn't do anything - no error or success message was shown.

Edit: it looks like you can win 999x on plinko, so it's not "up to 99.9x"...

cryptopia I do not recommend them mngo problems

Amazing!! Much needed competition for JD!
Are you planning on implementing bankroll / staking features or is it just for gambling?

+1 for Bittrex.

Poloniex and Bittrex are the best.

Bittrex is my prefered because the 100BTC withdraw daily limit, but they charge .2 CLAM for withdraw which kinda kills me inside to pay.

Dude you must be whale of the clams