Skip to main content

Oasis Privacy Layer (OPL)

The Oasis Privacy Layer (OPL) is a powerful solution that enables developers to integrate privacy features into their decentralized applications (dApps) across multiple EVM-compatible networks.

  • Privacy-First: OPL leverages the Sapphire's privacy features to ensure that contract data and computation remains confidential.
  • Cross-Chain Compatibility: OPL is compatible with multiple blockchains through message bridging protocols, making it easy to integrate privacy regardless of the chain your dApp is built on.

For more information about OPL and to catch the latest news, please visit the official OPL page.

How OPL Works

The OPL is made possible through message bridges, which enable secure communication between OPL-enabled contracts on Sapphire and smart contracts on other chains. This allows dApps to access privacy-preserving capabilities while keeping their main logic on their primary chain.

Oasis Privacy Layer diagram

info

For how to use use signed messages with the GSN to trigger a cross-chain messages, please visit our Gasless Transactions chapter.

Message Bridges

You can integrate message bridges into your dApps using one of these three methods:

  • OPL SDK: A wrapper provided by the Oasis Protocol that simplifies the integration of message bridging with Oasis’s privacy features.
  • Celer Inter-Chain Messaging (IM): A generalized message bridging solution by Celer, which lets you build more complex solutions.
  • Router Protocol CrossTalk: An extensible cross-chain framework that enables seamless state transitions across multiple chains.

Comparison

ProtocolValidator NetworkRelayerFees
OPL SDKSGN (Celer)Executor (self-hosted or hosted service by Celer)SGN Fee: Paid via msg.value
Executor Fee: Charged externally (Free on testnet)
Celer IMSGN (Celer)Executor (self-hosted or hosted service by Celer)SGN Fee: Paid via msg.value
Executor Fee: Charged externally (Free on testnet)
Router ProtocolOrchestrators (Router Chain)Relayer (run by 3rd party)Paid by the approved feepayer on the Routerchain

Examples