Rei Researcher

A live, high-stakes test proving Sapphire’s defense-in-depth architecture in the real world

🚀 A Challenge Like No Other: “If You Hack It, You Keep It.”
In the world of Web3, most security programs follow a predictable pattern — report a bug, wait for triage, then maybe earn a reward.

#OasisNetwork decided to do things differently.
They launched a radical, open security challenge that flips the traditional bug bounty model upside down:

1 Bitcoin (wBTC) is locked inside a Sapphire smart contract. Whoever can hack it, keeps it.
No forms to fill out. No approval process. No private disclosures.

Just one rule: you only win if you break the Trusted Execution Environment (TEE) and extract the private key inside.
This is not a simulation or controlled experiment. It’s a live test on Sapphire Mainnet, with real money on the line, running under the same protections used by Oasis’s production network.
The challenge will remain open until December 31, 2025 — giving the global security community a full year to try their luck, test their tools, and push the boundaries of confidential computing.

🧠 Why This Matters: From Words to Proof
TEE-based systems are designed to execute sensitive code and manage private data in isolated hardware environments. They promise confidentiality even when the host system is compromised.

But as recent research has shown, that promise isn’t always unbreakable.
In 2025, two high-profile vulnerabilities — Battering RAM and Wiretap — exposed weaknesses in the deterministic memory encryption of Intel SGX and AMD SEV-SNP.

Those attacks allowed researchers to extract attestation keys and decrypt private data on multiple blockchain networks built around TEEs.
Projects like Phala, Secret, Crust, and IntegriTEE had to deploy emergency patches and temporarily suspend services.

But Oasis remained completely unaffected, thanks to years of proactive engineering and a strong defense-in-depth philosophy.
That’s why Oasis launched this challenge — not to boast, but to demonstrate confidence through evidence.
“We don’t just claim security. We prove it, in public, under real-world conditions.”

🔒 Built for Adversity: Why Sapphire Is Different
Sapphire, the confidential EVM built on Oasis, runs on Intel SGX v1, which uses a different memory encryption model from the affected SGX/SEV-SNP generations.

This makes Sapphire inherently resilient to the deterministic encryption attacks that compromised other networks.
But the real strength lies in Oasis’s layered security architecture — multiple barriers that work together to contain risk even if one layer is compromised.

These include:
On-chain governance and validator staking: Only approved validators with at least 5 million staked $ROSE can operate Sapphire’s key infrastructure.Ephemeral encryption keys that rotate every epoch, preventing any compromise from affecting past transactions.Dynamic CPU blacklisting that can instantly exclude vulnerable hardware from participating in the network.Strict node membership requirements and hardware attestation for all key manager nodes.

This holistic “defense-in-depth” model means that Sapphire isn’t just secure because of the TEE — it’s secure because every layer, from protocol to hardware, reinforces the next.
🧩 Inside the Challenge: The Unbreakable Smart Contract
The challenge centers on a Sapphire smart contract deployed at:

0xc1303edbFf5C7B9d2cb61e00Ff3a8899fAA762B8
Within the enclave, the contract generates a cryptographic keypair using Sapphire’s secure random number generation.

The private key is created and stored entirely within the TEE — it never touches disk or memory outside the enclave.
The public key is used to derive an Ethereum address that holds 1 wrapped Bitcoin (wBTC): 0xCEAf9abFdCabb04410E33B63B942b188B16dd497
From there, the contract functions as a custodial wallet, capable of signing transactions only when the authorized owner initiates a verified withdrawal.
To eliminate common attack vectors, Oasis implemented the following constraints:
No off-chain key generation — everything happens inside the enclave.
Hardcoded withdrawal addresses — even if an attacker compromised the owner’s account, they could only send funds back to Oasis’s multi-sig vault.
SIWE (Sign-In with Ethereum) for identity verification and transaction authorization.

There is no backdoor, no debug function, and no administrative override.
In short:
The only way to move the funds is to extract the private key from inside the TEE — something that would prove a full hardware compromise.
🔧 Real Security, Not a Simulation
Many blockchain security tests are run in isolated conditions, using modified hardware or experimental builds.

The Oasis Security Challenge takes the opposite approach: it operates under exactly the same parameters as the live Sapphire network.
That means all of Sapphire’s standard protections are active:
🔄 Ephemeral key rotation every epoch
🧱 Restricted compute committee membership limited to trusted validators
🔐 Enhanced key manager safeguards
⚙️ Dynamic CPU blacklist enforcement to remove compromised processors
This ensures the test reflects real operational security — not a lab demo or proof-of-concept.
🌍 A Community-Wide Experiment
Since its launch, the challenge has already gained over 250,000 views and drawn attention from Ethereum security researchers, hardware hacking groups, and academic institutions studying confidential computing.
The contract code is fully verified and publicly visible on the Oasis Explorer, ensuring total transparency.
Participants are encouraged to discuss techniques, share insights, and collaborate within the community — especially in the official Oasis Discord.
The message is simple:
“If you think Sapphire’s TEE security can be broken, here’s your chance to prove it.”
And if no one succeeds by the end of 2025, it will be a powerful validation of the robustness of Sapphire’s architecture — real proof that confidential computing can work safely on a global blockchain.
🕒 Challenge Parameters
Duration: Now through December 31, 2025

Reward: 1 wBTC (one full Bitcoin)

Network: Sapphire Mainnet (Oasis Network)
🧭 Beyond the Bounty: A Philosophy of Proactive Security
This experiment reflects a broader truth about Oasis’s design philosophy.

Security isn’t something that happens after a problem — it’s something you design for from the start.
Oasis engineers anticipated hardware-level threats years before they became mainstream.
That foresight led to architectural decisions — like key separation, ephemeral encryption, and governance-enforced trust — that now protect Sapphire users today.
The security challenge embodies this philosophy: open, transparent, and fearless.
Instead of hiding behind marketing claims, Oasis invites the world to test its assumptions.
In an industry built on trust, Oasis proves that trust is earned through verification — not just belief.
🔒 Conclusion: Actions Speak Louder Than Words
The Oasis Security Challenge is more than a bounty — it’s a real-world experiment in trustless security.
It’s an open invitation to every researcher, hacker, and engineer to test the boundaries of TEE-based confidentiality.
If someone manages to steal the Bitcoin, it will mark a significant moment in security research.

If not, it will serve as undeniable proof that Oasis’s defense-in-depth architecture stands strong — even under the harshest scrutiny.
Either way, the blockchain community wins — with clearer insights, stronger technology, and a deeper understanding of what true security looks like.
So the challenge stands:
Can you break Sapphire’s TEE?

If you can, the Bitcoin is yours.

If you can’t, you’ll have witnessed one of the most resilient confidential computing platforms in action.
🧭 Learn more: Sapphire – Confidential EVM by Oasis Network