Skip to content
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.

Add nextNetworkBits and nextNetworkTarget to /api/pools #443

Merged
merged 1 commit into from
Oct 25, 2018

Conversation

bitspill
Copy link
Contributor

Adds the bits/target of the next network block to the pool.networkStats section of the api/pools API

These additional datapoints were necessary for a FLO application but could perhaps be generally useful for debugging or other mining related analysis

Example:

      "networkStats": {
        "networkType": "Test",
        "networkHashrate": 10547.259085580305,
        "networkDifficulty": 0.000244137132,
        "nextNetworkTarget": "00000fffff000000000000000000000000000000000000000000000000000000",
        "nextNetworkBits": "1e0fffff",
        "lastNetworkBlockTime": "2018-10-25T15:41:49.5252676Z",
        "blockHeight": 254062,
        "connectedPeers": 16,
        "rewardType": "POW"
      },

@oliverw oliverw merged commit 21cc538 into oliverw:dev Oct 25, 2018
@bitspill bitspill deleted the extraStats branch October 25, 2018 16:20
oliverw pushed a commit that referenced this pull request Oct 25, 2018
* Ethereum geth compatibility fixes
* Added missing await for miner performance API endpoint. Fixes #441.
* Add nextBits and nextTarget to pool.networkStats (#443)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants