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 central idea very early on was to inform users about transfers, invitations, etc. via email or Twitter or at least on GitHub (that's what this issue is about: #28). The oracles are the entities sending the actual notifications. That means they need to have access to an Octobay GitHub bot account, the Twitter account and some mail credentials. Individual accounts are also possible.
Is it even necessary to let the oracles do that? In my first ideas I saw an oracle as more than just any other CL oracle that happens to serve an Octobay adapter but more as a central part of a decentralized/redundant/trust-minimized nature of the project. In other words I don't want Chainlink oracles... I want Octobay oracles, built on top of Chainlink oracles and use them as our own "cloud" for whatever purposes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A central idea very early on was to inform users about transfers, invitations, etc. via email or Twitter or at least on GitHub (that's what this issue is about: #28). The oracles are the entities sending the actual notifications. That means they need to have access to an Octobay GitHub bot account, the Twitter account and some mail credentials. Individual accounts are also possible.
Is it even necessary to let the oracles do that? In my first ideas I saw an oracle as more than just any other CL oracle that happens to serve an Octobay adapter but more as a central part of a decentralized/redundant/trust-minimized nature of the project. In other words I don't want Chainlink oracles... I want Octobay oracles, built on top of Chainlink oracles and use them as our own "cloud" for whatever purposes.
On the other side existing operators won't likely open up their setup to support extra features, like serving an API.
See also: https://github.com/Octobay/chainlink-adapters/blob/main/endpoints/notify.js
Beta Was this translation helpful? Give feedback.
All reactions