PoolServerJ: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
Shads (talk | contribs)
No edit summary
Shads (talk | contribs)
Add forum thread links
Line 19: Line 19:


* [http://poolserverj.org/about/ PoolServerJ Homepage]
* [http://poolserverj.org/about/ PoolServerJ Homepage]
* http://forum.bitcoin.org/index.php?board=14.0
* [http://forum.bitcoin.org/index.php?topic=33142.0 Forum Thread]
* [http://forum.bitcoin.org/index.php?topic=33144.0 Tech Support Thread]


[[Category:Mining]]
[[Category:Mining]]
[[Category:Pool_Operators]]
[[Category:Pool_Operators]]

Revision as of 07:17, 31 July 2011

PoolServerJ is a pure java implementation of a Bitcoin mining pool server. It’s functionally very similar to pushpoold. Although there are some differences it is capable of being swapped over with pushpoold without any config changes.

Features

  • Work caching – caches work from bitcoind to handle short term spikes in requests
  • DoS resilience with QoS support to ensure workers who’ve submitted valid work are serviced with priority
  • Capable of pulling work from multiple bitcoin daemons to get around the getwork bottleneck and also to provide some redundancy
  • Notify of block change via HTTP to a user configurable URL to support event triggered share processing
  • Cached database handling (optional) to reduce round trips.
  • Supports Mysql, Postgresql, sqlite3 (JDBC based so others can be added easily – currently only tested on mysql)
  • Runs as a Windows service
  • Longpolling support
  • Integrated block monitoring using all available bitcoin daemon work sources
  • Dump shares to Database, log file or stdout
  • Safe restart – shares issued to client are dumped to file on shutdown and reloaded on startup so your miners won’t get stale shares if you restart a live server
  • Only dependency is a Java 6+ JDK.

Links