Will lyra2z330 gain benefit from thoese ssl/sha optimizations, too?


FYI, with the help of a sysadmin, I got it to work (well, he did, most of it, and I ignore the details), so this miner is now running on Centos 6.9 and real hardware.

It looks an ambitious goal, yet an interesting project. I'm new to tokens, I guess this is the time to begin documenting on how they work in order to not miss this chance.

Keep up good work.

I would also liked the reCaptcha V2 very much, way more than every other where you have to type something, but at the condition that it worked normally, without handicaps.

When I started with the faucets, I remember it took just a click and the green mark appeared. Today, is a looong gone memory.

In my experience and congecture, what I think Google does is, simply and foolishly, to increase the fail chance with the increase of frequency of use of the the widget. Doing so, Google associates an increase in frequency of use to an increase of possibility that the network is running automated queries.

That would be bad, but not so bad if the solving difficulty was increased, okay, maybe I have to suffer a bit more because I have to prove I'm no bot or because I'm consuming your bandwidth, uh?

The fact is that at some point, solving them becomes impossibile, they fail even when you solve them correctly on all the slides and slow fading out tiles that are shown. I'm experiencing that in these days on freebitco.in, freedoge.co.in, the moon*, the bitfun and bitcoinbonus and on some dice site at the free faucet. The common line here is that I'm using them pretty much since the same amount of time and at high frequency during the day because as a developer I work at pc/internet most of day and sometimes at night and on Chrome only.

Today, I had the idea to change browser, try to go back to the sluggish shitty Firefox, and even if it lags with as few as 5 tabs open, well, I had no issue with the recaptcha, it's been a miracle don't having to loose minutes in front of that stupid popup and desperately refreshing the page. So maybe it need some cookie cleanup to reset this "virus".

I think admins of these site don't fully consider or take seriously this problem because they don't use, of course, this kind of sites themselves, so if they test them once in a while, they see the widget working perfectly normal because Google doesn't apply a free fail chance to a low frequency user. I would be suspicious of those sites that benefit from multiple page refresh when the captcha fails and you have to submit the page again, but I don't think this is the case, not for all of them at least, because some of them don't even have ads (freebitco.in)

--

I found this video days ago in the official google recaptcha discussion group (that is FILLED with complaints about this by the way), where a guy shows the issue pretty well:

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

XTremeLoser

Personally I first hated the captcha where you had to input the six black letters, but now, after so many issues with Google recaptcha V2 and its stupid street signs, cars, store fronts that get continuatively asked for, I like it way more when it gets choosen by the system.

So if I had to choose a captcha, my favourite list would be, in order of preference:

1. the six black letters (don't know if it has a name)
2. SolveMedia
3. Google reCaptcha V2

Where do you access that kind of information? I can't find it anywhere.

I understand this sites give away bitcoins, but we give away our IP address for ads, popups, clicks and multiple page refreshes when captcha strangely fails, but admin should take some time to respond to some enquiries and not staying 100% in the shadow.

Here and in the various moon*, bonus*, where apparently the admin is the same, I never received an answer when complaining to not working captchas and when they fail during so many attempts.

Also, during this DDOS I saw my daily bonus reset because site was unreachable. ("You must make at least 1 faucet claim during the previous day to be eligible for this bonus")

So, I appreciate the service, even if filled with so many ads, but admin should get more in touch with us.

I received it immediately. Is your email correct? Did you check the spam folder?

I just noticed there is a clone of this btchoax, in all similar, they are spamming the internet with this scam scheme.

kryptomachine . com

Same modus operandi, same bullshit.

Another update, sorry for the spam.

Managed to install devtoolset-6 (GCC 6.3.1), it was quite straightforward:




The errors are always there, but at least they more detailed. They are all very similar, I'll paste just one:


Searching in and here found just this similar question: https://stackoverflow.com/questions/43128698/inlining-failed-in-call-to-always-inline-mm-mullo-epi32-target-specific-opti but not much idea how to proceed.

XTremeLoser

Sorry if I flood the thread, but it may be useful information to others, too.

Managed to update to gcc 4.9 (thanks to this guy's comment), with:

(reminder: I'm on Centos6.9)

sudo yum install centos-release-scl
sudo yum install devtoolset-3-toolchain
scl enable devtoolset-3 bash

Relaunched make, got these lines on screen (still out of redirected txt, duh):



warning: implicit declaration of function ‘syslog’ [-Wimplicit-function-declaration]

Then many other lines started to popout, ending with these, that may be related to Intel intrinsics already mentioned before:



Now I try to fix all these, if you have any clues to spare, thank you in advance.

Found this for _mm_shuffle_epi8 of the last screenshot : https://msdn.microsoft.com/en-us/library/bb531427(v=vs.120).aspx

The full makelog2.txt: https://pastebin.com/yr6dexwL

---

after digging here and there, it looks like a matter of upgrading GCC to the greater version available, from my current 4.9 to 6.x or 7.x even.

Thank you, I'll surely need that once I manage to compile the miner.

I'm slowly trying to come to an end at this

Followed your advice, did a make -B > makelog.txt.

First lines to popup on screen (they weren't redirected to makelog.txt, strange), were about 10 of this:

configure: WARNING: The assembler does not support the AVX2 instruction set.

It seems for that I need gcc 4.7 at least, I'm running gcc 4.4.7, I'll try to update this as first thing.

Okay maybe there is no need for this since this service is confirmed to be legit, but I can confirm myself that a transfer of 50k sats from my coinpot.co account to my freebitco.in account succeeded in less than 24 hours without any issue.


Ah alright, this makes 100% sense.

I wonder why one should decide to depoist into coinpot in first place. It's perfect to receive micropayments from faucet and its internal miner, other than that, I wouldn't know.

Amazing, keep up good work!

Mmm 3 days are a lot, did you try to contact them?

XTremeLoser

Having experienced in person with my account that odds to win becomes very very very rare the most you go on, I think chance to win could be a formula similar to this:

chance to win = ( 0.029 - balance ) * 100 / 0.029 [%]

eg:

when balance is 0 (you just registered), chance is 100%

when balance is 0.01, chance is 65%

when balance is 0.02, chance is 31%

when balance is 0.025, chance is 14%

when balance is 0.0289, chance is 0.34%