We are launching bitp.it today, a revolutionary 100% Javascript based bitcoin miner that you can easily embed right into your own website. Visitor to your website will run this Javascript seamlessly in the background computing hashs for you, and if a share is found you (the website owner) will receive credit.

We are hoping this will be viewed as an exciting new alternative to banner advertisement that actually has the potential of not being annoying to website visitor and actually generating bitcoins for the website operator.

bitp.it uses Slush's pool, and for the time being we will pay you out your shares in 0.01 BTC increments once a week. We realize there is a lot to be done, and possibly even some bugs along the way, so we are going to not charge any fees of our own for the first month while we iron out some of the details. Slush will obviously take his fees off the top, but other than that your earnings should be passed straight through to you.

Since we are treating this like a beta, we'd love to hear your feedback, good, bad or ugly. Post up here and let us know what you think.

Javascript is just too slow to mine bitcoins. The recent difficulty increases have made this an impractical idea. Couple that with the fact that WebCL is practically non-existant, and what you are left with is an ornithopter.

It is this reason that we started our own pool (https://pool.bitp.it) for people to use their own CPUs and GPUs to mine for bitcoins. It is also this same reason that effective July 9th, 2011 we will no longer be offering Javascript as even an option. All existing users are encouraged to switch to our pool.

We will leave the server side Javascript in-place, so you're existing websites will not attempt to fetch content that doesn't exist. However, the JS on our end will be gutted rendering it non-functional.

dude, it seems like your script is based on your own pool. Can you post the source code?

bitp.it uses Slush's pool. We are still working out the longer term details of how the backend will work, there has been lots of talks of establishing our own pool. But for now, to boot strap this process, it just makes more sense to use an existing pool.

I have some very HIGH traffic sites that would benefit from this but i need some more information will this be open sourced at all ? i need more info to assure there is nothing malicious going on simply because well thousands of users at one given time will be mining i need to know this won't fuck ANYthing .. i also need to know how the workers can be monitored on my end .. no offense but i can't trust anyone these days bitcoincontact me if you want to be discrete and charge what fees you need to but i need to know before i put this on a major production site what were dealing with

-J

EDIT:

also that said is there a way to adjust the total cpu usage ? seems to be only like 40% increase appreciate it thou seems interesting but possibly viral i can think of MANY MANY ways to use this maliciously sadly

also that said is there a way to adjust the total cpu usage ? seems to be only like 40% increase appreciate it thou seems interesting but possibly viral i can think of MANY MANY ways to use this maliciously sadly

I would also be interested in a similar feature, I don't want to bombard my users CPU to any point at which it would impact the running of their PC (or become noticeable).

Ya i see it works in slush's pool but.. Where do I input my worker information so the calcuations done on the site are made for my account on slush's pool

Ah... very good question, I misunderstood.

When you register you enter your email address. We are feverishly working on the user control panel, and that is where you will set your wallet id to receive your payouts. We are targeting weekly payouts, and the hope is to have the control panel ready this weekend.

I have some very HIGH traffic sites that would benefit from this but i need some more information will this be open sourced at all ? i need more info to assure there is nothing malicious going on simply because well thousands of users at one given time will be mining i need to know this won't fuck ANYthing .. i also need to know how the workers can be monitored on my end .. no offense but i can't trust anyone these days bitcoincontact me if you want to be discrete and charge what fees you need to but i need to know before i put this on a major production site what were dealing with

-J

EDIT:

also that said is there a way to adjust the total cpu usage ? seems to be only like 40% increase appreciate it thou seems interesting but possibly viral i can think of MANY MANY ways to use this maliciously sadly

These are exactly the type of discussions we wanted to generate. In regards to open source, let me discuss with my partners. This is something we only briefly discussed and I am not sure where we ended that conversation.

We intentionally avoided using jQuery, prototype, or any other frameworks as we wanted this to not interfere with anyone's website. We also make use of "namespaces" (well, as much as JS can :-D) to also reduce the change of doing anything bad to any of your existing JS.

We would be honored to have you test it out on your site, I will send you a PM shortly in case you wanted to discuss in any more details.

As far as the CPU...

Chrome, Safari, and Firefox have support for HTML 5 WebWorkers. In those browsers the JS defaults to using 100% of one core. Since this is a WebWorker, it has no ill effect on the web page. In IE (or any other browser without support of WebWorkers) hashes are computed in the UI thread using a setTimeout that makes it VERY CPU friendly. There are settings in our code to force even Chrome, Safari, et al to use the UI thread and be equally as friendly as IE. A recent change today made those settings less obvious. I will work on getting those exposed better, and will report back.

Thanks for registering. Our hosting provided (for some reason) is blocking outbound SMTP connections. We have an open support ticket with them trying to get this resolved.

Your Javascript should be fully functional though. The email will be used to help you set your password when we bring the user control panel online in the next couple of days. In the mean time, any shares generated with your custom Javascript will be tired to your account. When the control panel comes online this should all be a little more transparent.

But on a side note, great idea, although one question how well does it handle people moving between pages because the rate at which shares are generated with CPU hash rates is surely going to be pretty low?

But on a side note, great idea, although one question how well does it handle people moving between pages because the rate at which shares are generated with CPU hash rates is surely going to be pretty low?

Thanks for the bug report... I will get right on this. The Firefox issue I have a very good idea what that is about. That kinda ties back to the comment I made about, about exposing our miner engine settings better.... it looks like the way we are passing params into the iframe is not liked by Firefox 4.

I will look into the IE one as well, it may be one and the same.

You are right, one pages where people on only there for a brief instant, this would be less than ideal. This is really good for websites like blogs, newspapers, forums, etc, where people sit and read content for a few minutes at a time. That is not to say that it wouldn't work on any site, but I think you catch my drift.... the long someone just sits on your website, the better it is for you, the website operator.

I'm probably about to show my ignorance of bitcoind and Javascript/HTML5 in a couple of lines (I'm a Java/C programmer and tend to ignore Javascript wholesale) but here I go.

Is it possible to push smaller work units than the default (most cpu's seem to do about 1 share per minute from my experience) in order to reduce the amount of time required on each page, or are the share sizes a hard coded part of bitcoind/rpc? Or perhaps is it possible to have the miner store its state in HTML 5's cache in some way, so that it can be resumed on subsequent pages? Or maybe make use of a cookie to store the state information which is then reread on the new page?

I'm not sure the client will be very happy to see his computer burn CPU for apparently no apparent reason, though. But indeed it is probably better than annoying add. Again: awesome idea.

My intention is to only have it run for guests to the site, the person can choose to not enable it by simply registering with the website - fair trade off in my eyes.

Edit: I'd like to make a request, I'm sure its already on the cards but I'll ask anyway, within the control panel it would be nice to see some information such as effective total hash rates, number of users currently hashing and such and perhaps some distinction between the pages which it is being run from (or some ability to set of "campaigns") so that we can see which pages on our websites are proving more or less effective that generating coins.