I was out of internet for the weekend, I'm working on that, long report will be later. Mining works again, payouts are stopped, analyzing troubles.

Edit: Payouts working, need to go sleep. I'll write report tomorrow.

Not sure how much lucky you really are - this block is invalid . Hash has been found faster than bitcoind distributed information about new bitcoin block on p2p network.

And we're telling you that if you show the code (which is no-loss for you), you will have much more users and potential donations, too.


There is almost 0% chance that WinRAR contains code stealing bitcoins. On the oposite, simple tool for Bitcoin made by unknown developer has very high probability that is malicious (as we already had those issues). The chance is even higher when the developer refuse to open his code, althought there is probably nothing magical inside which should be kept private (like special intelectual property about how to download json data and display them in window with custom skin).

I think that I wrote enough and other people can decide if they want to use your app and take the risk or not, so this discussion is over for me.

I found that phoenix isn't using keep alive, but for every RPC call it open separate connection. I'm pretty sure that's the reason for troubles connecting to my pool; I introduced pretty strict rules after last DoS attacks, but using keep-alive in miners, people should not hit those limits at all (at least not with few rigs from one IP).

As this issue affect my pool, I offer 15 BTC to anybody who pull keep-alive patch for phoenix (in fact it should be relatively simple as phoenix is coded clearly).

Guys, this is *bitcoin analysis* thread, not 4chan.

nextshare wrote me the feature request today, worker status is currently only missing API, which is not so hard. So yes, I'll support that.

Well, that's not absolutely correct. People _see_ block payments immediately, but also have to wait 120 blocks till it mature (or 100 blocks with hacked bitcoin client).

...and I promised that I'll test it soon .

Maybe I'm paranoic, but using this type of closed sources utilities targeted to bitcoin are high-risk business for me. There is no reason to _not_ show the code, except it is doing something nasty or you're shy for your codebase.

Please don't take it personally, but:
1) You offering simple tool which does almost nothing except downloading one or two json files from the net.
2) This tool have full access to computers with (probably) thousands of bitcoins.
2) You are absolutely unknown entity for us.
3) You're refusing to show sources for no obvious reason (is there anything valuable in the sources?) and explaining that as "MS/Apple are also closed source"

Maybe you're just shy for your codebase, which I understand, but maybe you're just another script kiddie who want to 'earn' bitcoins easily. Who knows?

Good idea, if you add hooks to correct places, I can collect some logs for further investigation...

I tried it on my two rigs and had this problem, too. It must be specific to the miner, because I used diablo and poclbm without any problem before.

Once I started at least one phoenix miner, other miners on second machine suddenly stopped working. More phoenix miners on the same machine works without problem. I tried to stop pool's firewall (where are some advanced anti-DoS techniques enabled), but no difference. Currently I have absolute no idea where the problem can be and problem indices sounds really weird. My two rigs aren't linked together in any way, they are even mining under separate pool accounts and I have no other limitations on the pool except the firewall. As this problem occured only with phoenix, there must be _something_ different than in other miners... Still no idea?

But users still need to run blackbox on they computers, so I call for cautiousness...

jedu95, thanks for new very fast miner. I have one question - many users complaining about connection troubles while using more computers with my pool. Do you have any idea why it should not work? All other miners - poclbm, diablo, jgarzik etc does not have such problem. I don't have any limits on RPC connection, so I don't see the reason why it should not work... Thanks for your reply in advance.

Yes, "forgot password" feature on login page.

We talk about upgrading to the newest bitcoind all the time .


Well, they are custom patches like "don't close rpc connection after every request" or "report current block number in getwork response" and so on, which is not needed for other deployments outside the pool. There are also some custom patches from other people (like jgarzik's settxfee or m0mchil's getwork lockup solution), which are publicly available, but are not in main source tree (yet).

Are sources available? I'm suspicious in tools like this, we already had virus in closed source tool for  Bitcoin wallet backups which sent wallet.dat over Internet.  Also, this is first post of tool author on this forum...

Yes, everything is fully automatic, but payment processing is done once every hour. So please be patient, if your confirmed reward is >= 0.5 BTC, your threshold is 0.5 BTC and you have correct wallet address on profile page, it will be processed soon.

Which status?

Currently there is no explicit API, but it is pretty easy to use form POST to right URL...

I'm probably not going to make an API, because every time I had request to this, people told me they are going to do some kind of botnet. As I don't like it, I don't plan to support it by APIs.

If everything works except website, it looks like problem with site rate limiter. People started to complaining when I turned it on, maybe there is some problem inside and I should investigate a little... :-/.