Embedable Javascript Bitcoin miner for your website

[scooter]

We've definitely discussed it... and as presha pointed out, the BTC you can make by mining in-browser (or anywhere) won't last forever, with the virtual guarantee of diminishing returns. The idea of a general-purpose browser-based distributed computation framework is extremely enticing to me If nothing else, this project has taught us a little about how that would work and what it might look like.

Right on. Should you ever decide to move forward on a project like that, I would be more than happy to contribute in some way.

[1713852222]

1713852222

[1713852222]

1713852222

[Basiley]

when browsers get OpenCL support, along with WebGL nowdays, or as part of it, things stabilize.

[interfect]

Would it be possible to hack something together using WebGL right now? Like they used to do before real GPU computing solutions were available? I believe you can read pixel data back out of a <canvas> tag.

[Basiley]

thats can't be nearly as efficient as OpenCL processing, IMO, but yes. thats how, actually 1st GPGPU appz work back few years ago.

[Sergey (imcex.com)]

Requesting mining stats in control panel  Thank you 

[winnetou]

Requesting mining stats in control panel   Thank you  

+1

btw: great project =)

[lowentropy]

Requesting mining stats in control panel   Thank you  

+1

btw: great project =)

Thanks guys We appreciate the feedback.

We'll be rolling out some basic stats into the console page this evening, namely: average hashrate (over the last 100 getwork requests), and total shares earned in the current round (we are in round 1, which ends Saturday).

We will work on more after that. Also, we will soon add support for a configurable siteId parameter which will let you track your sites separately while collecting shares on one account.

[gigitrix]

I love your failure page. That is all

[1bitc0inplz]

We just deployed the updated user console. This version should introduce some basic stats. We show you your average hash rate over the past 100 getwork requests. We also show you your current shares this round.

We have a lot of things we want to add, so believe us, this is just a first step. So do let us know what else you'd like to see in the console.

I love your failure page. That is all

Thanks we do too 

[brombomb]

sent you a pm.  Been running since it more or less opened and no hashes in my console...

[mosimo]

Loving the idea of this, I have it running on one of my sites. Right now though I don't know what I'm actually getting from this if anything. A lot of my users will leave the site open all day and just leave it there. However in the console it says my current shares is 0 and current average hashrate is 647. Is this hashrate the overall of my clients, overall of the service and over how long?

Things I'd like in the console:

• Round start/end time
• Number of my clients connected within the last x mins (10 or 30 minutes maybe)
• Average hashrate over the last 30 mins/1hr (Of my clients)
• List of average hashrate over the last 7 days. Graph might be best for this. (Of my clients)

[scooter]

Current average hash rate: 1093.0473480726896
Shares this round: 0

Poo.. I hoped to have more shares than 0

[Sergey (imcex.com)]

Also, we will soon add support for a configurable siteId parameter which will let you track your sites separately while collecting shares on one account.

1. Would be great if bitp could collect refering domain names automatically and group stats according to domains. It would be useful for people, running bitp.it running at multiple sites.

Concerning average rate: average rate is per 100 request as far as I remeber. Could you please recalculate it into avg per second? (hour, day, etc...)

Also, I vote for all the requests from mosimo

[newmont]

Great work!

I am considering rolling these tags out across web properties that generate 200M impressions a month. What is your capacity? Can you handle this request volume?

Feel free to PM me to discuss further.

[lowentropy]

1. Would be great if bitp could collect refering domain names automatically and group stats according to domains. It would be useful for people, running bitp.it running at multiple sites.

Concerning average rate: average rate is per 100 request as far as I remeber. Could you please recalculate it into avg per second? (hour, day, etc...)

Also, I vote for all the requests from mosimo

Thanks for the feedback, guys... we will try to get these additional stats into the next update:

• Group stats by domain
• Hashrate over several time periods
• Graph of past hashrates
• Show total getwork requests along with hashrate
• Round start/end time
• Recently connected clients
• List of when each share was found

Keep in mind we're not a pool ourselves, so our "rounds" always last one week. The first one will end on 20110528.

[BitcoinsWallet]

Thanks for the feedback, guys... we will try to get these additional stats into the next update:

• Group stats by domain
• Hashrate over several time periods
• Graph of past hashrates
• Show total getwork requests along with hashrate
• Round start/end time
• Recently connected clients
• List of when each share was found

Keep in mind we're not a pool ourselves, so our "rounds" always last one week. The first one will end on 20110528.

Great for that! 

[1bitc0inplz]

Just a quick note for those who have not seen any shares show up in their console.

While we are very proud of our Javascript bitcoin miner, please remember that the 6 to 10 kilohash/sec that one receives with our miner is nothing compared to a modern CPU and especially a GPU.

The real magic happens in numbers. Take something as low as 10 kilohash/sec and multiply it by hundreds of visitors, and then the work becomes noticeable.

As was stated by lowentropy, we hope to expose your total hash rate (not just an average) in a coming update. Hopefully this total hash rate will give everybody a better idea about how well their script deployment is working for them.

In the mean time, just remember, bitp.it has the best hash rate to wattage ratio.... ever 

[1bitc0inplz]

Great work!

I am considering rolling these tags out across web properties that generate 200M impressions a month. What is your capacity? Can you handle this request volume?

Feel free to PM me to discuss further.

We'd love to think so, but the reality is that we are still in beta. While I would love to tell you "sure, go ahead", I think a more realistic answer is to roll it out slowly (over some of the smaller properties first) and see how it works for you. And, if all goes well, then slowly work your way to some of the larger properties. Heck, maybe even inject the script in random... some visitors get it, some don't... and let's see how the servers take it.

[newmont]

Ok - I have rolled it out across a few sites but see very low average hashrates (1k hash/sec) in the bitp.it hash rate counter? Any idea how this could be? There are probably 40 concurrent users at any given time - so I'd expect roughly 30X this rate.

[lowentropy]

Ok - I have rolled it out across a few sites but see very low average hashrates (1k hash/sec) in the bitp.it hash rate counter? Any idea how this could be? There are probably 40 concurrent users at any given time - so I'd expect roughly 30X this rate.

There is some confusion on this number - it is not your total average hash rate, but the average hashrate of one of your clients. So if you have 40 concurrent users, your total hashrate is indeed 40x this number.

In the next couple of days we will roll out more complete stats that will show your aggregate average hashrate over multiple time periods. Sorry for the confusion.