-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for Self-hosted API Support, such as Cardano db-sync #5
Comments
Hi. For now, we support Ergo Node and Cardano Ogmios which is an interface via JSON/RPC for cardano-node. You don't need to use Cardano db-sync to self-host the API calls, instead, you can run an ogmios instance that offers a WebSockets API. |
I asked because for BALNC stake pool we already have a full node and db-sync, so it would be super cool to run the watcher independently. So if we know the specific API web sockets we can create our own Rosenbridge API. We are trying to find where that definition lives. |
It is my understanding that Watchers can access the Cardano network via Koios URL (api endpoints), is this correct? If yes, then would it be possible to utilizes a different URL that provides the same API endpoints? We currently have Cardano API endpoint service that is capable of providing the same endpoints as Koios, but would like to know if using a (non Koios) API url would be possible or not. Thanks so much for your support! |
Some more background information here: the Watchers in question here would be on a completely separate network and in different geographical location than the cardano nodees supporting the BALNC pool. The Watchers do not have ability to communicate directly (websocket) with the BALNC pool relay nodes. |
Instead of relying on Koios and Ogmios, for those of use who run an Ergo Node index on, and Cardano db-sync, can we get support to self-host the API calls to be a watcher.
This would support independent and even more decentralized watching.
More specifically, which Koios api endpoints are required by the Rosen Bridge watcher?
The text was updated successfully, but these errors were encountered: