Topic: Tumen miner - WebGL miner (Read 6291 times)
is anyone running this? i'd like to try it out
no interest at all on this, eh?
I checked it out, updated firefox, installed webcl then got this notice when activating webcl that ended the curiosity for me."WARNING! This WebCL implementation is experimental and is likely to introduce severe security vulnerabilities in your system. Use it cautiously and at your own risk. This setting is also available in Advanced Settings (about:config) as extensions.webcl.allowed"
no interest at all on this, eh?
OK, I could use a hand getting this working. Right now my firefox is way too new for krad miner. Any suggestions?
bitcoin.pandemichosting.com
A buddy of mine came up with a fix for the version issue.
bitcoin.pandemichosting.com
A buddy of mine came up with a fix for the version issue.
I like that this is happening, I wish I understood it all
This is the old kradminer, a miner that works in your browser.
Now it is open sourced by a good Samaritan! ^_^
I like that this is happening, I wish I understood it all
AWESOME! I'll give it a try!
https://github.com/temujin9/tumen_miner
Quote
Here is the dump, I may have other versions, but this was the first thing I found, it maybe the best I have. I think the important javascript parts were miner_original.js and worker_original.js (which is missing) but you maybe able to de-minfy the worker.js file.
The whole client side of the system was just the index.html page, and those two javascript files. IIRC the 'web-worker' can't create an opencl context so all the work is done in the main javascript thread. The backend is just a proxy to a bitcoin miner, the reason it exists is just because of javascript security you have to connect to the same url/port, so that can be replaced by a modern mining proxy of some kind.
My advice would be to study how webcl works, and get a demo of that going in your own code, then learn how the mining process works, and try to load the opencl kernel using your own webcl javascript code. then look over the worker.js and miner.js files and pick out the pieces that actually do the work of converting the bytes around to the right formats and talking to the webcl kernel. Looking at the source of poclbm and diablominer should give you an idea of the various byte conversion functions needed, krad miner works in the same ways as these miners do, only the code is in javascript and you have to deal with the strange different world of javascript.
The whole client side of the system was just the index.html page, and those two javascript files. IIRC the 'web-worker' can't create an opencl context so all the work is done in the main javascript thread. The backend is just a proxy to a bitcoin miner, the reason it exists is just because of javascript security you have to connect to the same url/port, so that can be replaced by a modern mining proxy of some kind.
My advice would be to study how webcl works, and get a demo of that going in your own code, then learn how the mining process works, and try to load the opencl kernel using your own webcl javascript code. then look over the worker.js and miner.js files and pick out the pieces that actually do the work of converting the bytes around to the right formats and talking to the webcl kernel. Looking at the source of poclbm and diablominer should give you an idea of the various byte conversion functions needed, krad miner works in the same ways as these miners do, only the code is in javascript and you have to deal with the strange different world of javascript.
Jump to: