Topic: Embedable Javascript Bitcoin miner for your website - page 11. (Read 149641 times)

I never even thought about the idea of pausing/resuming the worker.... but, I don't see any technical reason why it couldn't be added.

We are currently working hard to get you guys a control panel ASAP... but, once we get that out there, these ideas like WebCL, and even these Chrome extensions are very high on our list to investigate. I've honestly never heard of Chrome extensions before just now, but they look interesting. I am going to read up more on this idel execution extension.

Thank you for the link.

Can you add functionality to stop/pause worker in runtime. This is very useful for browser extensions. For example Chrome extensions support idle api http://code.google.com/chrome/extensions/idle.html so your worker could work in background and do not bother user.

I agree, if Google did flag it as malware, it could be a problem.

However, I do not currently have a reason to believe that Google would flag this as malware. Because, as best as I know, this does not meet the definition of Malware.... if so, wouldn't Google have flagged Bitcoin.org as a distributor of malware, for having miner downloads on it's homepage?

I ask to provoke questions, and discussion. I've been thinking about this all morning, and as best as I can rationalize, this is not different and an ad server. Even Flash ads can, and do, consume your CPU like their is no tomorrow.

However, I am thinking, just as a good general thing, that we will start including the forceUIThread: true setting as part of the default scrip that the site gives new users. This way, by default, the scripts out in the wild are more "nice" than not... hopefully this will help ease a lot of concerns all the way around. And, as always, anyone wishing to force the jsMiner to use web workers and be more performant can either remove forceUIThread or explicitly set it to false.

What do you all think? Again, I do not claim to know what to do... but I do want to open up the discussion.

Keep up the feedback, I appreciate it.

Sorry to disappoint, Steve, but our site is just listing hashes per second, so you're probably seeing 9 khps, not 9Mhps 

Unfortunately, javascript computation is rather slow There is intense discussion of making use of web-based CL to use the graphics card, but no implementation yet.

That can be a big problem....

I compared this with the native Bitcoin c++ client's mining...I am getting 4 to 5x the performance with your Javascript miner (running on OSX in the Chrome browser).  Can anyone else confirm that (I'm getting about 9Mhash/s in the browser vs less than 2Mhash/s with the bitcoin client)?  If it's really the case, that's quite impressive!

When Google scans a page, it looks at all links, embeds, etc. It will see the script address for the embed. After they decide that the script is taking up too much CPU (user reports and whatnot), they will flag it as malware. Any page that embeds the script will also be flagged as malware. This can lead to things like pre-visit warning dialogs within the browser.

Hiding the script, along with any related content, from bots such as Google is the only way to prevent a page from being flagged.

For the fun of it, Google Nexus S - 350-400 using the Android Browsers on Android 2.3.4 and Firefox 4 actually does worse at 300-350 

Introducing Bitcoin mining on your otherwise useless iOS devices;

500 hashes per second on the first generation iPad, and 430 hases per second on the forth generation iPhone.

Both running Safari on iOS 4.3.3.

Sucks battery power like nothing I have ever seen.

And there he is 

Howdy, I'm one of the developers of bitp.it, and I'm going to help 1bitc0inplz field questions.

I'm working on pushing out registration emails and a console page where you can:

 - Set a password to log in
 - View statistics about your hashes and shares
 - Set a wallet id for payouts
 - Get your script code, in case you lost it

Everyone who signed up should get an email some time late this evening or tomorrow morning (we're in CST here).

Thanks for your patience during our launch and thanks to everyone helping us iron out code issues. We really appreciate it.

No, that was a bug. It should be fixed now.

Also, one of my partners, lowentropy should be swinging by soon to introduce himself too. He has been helping me with this project.

When comparing the effects of using forceUIThread / webWorkers I noticed that the UIThread variant makes a lot more requests to the server than the webWorker variant. webWorker seems to make about 1 request every 10seconds in FF4, whereas UIThread appears to be making 5 or more requests a second.

Just want to confirm that this is the intended behavior.

This is pretty damn cool.

Is there no way to add GPU mining to this?

EDIT: To answer my own question, it looks like it would be possible in the future using WebCL.

I have dual core. With one tab open it goes to 50% CPU. With two tabs open to 100% CPU. So that works fine. However, i want to know if i'm working on 2 different shares in that sense. Offcourse using Chrome.

Also, how do i easily show hashes/s just like bitp.it does?

Hmm, interesting.  Patiently waiting for a full release. One thing that I'd like to know, though. I accidentally signed up several times, and I believe my ID's were different for each. While the control panel thingamabob isn't working yet, which ID should I use with the embedded code? The last one I got?

Wow!

First off, to everyone who registered and/or replied to this thread. Thank you all. I never imagined there would be this much interest in this. Your feedback, all of it, is great. This is really helping us find ways to make this even better.


I am a little confused on what the concern is. AFAIK, Google, et al, do not execute Javascript when they visit your website. Am I missing something?


Javascript cannot explicitly set thread prioritization, the browser is left taking care of that. From my testing, it would appear that all the major browsers do set thread priority to "nice". Read my replies below though, because this seems to be a shared concern, and I think I know how we can help limit the CPU utilization if you so desired.



Thanks, I appreciate the feedback. You are right, this is not ever going to compete with a GPU miner. The basic idea is that you, the website operator, have all these visitors. Right now many websites place banner ads on their site to try and make revenue. Banner ads are less than ideal in that they require the visitor to do something (assuming PPC, not PPV) for you to make revenue. This, however, is entirely non-volontary on the site visitor's behalve. They *have* to mine bitcoins for you if they are using your site. There was mention in a previous reply about turning this off for registered users, or other sub-sections of your website base, and I think thats an awesome idea too.

Where this Javascript miner really shines is in it hash/sec per watt 

I do think you have a valid point about not wanting to run people off with a high CPU usage, so did a few others. For now, just use the forceUIThread: true setting to make the worker process more CPU friendly. This will reduce your hashing rate, but will make it more friendly for your website visitors if you choose. Today I will also look into making more of a "nice" setting where you could set the niceness with better precession... of course this would be implemented in a work-pause-work, and not actually setting the thread priority level... but, I do believe the browsers already have their threads set to nice... so this would only be reducing the CPU load, which is what I believe you (all) are looking for as an option. I agree, I think that'd be a good setting to have.

As far as GPUs, I'm glad I bought mine as well. I do not think they'll be going anywhere anytime soon.


Which browser gave you 100%? Of the browsers I tested, they generally fall into two categories... those that support HTML 5 web workers, and those that do not. Only the ones that support web workers should be running the CPU at any noticeable percent (maybe I'm wrong, I'll test more)... but the ones with web workers support will max out 1 core.

So, in the 50% case, I assume that means you have a dual-core machine?

In the 100% case.... I am stumped. Unless you only had 1 core, or had this open in multiple tabs, I do not know how that would have happened. Let me know what browser and OS, and I'll look into it.

Just awesome. An easy way to use my work computer as a bitcoin generator. I can even leave it on 24/7 if the cleaning lady doesn't turn it off .

Any easy way for me to display my hashes/s in the little HTML file i made?

Also: When running one instance i get 50% CPU, with two 100% CPU. Does this matter in the sense that i might be doing double work or?

Not quite...

Google could place this on their website and gain 50%+ hashing power of the network overnight.

EDIT: Then again, maybe not...

According to my calculations....

One $100 5830 can do 300,000,000 hashes per second if tweaked correctly.

Divided by an average of 10,000 hashes per second for an average cpu running this javascript miner = 30,000 concurrent visitors to your website to equal the hashing power of a 5830 - and whenever users hit your website, their CPUs would start burning up... so they would probably leave within let's say 2 minutes of visiting your web page.

So multiply 30,000 concurrent required visitors by the number of 2 minute intervals in the day... (24 * 60 / 2 = 720)

And you come to a total of 21,600,000 unique visitors per day that you would need to your website in order to hash the equivalent of a $100 GPU.

Or make about $8 per day according to the bitcoin calculator right now from 21 million unique visitors.... totally not worth it.

Phew, now I feel better about my mining investments!

Don't get me wrong OP, I love it when anybody contributes anything to the bitcoin network, I am just thinking out loud.

It's obvious why it's happening, but shouldn't it be using just enough cpu so that the visitors/users of the site don't notice anything?