You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note here that the contract itself doesn't check if the published prediction actually exists on Omen. We expect that paying fees to upload fake results isn't worth it, because in the end you can query this subgraph based on available markets on Omen (not the other way around) and then fake answers would be just ignored anyway.
The fields are:
marketAddress
The market ID/address this is for.
publisherAddress
Public key that published this prediction.
estimatedProbabilityBps
Probability in basic points for p_yes that agent predicted. 2000 is 20%.
Please note here that we are considering support of arbitrary categorical markets. Ie not just YES/NO markets. So theoretically this field could change to something more universal then only p_yes, if you can somehow account for that it'd be great but we will of course inform you if we would do such a breaking change.
txHashes
Each prediction can be associated with multiple trades on Omen. E.g. based on one prediction, agent can first sell his current positions and buy a new one.
In your history tab we can see that this is happening quite often, that's why txHashes is a list of hashes. You can use these hashes to match these predictions with trades.
ipfsHash
IPFS file with more details. We store only most required stuff on contract (fields above). This file will contain additional details. Currently, it is JSON representation of this Pydantic model. So it will look like
{
"agent_name": "PredictionProphetGPT4o",
"reasoning": "Based on Google news X, Y, Z I predict that A will happen with P probability. Blah blah."
}
Please note that this file could change, please handle that agent_name or reasoning could be completely missing there or null or something. Also the whole ipfsHash could be missing and be just NULL_BYTES.
The text was updated successfully, but these errors were encountered:
Hey team,
we have a new contract 0x260E1077dEA98e738324A6cEfB0EE9A272eD471a and associated subgraph.
If you query the subgraph, you will get data like
Please note here that the contract itself doesn't check if the published prediction actually exists on Omen. We expect that paying fees to upload fake results isn't worth it, because in the end you can query this subgraph based on available markets on Omen (not the other way around) and then fake answers would be just ignored anyway.
The fields are:
marketAddress
The market ID/address this is for.
publisherAddress
Public key that published this prediction.
estimatedProbabilityBps
Probability in basic points for p_yes that agent predicted.
2000
is20%
.Please note here that we are considering support of arbitrary categorical markets. Ie not just YES/NO markets. So theoretically this field could change to something more universal then only
p_yes
, if you can somehow account for that it'd be great but we will of course inform you if we would do such a breaking change.txHashes
Each prediction can be associated with multiple trades on Omen. E.g. based on one prediction, agent can first sell his current positions and buy a new one.
In your history tab we can see that this is happening quite often, that's why
txHashes
is a list of hashes. You can use these hashes to match these predictions with trades.ipfsHash
IPFS file with more details. We store only most required stuff on contract (fields above). This file will contain additional details. Currently, it is JSON representation of this Pydantic model. So it will look like
Please note that this file could change, please handle that
agent_name
orreasoning
could be completely missing there or null or something. Also the wholeipfsHash
could be missing and be just NULL_BYTES.The text was updated successfully, but these errors were encountered: