migrated to objects page

GET

fetch a table about all paths' status (available or not)

{
    "path1": true, // response of path1
    "path2": false, // response of path2
                 // ...
    "pathN": {}, // response of pathN
}

migrated to config page

migrated to pool page

migrated to miner page

TODO

We are recommend to deploy different algorithm stratum port with different mining pool instance, so it means the frontend page have to deal with multi-api-server circumstance.

• GET

Get all algorithms

• POST

POST on '/algorithm' is meaning for being compatible multi-algorithms coins

{
    "name": "scrypt",
    "variant": "ltc-origin",
    "blobType": ""
}

the lucky table

lucky = 1 / effort

More lucky means more benefit when same hashrate

• GET

{
    "1d": 0.99,
    "7d": 1.01,
    "1m": 1.11
}

• POST

e.g.

request with body, aiming to fetch luckies between these 14 days.

{
    "start": "1-Jan-2020",
    "end": "10-Jan-2020"
}

pool returns a list

["1.1", "1.11", "0.9", "0.98", "0.7", "1.5", "1.11", "0.9", "0.98", "1"]

the effort table

effort = 1 / lucky

More lucky means more benefit when same hashrate

• GET

{
    "1d": 1.01,
    "7d": 0.99,
    "1m": 0.91
}

• POST

e.g.

request with body, aiming to fetch efforts between these 14 days.

{
    "start": "1-Jan-2020",
    "end": "10-Jan-2020"
}

pool returns a list

["1.1", "1.11", "0.9", "0.98", "0.7", "1.5", "1.11", "0.9", "0.98", "1"]