how come this uses much more cpu than the mine 32 process option

I think it should be a dynamic structure.


Eg:

https://bitsharestalk.org/pools.xml


<?xml version="1.0" encoding="utf-8"?>
<pools>
  <mcpool>
    <name>MMC Pool</name>
    <website>http://mmcpool.com/</website>
    <logo>http://mmcpool.com/logo.png</logo>
    <api>http://mmcpool.com/api?wallet=%wallet%</api>
    <connect>minerd --url http://work.mmcpool.com/ --user %wallet% --threads %threads%</connect>
  </mcpool>
  <extasie>
    <name>Extasie Pool</name>
    <website>http://extasie.net/</website>
    <logo>http://extasie.net/logo.png</logo>
    <api>http://extasie.net/api?wallet=%wallet%</api>
    <connect>minerd --url http://extasie.net:8337/ --user %wallet% --threads %threads%</connect>
  </extasie>
</pools>


logo directive can be base64 data.


api directive
Eg: http://mmcpool.com/api?wallet=MQoJDguWCMAug2J2rRUEsZPC9UjdSCppkS

Result:

<?xml version="1.0" encoding="utf-8"?>
<api>
  <paid>16.2157</paid>
  <balance>1.22</balance>
  <unconfirmed>7.5832</unconfirmed>
  <connected>Yes</connected>
</api>


I am going to fork on github and add support for the XRamPool protocol.

It will be accepted, right?

I'd like to see extasie.net added. Uses the same getwork protocol.

Although it does need a username & pass .. No idea if you have that in the GUI.
--url http://extasie.net:8337/

I'll shortly bundle MMCPool's minerd with the wallet and introduce a menu option allowing wallet users to pool mine with just a single click. It'll launch an external process running minerd properly parameterized for MMCPool.

Any other pools using the same network interface (capable of using the same client software with different parameters)  that would like to be included in the GUI - please let me know asap.

We'll need to have a careful think about how to standardize an interface for the GUI to talk to pools, but for now I just want to get it up and running quickly.