Sapphire is the first and only confidential EVM that empowers Web3 with Smart Privacy — privacy that evolves with developers, users, and brands. Developers can build EVM-based on-chain dApps with smart contracts that are 100% confidential, 100% public, or anywhere in between.
Building on Oasis positions any dApp to achieve the most important features and use cases for every Web3 audience.
Get ready to experience the fast and frictionless development experience of building on Sapphire.
Explore the public Github repository and start adding it to your projects.
When a dApp uses the Sapphire provider wrapper all transactions are end-to-end encrypted between the browser and the smart contract without any additional changes. However, signing encrypted transactions will look slightly different than normal in MetaMask due to EIP-712.
When the EVM is run inside a Trusted Execution Environment (TEE) - in the case of Oasis Sapphire this is Intel SGX hardware isolation - the node operators cannot see transaction inputs, return values or smart contract state because all memory used by the enclave is encrypted. The EVM runs at nearly full speed in comparison to other privacy solutions such as ZK or FHE which are very computationally expensive.
The Sapphire ParaTime uses the Oasis Layer-1 BFT Proof-of-Stake consensus system, see the WhitePaper.
Yes, most applications can be ported over with no changes if they use Truffle or Hardhat. To take advantage of the full potential of confidential contracts dApps will need some minor changes.
Yes, dApps will remain compatible with MetaMask and other window.ethereum providers with or without the Sapphire encryption wrapper.
While OPL provides a bridge to many EVM chains via Celer IM, contracts on Sapphire can generate Ethereum and Bitcoin compatible keypairs, allowing them to conditionally sign their own transactions.
Yes, with support for EcDSA, EdDSA and confidential storage you can implement authentication using strong credentials present on every modern mobile device and browser.
Developing dApps for Oasis Sapphire has full support the two most popular smart contract development frameworks. Truffle works out of the box using the Sapphire wrapper.
For Hardhat there is an extra plugin you can use, just add this to the beginning of your hardhat.config.ts file:
import '@oasisprotocol/sapphire-hardhat';
Oasis Privacy Layer (OPL) is a message passing bridge and suite of utilities that enables you to easily access the confidentiality and encryption features of Sapphire from many other EVM compatible chains without your dApp users worrying about how to pay gas.
.svg)
