GET

Get latest OPoW data

Changed on

Notes

  • Query parameter <block_id> must be the latest block. Use /get-block endpoint

  • Each opow is for a specific Benchmarker. opow.block_data.reward is the reward before any sharing amongst delegators

  • player_details is a map of <player_id> to PlayerDetails

get/get-opow

Request

Query parameters

block_idstring required

Response

Success

player_detailsobject

Map of player_id to PlayerDetails

Example response

{
  "opow": [
    {
      "block_data": {
        "num_qualifiers_by_challenge_by_track": {
          "c001": {
            "n=100": 5,
            "n=200": 3
          },
          "c002": {
            "n=100": 2,
            "n=200": 4
          }
        },
        "num_potential_qualifiers_by_challenge_by_track": {
          "c001": {
            "n=100": 5,
            "n=200": 3
          },
          "c002": {
            "n=100": 2,
            "n=200": 4
          }
        },
        "weighted_self_deposit": "123456789123456789",
        "weighted_delegated_deposit": "123456789123456789",
        "reward_share": "123456789123456789",
        "imbalance": "123456789123456789",
        "influence": "123456789123456789",
        "reward": "123456789123456789"
      }
    }
  ]
}

Changes

    • warning

      removed the optional property from the response with the status

    • info

      added the optional property to the response with the status

    • warning

      removed the optional property /// from the response with the status

    • warning

      removed the optional property /// from the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status