Oasis Network

The problem

Public blockchains publish everything by default. Financial applications, healthcare data, identity systems — most real-world use cases need selective privacy without giving up the auditability of blockchain settlement. General-purpose L1s force a choice: either put sensitive data on-chain and lose privacy, or keep it off-chain and lose the settlement guarantees. Oasis's confidential compute architecture (built on trusted execution environments) lets applications keep computation private while settling on-chain. But the developer experience for building on that architecture is still new territory.

Key challenges

Confidential compute on blockchain has to reconcile several unfamiliar concepts: TEE attestation, confidential state management, private-then-public settlement flows, and the security model of the TEE hardware itself. Developer surfaces have to make these approachable without hiding the guarantees they're supposed to provide.

What we built

AR Data contributed engineering on the Oasis ecosystem — privacy-preserving application patterns and tooling that let developers build on confidential compute infrastructure. The contributions focused on the developer surface — patterns, examples, and integration paths that make the platform's confidential-compute story usable. Specific work included integration patterns for common use cases (private financial computation, confidential data economy applications) and tooling that lowered the barrier for developers coming from non-confidential-compute backgrounds.

Our approach

1. 1

   Application patterns for common use cases

   Confidential compute is abstract until you see it applied. Building patterns for common use cases (private computation, confidential data marketplaces) makes the platform concrete.

2. 2

   Attestation surfaces developers can approach

   TEE attestation is a specialist concept. Wrapping it in developer-friendly surfaces without hiding the guarantees is real engineering work.

3. 3

   Integration paths for teams from other L1s

   Developer intuitions come from public-chain patterns. Building integration paths that meet those intuitions lowers the switching cost.

4. 4

   Ecosystem-facing engineering over one-off applications

   Contributions that unblock many teams have higher leverage than single applications.

Key architectural decisions

Results

• Privacy-preserving application patterns for common use cases
• Confidential compute tooling accessible to non-specialist developers
• Integration paths from public-chain intuitions to confidential compute
• Ecosystem contributions to the Oasis platform

Impact

Oasis represents the class of blockchain infrastructure where privacy is treated as core, not as an afterthought. The engineering contributions target developer adoption — the layer that decides whether privacy-preserving blockchain becomes real infrastructure or stays a specialist domain.

Tech stack