Pinned
Oasis ๐น
9,303 posts
Oasis ๐น
@OasisProtocol
Privacy you can verify. For any chain, any application, any builder.
Joined July 2019
1/ "Verifiable" is going to be the most overused word in crypto for the next twelve months. As the cycle turns from "trust the team" to "trust the code," every protocol is going to claim verifiability. Most claims will be wrong. The actual standard is high.
2/ Real verifiability has three properties: the code is public, the build is reproducible, the runtime is attested. Most projects ship one. A few ship two. The ones shipping all three are the only ones where "you can verify" is literally true. Anything else is asking you to trust3/ This is the bar Sapphire and ROFL were built for. Confidential compute with open source code, reproducible builds, and remote attestation isn't just a privacy story. It's the only stack where the chain of verifiability closes. The next twelve months are about which teams meet- Do you know whoโs going to stand on the podium? ๐ดโโ๏ธ If you're already calling the winners in your group chats, itโs time to make it official. Welcome to the Oasis ร Slovenia Cycling Challenge! Drop your predictions for the biggest races of the season - from the brutal climbs of
- Starting today, mGLOBAL is available on the Aave Horizon RWA Market. As the worldโs largest DeFi lending protocol with over $24 billion in net deposits, @aave enables investors to use mGLOBAL, an institutional asset-backed strategy by @FasanaraCapital , as collateral to borrow
00:00 - 1/ @robinmarketsxyz just moved their TWAP oracle inside an Oasis ROFL TEE. The yield-distribution math that allocates returns to YES and NO holders on Polymarket positions is now hardware-attested. Open source code, reproducible build, attested runtime. The full chain.
2/ Why the move matters: the oracle had been running on a normal server. The code was open source. That's not the same as verifiable. A binary on a server can drift from the repo, get tampered with, or be compromised at the operator level. Open source proves you can read the3/ Inside the TEE, the signing key never leaves the enclave. Attestation proves the exact code at github.com/robin-markets/โฆ is the binary doing the work. EIP-712 signatures, hardware-isolated, censorship-resistant. Yield distribution that's transparent, open-source, and now - 1/ Decoded: What open source actually proves. Open source code is treated as the gold standard for trust in crypto. If the code is public, the protocol is trustworthy. But that's a much weaker guarantee than people assume. Here's what open source alone really proves: you can
2/ The gap is what's running. Most "open source" software is built and deployed by an operator running a binary on a server. You can read the source. You can't verify the binary running matches it. The code that does the work is one trust assumption beyond the code that's public.3/ Verifiable builds close half the gap: deterministic build, published hash, anyone can rebuild and check. Attestation closes the other half: a TEE signs a proof of which binary is loaded. Open source + verifiable build + remote attestation = the only stack where "the code you - This week: a Decoded on what open source actually proves, @robinmarketsxyz shipping their TWAP oracle inside a TEE on ROFL, a Thursday read on what "verifiable" really means, and the Challenge Hub keeps rolling.
- You can read open source code. You can't verify the binary running it is the same code. That gap is where most of the remaining trust assumptions in DeFi live. The teams closing it are the ones to watch this cycle.
GIF - Sunday on Oasis. Privacy infrastructure compounds across cycles. The work doesn't notice what week it is.
- Heartbroken to see @urskazigart down at the Tour de Suisse Women. Fractured jaw, no other injuries. The fall is never the story. The way back up always is. Get well soon, Urลกka. ๐ธ๐ฎ
- Open source. Reproducible. Attested. The three properties production DeFi has been pretending it had. @robinmarketsxyz actually shipped all three. The bar for trustworthy oracles is now a working example, not a claim.1/ How does Robin Markets ensure fair yield distribution across stakers? We built our own TWAP Oracle and we just made it significantly more robust by running it in an Oasis ROFL TEE. Here's why this matters ๐
- Half the code you wrote this week will get rewritten. The other half is just waiting for someone to notice. Outside.
GIF - 1/ Every financial system has a finite number of trust assumptions. A traditional bank: hundreds. A custodial exchange: dozens. A self-custody DeFi protocol: between five and twenty, depending on how you count oracles, multisigs, and operators. The unit isn't binary. It's a
2/ The work of the next cycle of DeFi is counting and removing. Every operator that can be replaced by attestable code is one assumption gone. Every oracle that can be moved into a TEE is one more. Every smart contract that can be made fully autonomous reduces the count further.3/ This is the thesis behind ROFL. Confidential offchain compute with attestation, replacing the "trust the AWS instance" assumption with a "verify the enclave" property. Every product that puts a component onchain via ROFL counts as one fewer black box in the industry. That's
