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
A simple (optional: stake weighted) oracle protocol operates in the following phases:
Observe data from off-chain source
Attest to that data by signing on it
Broadcast the signed payload to its peers -- this can happen either on a fixed interval basis, or triggered as a response to an external action e.g. an onchian event being emitted as a result of the "request / callback" pattern, frequently seen in ChainLink or Axiom-style contracts
Track signatures
Once it hits quorum of signatures, send it out either directly to the place where the data will trigger an action (i.e. it handles also being a "keeper", e.g. submitting the signed oracle 2-of-3 multisig data to a smart contract's callback function, or even archiving it to blobs) or it proceeds to expose it over an (optionally authenticated) API to a user querying it, for self-relaying.
A simple (optional: stake weighted) oracle protocol operates in the following phases:
Originally posted by @gakonst in #18 (comment)
Tasks
The text was updated successfully, but these errors were encountered: