Open JeremyParish69 opened 2 years ago
+1 for more generalization instead of specific to a single vendor — this is good.
Here is my schema suggestion:
"oracle_ids": {
"type": "object",
"properties": {
"coingecko_id": {
"type": "string"
},
"coinmarketcap_id": {
"type": "string"
},
"osmosis": {
"type": "object"
"properties": {
"osmo_spot": {
"type": "number"
},
"atom_spot": {
"type": "number"
},
"usd_spot": {
"type": "number"
},
"other_spot": {
"type": "number"
},
"largest_spot": {
"type": "number"
}
}
}
}
}
wouldn't be too difficult to transform existing data to match this schema...
currently, we allow for
"coingecko_id"
for each asset, but what about other price oracles, like CoinMarketCap, or Dex spot prices, like Osmosis' OSMO/asset spot price?we could have a generic price oracle object that contains the id for coingecko, as well CMC and Osmosis and others. E.g.,:
This is what we have now: