Skip to main content

Supported Ecosystems & Integrations

Acurast is built with interoperability at its core and is able to support various Web3 ecosystems and has multiple ways of being integrated within various environments such as EVM, WASM, Substrate and others.

Supported Ecosystems​

Acurast supports ecosystems that have an active developer community and smart contract environments.

NetworkEnvironmentLevel 1 Integration ↗Level 2 Integration ↗
Aleph Zero Aleph ZeroIn DevelopmentWASM✅❌ *
Arbitrum ArbitrumMainnet, GoerliEVM✅❌ *
Astar AstarMainnet, Shibuya, zKatanaWASM, EVM, zKEVM✅❌ *
Base BaseMainnet, GoerliEVM✅❌ *
Binance Smart Chain Binance Smart ChainMainnet, TestnetEVM✅❌ *
BoB BoBTestnetEVM✅❌ *
Ethereumn EthereumMainnetEVM✅❌ *
Moonbeam MoonbeamMainnet, MoonbaseEVM✅❌ *
Optimism OptimismMainnet, GoerliEVM✅❌ *
Pendulum PendulumTestnetEVM✅❌
Polygon PolygonMainnet, MumbaiEVM✅❌ *
Peaq PeaqkrestEVM✅❌ *
Tezos TezosMainnet, GhostnetTezos✅✅
aeternity æternityIn Developmentæternity✅❌ *

* In Development

Support for additional ecosystems are added on a regular basis.

info

Are you considering an Acurast integration for your ecosystem and have questions?

Reach out to us on [email protected], on Discord or Telegram.

Integration Levels​

Level 1​

With a Level 1 integration, the Acurast Protocol is capable to accept Deployments for the given destination ecosystem e.g., Ethereum smart contract. Developers are creating their Deployment requests through the Acurast Console directly on the Acurast Protocol, funding the rewards with Acurast Tokens. Processors are capable of interacting with the destination directly, signing transactions and injecting them.

A simplified representation of the Level 1 flow:

Level 1 FlowLevel 1 Flow

Key takeaways:

  • Processors can interact with the destination and submit their output
  • Developers create Acurast Deployments through the Acurast Console directly on the Acurast Protocol which requires an Acurast Wallet and Acurast Tokens
  • Developers need to fund transaction fees of the Processors with the asset of the destination ecosystem

Level 2​

A Level 2 integration provides a much improved developer experience and streamlined onboarding. An Acurast Proxy contract is deployed in the destination ecosystem that establishes a bi-directional cross-chain communication channel with Acurast Hyperdrive to the Acurast Protocol. Users e.g. on Ethereum can connect with their Ethereum wallet to the Acurast Console and create a Deployment by interacting with the Proxy contract and rewarding Processors in the native currency. The created request is forwarded to the Acurast Protocol where that matches with eligible Processors that in turn then provide their output to the destination.

A simplified representation of the Level 2 flow:

Level 1 FlowLevel 1 Flow

Key takeaways:

  • Developers create Acurast Deployments through the Acurast Console with a wallet from their ecosystem e.g., Metamask for Ethereum
  • Rewards and transaction fees are paid in a native asset e.g., ETH
  • Acurast Hyperdrive is used for cross-chain communication

Integrations​

Support for Acurast in a Web3 ecosystem can be achieved through various integration approaches:

  • EVM
  • Substrate
  • Substrate with WASM
  • Tezos