I'd like to announce BitToll, a small project I've been working which allows you to do bitcoin transactions in a very small period of time ~200ms designed for automated usage.

The docs are online at https://www.bittoll.com

BitToll Overview
=====================================
 - Allows you to do transactions inside a node.
 - Payments are requested (Tolled) and then paid, rather then money being sent directly.
 - Can withdraw money on the server to the bitcoin network and deposit bitcoins inside of the server
 - Has a bitcoin pool inside of it to allow for clients with no bitcoins to generate them and pay small tolls.


If you'd like to take a look at the source code its all online at
https://github.com/c00w/bittoll

@Subo1977

I'm pretty sure the reason running as root breaks everything is due to a bug in btcnet_info. I'd advise you to update your bithopper version and then run

python setup.py install

I also want to try and clean up the pool list and just streamline everything down to the bare basics. I also want to make the statistics gathering engine much more powerful so this is more useful for server owners.

Its not completely dead. I was pretty busy this summer and didn't have a lot of time to get around to it. I've fixed p2pool in the 0.3.2 branch and I'm going to merge it into master since its the only branch I want to deal with anymore. I'm not sure about some of my other decisions regarding moving everything into a stats.db file. I'm going to try and integrate a dht into bithopper to help with the deepbit lp problem.

The top issue is fixed. I'm not sure what is breaking with the bottom issue.

A bug was found and fixed. If you had random workers not working after you removed a server they should start working again.

@everyone who wants features added.

Just send me a PM or open an issue on github. I've just been busy and not monitoring this thread since I thought it died.

There is a 1% default donation. Its implemented such that 1 out of every 100 blocks is sent to a donation address instead of a server you selected. So from your end it should be transparent.

I added everything bitHopper supports that isn't an alternate coin and doesn't require a dedicated client like p2pool.

So there are pools that are hoppable and pools that aren't. Its much more of a fancy proxy although it does pool hop if you have hoppable pools.

BTCProxy.net

• Proxy Pool
• Automatic Fail Over Between Pools In Case Of DOS
• Pool Hopping
• Easy one button setup for a couple pools
• 35 pools supported

Questions, Comments?

@Transisto
You didn't set a role for one of your pools.

@transisto
Are you using the latest version? That looks like a bug that was fixed at least ~20 commits ago.

Type git pull to update to the latest version.

@Those errors with lagging:
That should be fixed.

mine_force makes the scheduler mine that pool.

mine_lp_force makes the scheduler mine that pool until it recieves a new lp than it changes the role until the default role.

Oh and mine_lp_force is added and mine_lp is now in place of mine_deepbit.

Shoot. Did it come back alive after that? Or was it just dead.

And what version?
If you are unsure git describe will tell you.

leever: There was a bug with the error output display. Can you update to the latest version and see what error appears?

What version are you using?

leveer can you post what exceptions appears?

And versions are just git tags. So if your are pulling you'll be on the latest version.

Getwork issues should/may be fixed. Also we should reuse connections properly now.

When it says x is not working it means the options themselves. The underlying code does work we just don't have it checking the options yet.