WalletBit says "batch: 8829"

What, pray tell, is this for?

3 units ordered, full payment via WalletBit eWallet, and I have my receipt mirrored here for all to see.

Thanks for keeping this list, senseless.

EDIT: Receipt contains BTC transaction. Here it is: http://blockchain.info/tx/e67d420550c2a572b668c21ed439e1ddddff4618768a7da9e0caf9e581fb6046

Indeed, jedi95 is now taking over the release maintenance of Phoenix 2 (as he did with Phoenix 1).

Tomorrow I'll request that the beta thread be closed.

We had it uploaded with an extra dot in the filename... Oops! jedi95 fixed it.

The changes for RC2 should really just be renaming MiningKernel to PhoenixKernel, and putting the kernel package in "plugins" instead of "kernels" (which is no longer used as the directory name)

Edit: Let me clarify: Those changes are what are needed to get it working. You should also add jedi95's changes, since those fix some performance problems.

Phoenix 2.0.0-rc2 is now up.

We changed lots of things here and there, but that should have taken care of all of the known bugs. As always, please test it and let us know.

The changes include:

• The kernels directory has been renamed to plugins
• Kernel API has been slightly modified
• An advanced-level example config is included in the doc directory (courtesy of jedi95)
• Backup pools are now possible (see first post for example)
• A handful of bug fixes

Still to be implemented for release:

• Web control panel? I hope?
• PluginInterface so third-party non-kernel plugins (GPU management, GUI support, etc) can be easily created

That error means the card found a hash where state_H != 0. While the error should really be "difficulty < 0.9999847..." we just round up to 1.

Because the OpenCL code only returns nonces satisfying state_H == 0, this is most certainly a hardware/OpenCL/kernel problem and not an unusual interaction with P2Pool.

I just posted a bounty for a web developer to write a nice web control panel. If you want to see it happen as much as we do, see the main post for the link to the bounty thread.

Current pledges

• Anonymous: 0 BTC (send to 12Ar9TeVxz4Bjf22dossLMdVMv7vpMJFce)
• CFSworks: 10 BTC
• jedi95: 5 BTC
• Total: 15 BTC

Overview
This bounty is for a JavaScript- (or perhaps Python-) based web control panel for the Phoenix 2 miner, which must:

• Be open-source - MIT/X11 is preferred since the rest of Phoenix is written in it, but BSD makes sense too. (L)GPL is fine, but AGPL may upset users who wish to introduce their own modifications.
• Be entirely self-contained - The web control panel cannot rely on external webservers, databases, etc. It must be served and operated entirely from the web/RPC server builtin to Phoenix 2. This means it must be pure-JavaScript (accessing the RPC server of the Phoenix instance that served it) and/or use Twisted .RPYs in the server.
• Have a first-time setup wizard - Upon first startup, the web interface needs to attempt a login with the default password ("phoenix")... If this password works, it should start a setup wizard that allows the user to set a more secure password, choose autodetect (GPU-only, GPU+CPU, no autodetect), and pick a backend.
• Be capable of managing devices - If the default password does not work, the control panel prompts for a password, then takes the user to a page listing all of their devices, with hashrates for each. The user should be able to disable/suspend/restart their devices from this page.
• Look professional - This is more subjective than the others, but please make the page look nice. It doesn't need to be full of images and flashy animations, but a white page with hyperlinks is not appealing.

To developers seeking to claim this bounty:
When developing this, you should probably make a GitHub fork of the repository here as a matter of practicality. The code there can already handle logins, password creation, and dropped connections. There are "DEVAID NOTE" banners at the top of each JavaScript file indicating what needs to be done for each. Finally, everything there is MIT-licensed (even though I didn't explicitly say as such anywhere in the repository).
You might even choose to throw out all of the JS and start anew - but please do fork the repository, since it makes it easier to keep track of progress.

Rules for bounty payment
The control panel must meet the criteria above, which are subject to change (I will keep a changelog and track how much of the bounty is pledged to which version of the criteria).
When the bounty is about to be paid, it will be announced 48 hours in advance. This allows the pledgers time to voice concerns that the finished product does not meet criteria. The bounty will not be paid if 50% of the pledges (by number of BTC) can agree that the control panel is not finished. Anonymous pledges are not counted.

Sorry for leaving the Git repository untouched - I wore myself out on RC1 and needed a break. Getting back to work now!

No promises, but we might be able to get rc2 released in about 24 hours. Changes to be in rc2:

• Better kernel import mechanism (fix bug with phatk2 depending on opencl).
• Some semblance of a PluginInterface.
• jedi95 is making some kernel-level improvements
• Misc. bugfixes (got the Python-on-Linux installer working right, etc)
• Support for submitold (addresses some concerns forrestv had)
• Maybe backup pool support, if it's easy to tackle after this... otherwise we'll add it post-release

And of course, it is a release candidate. If all goes well, rc2 will be the official release version.

-- snip -- (accidentally quoted the main post)

I just checked - the zipfile itself is identical. I'm going to go badger jedi95 to compile a new one.

Sorry about that! Apparently I don't know how to use setuptools correctly.

I just pushed a fix for that problem into the Github repository. You can try that if you like.


A better fix for that problem is to use a function which loads the kernel if it hasn't already been imported. I'm working on that now...

The plan is actually to tell the user to fire up a web browser and have PhoenixWeb run the first-time setup wizard. The only trouble is that PhoenixWeb still needs a lot of work before it's ready to be included in the standard Phoenix download. (Right now it only has enough there for a "real" web developer to pick it up and work on it...)

While both of these features are really nice, there is no easy way to interface with these functions on the card through OpenCL. We can do it, and I've asked jedi95 about it. His stance on the issue is pretty much what lodcrappo said:

So, we're definitely not adding GPU management features to the Phoenix 2 core.


It's important to keep in mind that cgminer and Phoenix are alternatives, not competitors. We're both on the same side here. If you like cgminer better, please, use it! Phoenix's purpose is to do things differently for those that don't prefer the way cgminer operates. (And, Python BS? I'm assuming you mean the dependencies you have to install to get Phoenix operational, since I don't see how choice of language affects the end-user, especially when the core was written with speed in mind.)


Adding OC and fan management is very tempting, I must admit. A thought occurs to me: What if we renamed the "kernels" directory to "modules" or the like, and allowed non-kernel modules to be loaded into Phoenix as well? This allows a third party to easily develop a complete GPU management subsystem that integrates into Phoenix while still keeping the core slim and fast for those who prefer to do OC themselves.

If the phatk kernel were updated to be compatible, it would work. I can't think of any benefit to doing so, though. The phatk2 kernel outperforms phatk on all hardware we've tested with.

You would have to dedicate each GPU to a different Phoenix process to do that. The Phoenix core is currently designed to connect to only one backend.

The Phoenix 2 core itself recognizes (not an exhaustive list):

The phatk2/opencl kernels recognize:


Try:

Yes. The kernels are very similar, so the kernel options are pretty much the same as in Phoenix 1.

If you don't want to autodetect, you can do:

If you do want to autodetect, you can just omit the one that has autoconfigure = True.

That's jedi95's department. He's on it.

Forgot to put that in the first post. I updated the example config file to show how you can do it. You will need to know the device ID of your hardware (cl:PLATFORM:DEVICE) and you can override the autoconfigured settings (or disable autoconfiguration completely) from the config file.