Oracle Ecosystem Initiative
Oracle Ecosystem Initiative - Acurast
The oracle problem is considered to be the Achilles heel of public blockchains. As more complex and intricate systems are built on permissionless blockchains, the importance of Oracles grew as well since most complex economic interactions require some external data source. Achieving a trustless and decentralized oracle solution is challenging, and several approaches have emerged, with many of them reintroducing Trusted Third Parties (TTP) and thus undermining the permissionless design principles.
The Current Challenge In The Ecosystem
The Polkadot ecosystem has seen multiple attempts to establish a feasible oracle solution, e.g., Chainlink announcing the support of a Pallet for Substrate (Polkadot SDK) chains. Unfortunately, in this example, the agreed upon support was never established in a production setting and the maintenance and support of the Pallet was discontinued.
Even though there exist oracle solutions (e.g., Redstone, Chainlink) covering multiple different environments, most of these solutions lack support and coverage of the Polkadot ecosystem.
It is time to establish a solution supporting Substrate (Polkadot SDK), EVM, and WASM. It is time for a feasible solution that does not rely on a centralized party or setup, but one that offers minimized trust assumptions based on strong cryptography and the latest advances in secure hardware, offering the flexibility to seamlessly expand new price feeds without additional roadblocks.
About Acurast
Acurast provides a zero trust, off-chain Execution Layer based on secure mobile hardware to create a trustless and confidential computation environment. In connection with a Substrate (Polkadot SDK) based chain responsible for permissionless orchestration of computational request.
Context of the proposal
- Establish an ecosystem-wide solution for oracles accessible in three distinct environments: Substrate (Polkadot SDK), EVM and WASM
- Provide price feeds for all Polkadot and Kusama assets, other popular crypto assets and Real-World Assets (RWA).
- Establish an ecosystem-wide solution with these integrations that can be leveraged by every Polkadot-based project, utilizing a third-party audited solution.
- Provide support to projects to integrate price feeds into their environments
- Add support for new asset classes as price feeds.
- Provide access to larger off-chain compute resources for additional use cases.
Voices From The Ecosystem
Some ecosystem feedback on this proposal:
“Given how Tanssi is building an infrastructure protocol to facilitate appchain deployments as much as possible, tools like oracles are essential for many use cases within the ecosystem. Acurast standardizing oracle solutions via a pallet will allow developers to include price feeds within their runtimes in a practical way, and it's highly complementary to what we're building at Tanssi.”
Francisco Javier Agosti, Founder and CEO of Moondance Labs
“Acurast and Astar have been collaborating, in adding support for price feeds through Acurast and bringing them to Astar. An ecosystem wide solution, like Acurast is proposing, will not only improve the developer experience on Astar EVM and WASM but the broader Polkadot ecosystem.”
Maarten Henskens, Head of Astar Foundation
We would love to get your feedback on this proposal. Find more details in the full proposal
Comments (4)
Comments (4)
Our real estate lending and asset tokenisation project... the Xcavate appchain (currently on the Tanssi testnet) needs reliable decentralised Oracles to check real world data such as property / land ownership, planning permission approval and real time property prices. We've used the Acurast system and its really helped our project go through successful testing phases. We are just about to enter another phase requiring an additional Oracle to execute an API to create a SPV for each property. If our ecosystem is to grow, then we need these helpful tools with a dedicated team to drive continuous improvement.
The Polkadot ecosystem needs a viable and well maintained oracle and it becomes more important if it's a native project. The doors are open for oracle projects from other ecosystems but we're glad to see an oracle project using the polkadot-sdk technology.
Some questions:
-
We noticed you guys have your own cumulus / substrate / polkadot-sdk based code. Expanding the services to other ecosystems is great, encouraged and good for business like Axelar and others have proven already. But do you have plans to continue developing on the polkadot-sdk, using the Polkadot relay chain and more importantly, you guys plan to remain in the ecosystem to develop here for the foreseeable future or do you have plans to pivot away to other technologies at any point in time?
-
Is there any plan to push for adoption of Acurast use into more active projects and potential projects within Polkadot?
-
What are the plans for reporting the progress of this proposal? Monthly? Quarterly? At the end all at once?
-
Any plans for a path to Integration of PolkaVM?
-
It is correct to assume that this funding will cover the implementation of all the proposed deliveries (including pallet/EVM/WASM integrations, etc.) as well as support for 12 months?
-
How confident do you guys feel that you are going to deliver all the proposed deliveries within your proposed timeframe?
We have voted AYE in the meantime, we'll change it if we seem fitting or if new important information arises regarding this proposal.
Looking forward to your answers.
Our real estate lending and asset tokenisation project... the Xcavate appchain (currently on the Tanssi testnet) needs reliable decentralised Oracles to check real world data such as property / land ownership, planning permission approval and real time property prices. We've used the Acurast system and its really helped our project go through successful testing phases. We are just about to enter another phase requiring an additional Oracle to execute an API to create a SPV for each property. If our ecosystem is to grow, then we need these helpful tools with a dedicated team to drive continuous improvement.
The Polkadot ecosystem needs a viable and well maintained oracle and it becomes more important if it's a native project. The doors are open for oracle projects from other ecosystems but we're glad to see an oracle project using the polkadot-sdk technology.
Some questions:
We noticed you guys have your own cumulus / substrate / polkadot-sdk based code. Expanding the services to other ecosystems is great, encouraged and good for business like Axelar and others have proven already. But do you have plans to continue developing on the polkadot-sdk, using the Polkadot relay chain and more importantly, you guys plan to remain in the ecosystem to develop here for the foreseeable future or do you have plans to pivot away to other technologies at any point in time?
Is there any plan to push for adoption of Acurast use into more active projects and potential projects within Polkadot?
What are the plans for reporting the progress of this proposal? Monthly? Quarterly? At the end all at once?
Any plans for a path to Integration of PolkaVM?
It is correct to assume that this funding will cover the implementation of all the proposed deliveries (including pallet/EVM/WASM integrations, etc.) as well as support for 12 months?
How confident do you guys feel that you are going to deliver all the proposed deliveries within your proposed timeframe?
We have voted AYE in the meantime, we'll change it if we seem fitting or if new important information arises regarding this proposal.
Looking forward to your answers.