This Flask server is configured to serve the outputs of the PTN repo (Bittensor subnet 8), which generates files accessible via this API. This is needed so that validators can provide PTN data to consumers.
The Flask code can easily be modified to serve outputs from any other Bittensor subnet.
The API uses a simple token-based authentication system. The default API key is set to "xxxx".
Change the default API key in the accessible_api_keys list in serve.py to a more secure key before deploying in a production environment to prevent unauthorized access.
By default, the server binds to 127.0.0.1 which only allows local requests. To allow access from any IP address, bind to 0.0.0.0:
serve(app, host="0.0.0.0", port=48888)On your validator, clone this repo in the same directory that the proprietary-trading-network repo is in, make desired edits, and then run
pm2 start serve.py --name serveIf you are using the repo as a standalone solution that does not leverage the Request Network, you will need to consider several factors in your custom implementation.
Consider implementing rate limiting using out of the box Flask extensions like Flask-Limiter or custom implementations to prevent abuse and ensure fair use of the API.
Deploy the Flask application over HTTPS in production to encrypt data in transit. This is typically done by placing the Flask application behind a reverse proxy that handles SSL/TLS termination.
Configure firewall rules to only allow traffic on necessary ports from trusted IP addresses.
@app.route("/miner-positions", methods=["GET"])
This endpoint retrieves the positions of all miners, optionally filtered by a specified data freshness tier. The tier parameter can be one of the following values: ['0', '30', '50', '100'].
Parameters: tier (optional): Specifies the data freshness tier.
- 0: 100% of positions show data with a 24-hour delay.
- 30: 30% of positions show real-time data, 70% show data with a 24-hour delay. (superset of tier 0)
- 50: 50% of positions show real-time data, 50% show data with a 24-hour delay. (superset of tier 30)
- 100: 100% of positions show real-time data. Equivalent to not providing a tier. (superset of tier 50)
If no tier is provided, the response will be a raw JSON file with the following schema:
{
"5C5GANtAKokcPvJBGyLcFgY5fYuQaXC3MpVt75codZbLLZrZ": {
"all_time_returns": 1.046956054826957,
"n_positions": 15,
"percentage_profitable": 0.8666666666666667,
"positions": [
{
"average_entry_price": 0.59559,
"close_ms": 1714156813363,
"current_return": 1.0002165919508386,
"initial_entry_price": 0.59559,
"is_closed_position": true,
"miner_hotkey": "5C5GANtAKokcPvJBGyLcFgY5fYuQaXC3MpVt75codZbLLZrZ",
"net_leverage": 0.0,
"open_ms": 1714139478990,
"orders": [
{
"leverage": -0.1,
"order_type": "SHORT",
"order_uuid": "18ca3cdf-b785-4f88-90a9-d2c06e8653b1",
"price": 0.59559,
"price_sources": [],
"processed_ms": 1714139478990
},
{
"leverage": 0.0,
"order_type": "FLAT",
"order_uuid": "c902c428-fcfb-43ca-ab79-117c957dbbfa",
"price": 0.5943,
"price_sources": [],
"processed_ms": 1714156813363
}
],
"position_type": "FLAT",
"position_uuid": "1f3f427f-6cbe-497c-af11-2fbef2ca3c10",
"return_at_close": 1.0002095904346948,
"trade_pair": [
"NZDUSD",
"NZD/USD",
7e-05,
0.001,
500
]
},
...
Hotkeys are mapped to a data dict. The data dict contains positions which contain orders.
- miner_hotkey: A unique identifier for a miner. This is the same as the Bittensor metagraph hotkey value.
- all_time_returns: The miner's total return on investment across all positions over all time.
- n_positions: The number of positions held by the miner.
- percentage_profitable: The proportion of the miner's positions that have been profitable.
- positions: A list of individual trading positions held by the miner.
- average_entry_price: The average price at which the miner entered the position.
- current_return: The current return on the position with no fees.
- return_at_close: The return on the position at the time it was closed with all fees applied.
- initial_entry_price: The price at which the position was first opened.
- is_closed_position: Indicates if the position is closed.
- net_leverage: The leverage currently used in the position. 0 if the position is closed.
- open_ms: The timestamp (in milliseconds) when the position was opened.
- close_ms: The timestamp (in milliseconds) when the position was closed. 0 if not closed.
- orders: A list of orders executed within the position.
- leverage: The leverage applied to the order.
- order_type: The type of order (e.g., SHORT, LONG, FLAT).
- order_uuid: A unique identifier for the order.
- price: The price at which the order was executed.
- price_sources: Used for debugging. Info about the sources used to determine the price. At the time of this writing the sources are Polygon and TwelveData.
- processed_ms: The timestamp (in milliseconds) when the order was processed.
- position_type: The current status of the position (e.g., FLAT, SHORT, LONG).
- position_uuid: A unique identifier for the position.
- trade_pair: Information about the trade pair (e.g., currency pair BTCUSD).
If a tier is provided, the response will be a gzipped JSON file with the above schema but with data freshness adjusted according to the specified tier. This allows different pricing tiers for data sales and enables more bandwidth-efficient data transfers due to gzip compression.
@app.route("/miner-positions/", methods=["GET"])
Similar to the above endpoint but only returns the data dict for the specified hotkey. The returned payload is a raw json file.
@app.route("/miner-hotkeys", methods=["GET"])
Returns all the hotkeys as seen in the metagraph from the validator's perspective.
@app.route("/statistics", methods=["GET"])
Returns the statistic relevant for scoring miners. These statistics are also consumed by the Taoshi dashboard for visualization purposes.
@app.route("/statistics//", methods=["GET"])
Returns the statistic relevant for scoring the specified miner.
@app.route("/eliminations", methods=["GET"])
Which miners are eliminated according to this validator. This is the same information visualized on the Taoshi dashboard.
Schema:
"eliminations": [
{
"dd": 0.0,
"elimination_initiated_time_ms": 1711184954891,
"hotkey": "5Dk2u35LRYEi9SC5cWamtzRkdXJJDLES7gABuey6cJ6t1ajK",
"reason": "LIQUIDATED"
},
{
"elimination_initiated_time_ms": 1711204151504,
"hotkey": "5G1iDH2gvdAyrpUD4QfZXATvGEtstRBiXWieRDeaDPRfPEcU",
"reason": "PLAGIARISM"
},
{
As of writing, the only ways to be eliminated are:
- Being liquidated (portfolio value goes to 0)
- Plagiarizing another miner
- Failing the challenge period
More information can be found here: https://github.com/taoshidev/proprietary-trading-network/blob/main/docs/miner.md#miner
@app.route("/miner-copying", methods=["GET"])
Automatically-generated plagairsm scores per miner. Coming soon
@app.route("/validator-checkpoint", methods=["GET"])
Everything required for a validator to restore it's state when starting for the first time. This includes all miner positions as well as derived data such as perf ledgers, challenge period data, and eliminations.
Perf ledger schema:
"perf_ledgers": {
"5C5GANtAKokcPvJBGyLcFgY5fYuQaXC3MpVt75codZbLLZrZ": {
"cps": [
{
"accum_ms": 21600000,
"gain": 0.12586433994869853,
"last_update_ms": 1714161050595,
"loss": -0.12587360888356938,
"n_updates": 17213,
"open_ms": 21599768,
"prev_portfolio_ret": 0.9999907311080851
},
{
"accum_ms": 21600000,
"gain": 0.017040557887505504,
"last_update_ms": 1714182650595,
"loss": -0.016984326534111933,
"n_updates": 2219,
"open_ms": 21599768,
"prev_portfolio_ret": 1.0000469635212756
},
{
...Perf ledgers are built based off realtime price data and are consumed in the scoring logic. More info in the PTN repo.
Example curl commands to interact with the Flask server. Replace <server_ip> with your validator's IP address and xxxx with your API key that you hardcode in serve.py
curl -X GET http://<server_ip>:48888/miner-positions -H "Content-Type: application/json" -d '{"api_key": "xxxx"}' -o miner_positions.jsoncurl -X GET 'http://<server_ip>:48888/miner-positions?tier=0' -H "Content-Type: application/json" -d '{"api_key": "xxxx"}' -o miner_positions.json.gzcurl -X GET http://<server_ip>:48888/validator-checkpoint -H "Content-Type: application/json" -d '{"api_key": "xxxx"}' -o validator_checkpoint.jsonExample python code to interact with the Flask server.
import requests
import json
url = 'https://example.com/validator-checkpoint'
api_key = 'abcdefg'
data = {
'api_key': api_key
}
json_data = json.dumps(data)
headers = {
'Content-Type': 'application/json',
}
test = requests.get(url, data=json_data, headers=headers)
print(test)
with open('validator_checkpoint.json', 'w') as f:
f.write(json.dumps(test.json()))
# print(json.loads(test.json()))The Request Network is a Taoshi product which serves subnet data while handling security, rate limiting, data customization, and provide a polished customer-facing and validator setup UI. Running this repo is a pre-req to serving data on the Request Network.