Topic: {CurlyBrace}-First PHP WebMiner-a proof of concept[v0.4] (Read 1529 times)

Chrome latest but those aren't from browser compatibility they are from bad coding.

So.

I could make a bunch of accounts on free webhosts and than upload this?


Also, could you make a git repo for this? :3

Running PHP bitcoin miner does not make much sense unless you have a dedicated server since the shared hosting services are very sensitive to your CPU usage. Therefore, you would not be able to occupy their servers for this purpose.

What browser are you using? Thus far I have only ran it in FireFox(20.0, on Windows 7). Don't worry, I'll sit down and fix browser compatibility issues during the next few days (But now I first need some sleep...)

This is testing data, for the most part copied directly from the getblocktemplate wiki page. It doesn't mean anything else.

It seems the URL to the source was also linking to an older version. Here you can see the newer version which has pool communication implemented.
(also, link in the first post is now updated to link to version 0.4 instead of 0.1)

Good night, I'll talk to you tomorrow.

~W-M

I'm doing some "code" poking around, I was curious of where you got "data" from and why is this line static? Its probably because of "testing" everything is usually static until it works so I can understand that but I want to make sure this data value isn't anything significant other than that reason?

Also note I've never made my own miner before I just understand Bitcoin client interworkings so this is slightly new to me. Cheers!

Hmm... it seems that I forgot to upload the latest version, that fixes that bug.

Try again now  .

No offence intended, just poking at the author thats all.... hehe I'm checking out the code now.

Hey there, Xenland, thanks a lot for your reply! Yes, this might be somewhat of a 'niche' application. I am mainly building it to get some better understanding about Bitcoin myself; It probably doesn't have practical purposes because it is extremely slow. That being said, up till now I've only tried it on free web servers. Paid web hosts, virtual machines or dedicated servers might perform much better, maybe even good enough to make profit. I didn't have the chance to try this out up till now.

Performance right now is somewhere between 2-4Megahash/second

What do you mean with " if it's legit"? The code works right now. The only thing that probably doesn't work is the submission of shares. It has produced a few shares before, but this was before the submission part of the script was in place. This application takes almost forever to come up with a share, so I have not been able to try out if the current implementation is correct.(It might be that I still need to change the answer over from big-endian to little-endian or something, before the pool will accept it).

It would be great if this can be some kind of example for other people to learn how to create their own miming applications. Altough for now the code is still very messy  . 

~W-M

I haven't tested this out or actually looked at any of the source code links, but I must say that although this might not get popularity for usage I think if its legit, seing a PHP / JS miner implementation would help increase the "learning" curve we all have.

Hello there, everyone,

For the past few days, I have been working on a new project. Because I wanted to learn more about how the Bitcoin works internally, I decided to give it a go and create my own miner. But not just an ordinary miner, no, something slightly different.


I present you:
{CurlyBrace}, the first PHP Hypertext Preprocessor Miner  (with a little bit of JavaScript as well)
(Disclaimer: This is a proof-of-concept. But it mines. For Real!)

---

Some basic info:
Language: PHP, and JavaScript for the front-end(steering wheel) of the miner.
Type: CurlyBrace uses the getblocktemplate standard.
Speed: Slow(0.1Mhash/s), but will hopefully allow paralellization in the future by talking to multiple webservers at once.

---

Why this odd language choice?
Using PHP, a serverside web programming language has certain interesting characteristics, and I was interested to see how well it would perform.

Pros:
-You now have some use for the normally unused processing power you have in your monthly server subscription.
-You don't have to pay for electricity costs during hashing on a remote computer.
-Opens up the possibility of setting up many servers (e.g. using free web hosting) in parallel, without much effort/costs.


Cons:
-Hashing is of course not fast. Tests thus far return about 0.1Mhash/s per slave webserver.
-Your worker username and password are visible by websites you are using. When using a cross-site AJAX solution, this data is even more visible.

---

What does the code do right now?
-You visit the webpage with the javascript client on it.
-Client asks the pool for a getblocktemplate reply.
-Client sends the returned block data to one or multiple server slaves, asking them to hash until they finds a hash below the target.
-Server hashes until it finds a hash below the target or it has tried 1000000 hashes(0.1Mhash). Returns results back to client.
-Client shows the debug info the server returned.
-If no correct solution is found yet, client sends a new request, but with an incremented nonce, to ensure that each server is looking at a different part of the possible hashes at one time.
-This continues on until a solution is found.
-Client submits solution back as a share to the pool. (this part might not be fully functional yet)

---

What still needs to be done?
-Support to increment the extra nonce (change the coinbase) when all 32int nonce values have been tried. (Right now the code is so slow that this never really happens before other parts die in one way or another, but its something to consider in the future.)
-Possibly change the way the final solution is padded together and submitted as a share (Might not work yet).
-Stop searching and load the next block when the current block has timed out. (Right now the script will continue searching on the current block until a solution has been found by it)
-Enforcing that the correct getblocktemplate and block version is used.
-Support for the optional parts of the getblocktemplate specification.
-Bugfixing. Lots of it.
-Possiblility implementing a scrypt algorithm as well(started, but currently disabled.)

---

Why  the need for a client webpage to operate the miner?
1. PHP is executed in a synchronious fashion, JavaScript on a web page is not. This allows parallellization(talking to multiple servers at once) when using JavaScript in the client side.
2. Very easy to start and stop.
3. I've had trouble getting cURL to work in PHP with ports different than port 80(which is the default HTTP web page port, but is almost never used for a bitcoin mining address).
   Also, many PHP hosts don't allow cURL to be used at all.
   Thus, using Javascript together with an Ajax Cross Domain service (such as YQL, which I'm using right now) seems like a better option.

---

Can I try this myself?
Yes, you can download the source here, upload it to your favourite webserver and direct your browser to http://yourserver.com/bitfrontend.html

Alternatively, you can currently see the script working here. Note that you shouldn't keep this version running for a long time as it doesn't use your own computing power but a few free webservers. I don't want to choke them. ;-)



Why do you post this here in such an early stage of development?
Basically I would love it if some people took the time to look through my code, and tell me if my calculations of the bitcoin hashing is correct. The main reason I started this project was to learn the inner workings of the bitcoin, so this would mean a lot for me.

I will be developing this project further during the next couple of weeks. But if there is anyone interested in contributing, feel free. There's a lot of optimizing and cleaning up to do ^_^'.

---

Thank you very much for your time. If you'd like to donate, you can thow a few coins in my direction here: 1MUZQsCSifF27XX98W13JLz6E9YaU3mVqG .


Have a great day!

~W-M