-
Notifications
You must be signed in to change notification settings - Fork 119
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
Oracle Communication Layer #2364
Comments
Is this the plan to replace the current StateRelayer I'm working on? |
Hi Cuong! Thanks! |
StateRelayer is in its final state of development, I am trying to finish several last pull requests. |
Hey @dcorral, thanks for making an issue on this. The current ecosystem level solution: The state relayer project https://github.com/BirthdayResearch/StateRelayer (and any other community projects of the same nature). It's a just a dApp solution, so anyone should be able to redeploy the same according to their parameters or tweaked versions of this as needed. The protocol level solutionThe DeFiChain protocol will eventually have it's own set of intrinsic contracts (The current Key challenges to be resolved first
Depending on which of these we tackle first, the timelines for these would change. So, the more effective route is to focus on transparent state oracle projects on EVM side that can bridge the gap, until the protocol based solution is ready. |
Hi @prasannavl, thank you for the update. The StateRelayer example is not an option. We are looking for a trustworthy source of the DeFiChain Oracle data, we can't push the updates ourselves. This would remove any decentralisation. I mean we could deploy something like https://tellor.io/ on the dmc, but this feels completely wrong because we would build around the native defichain oracles, which is one of the main features of the chain... A bridge solution is also not really an option if the protocol should be immutable. There is no way to swap the price feed after deployment. Is it possible for you to specify the timeline a bit? Are we speaking about Q1-Q2 2024, or is it more about Q1 2025? |
Closing stale / outdated issues. |
Summary
Rationale
The text was updated successfully, but these errors were encountered: