Eligius has, to my knowledge, more publicly exposed data about the pool and miners than any other pool, be it on the stats page, the API, or elsewhere.
Historic API JSON files
- Static files updated at reasonable intervals
- Written by the reward system code directly
- With Eligius's popularity growth, are admittedly cluttered (lots of users)
- Available at http://eligius.st/~luke-jr/raw/7/
- Up-to-date balance data for all pool miners, old and new.
- Values for Bitcoins are in "Satoshis" (0.00000001 BTC or 0.0001 TBC)
- everpaid - The all time total amount actually paid to the miner's address by the pool (via generation or manual payouts)
- balance - The current balance that the miner has at the pool INCLUDING ESTIMATES FOR EARNINGS FOR THE CURRENT ROUND
- credit - The total amount of shelved shares (and old SMPPS extra credit, if older miner from that time) that this miner has
- oldest - Unix timestamp for the oldest unpaid balance this user has (ususally the timestamp of the users last payout)
- newest - Unix timestamp for the latest balance change (new share submitted, or old shelved paid)
- last_balance_update - Unix timestamp for the last time the users not-estimated balance officially changed (usually the time of the last pool block submission)
- included_balance_estimate - Amount that was added to the balance field that is the estimated earnings for the current round only (not actually earned/rewarded yet)
- included_credit_estimate - Same as above, except for the credit field
- Updated roughly every few minutes
- Other data available to the reward system and exposed
- Currently only the amount of shares at various intervals is available, per user.
- The fields under shares for each user are labeled as intervals in seconds
- The values are the number of accepted shares (adjusted to pool difficulty 1) in that recent timeframe for that user.
- The footer value is the pool-wide total
- Note: known floating point addition issue here makes the pool-wide total off by as much as about 0.5%. (negligable)
- Updated about every minute.
- A simple list of addresses who have reached the payout queue, in order from oldest balance to newest
- Can be correlated with balances.json easily.
- The output from the coinbaser for the pool that is currently being mined for the generation transaction for miner payouts.
- Data similar to balances.json, except a snapshot at the time of the specific block mining.
- Includes date orphaned blocks
- All other files may be outdated/depreciated.
New per user hashrate API
- Example: http://eligius.st/~wizkid057/newstats/hashrate-json.php/1EXfBqvLTyFbL6Dr5CG1fjxNKEPSezg7yF
- Output in JSON. Format explained here in github: https://github.com/wizkid057/wizstats/pull/25
More to come. :)