Verifiable security,
all the way down.
OasisWallet is built around an explicit threat model, layered key custody, TEE attestation and reproducible builds. Every claim on this page is independently verifiable — by you, today.
Six pillars, one assumption: trust nothing by default.
The wallet is hostile to its own environment. The host OS, the network, even the user's own clipboard are treated as adversarial inputs.
Hardware-backed signing
Ledger devices sign every outbound transaction on-device. Private keys never leave the secure element — not even to the wallet process.
Local-first encryption
All sensitive state is sealed with Argon2id-derived keys before touching disk. The OS keychain holds the wrapping key.
Zero telemetry
No analytics, no crash reporting, no remote logging. OasisWallet talks to the nodes you authorise and nothing else.
Run your own node
Bring your own Oasis Core and ParaTime RPC endpoints. No hosted indexer dependency, no shared infra.
Reproducible builds
Every release is bit-for-bit reproducible from public source. The binary you run matches the audited tree.
Defense in depth
Per-transaction simulation, blind-signing guards, EIP-712 typed approvals and anomaly review on every signature.
What we defend against — explicitly.
A wallet's threat model should be written down. Here is ours, in full, with the corresponding mitigation for each surface.
| Surface | Attack vector | Mitigation | Status |
|---|---|---|---|
Host malware | Process injection or memory scraping of the wallet runtime | Hardware signing — secrets never exist as plaintext outside the secure element | mitigated |
Supply chain | Compromised dependency pushes a malicious release | Reproducible builds + 3-of-5 maintainer signature threshold for tagged releases | mitigated |
Phishing UI | Fake popup tricks user into approving a hostile transaction | Native desktop window (unspoofable from a webpage) + on-device Ledger confirmation | mitigated |
RPC tampering | Malicious RPC returns forged balances or simulation results | Cross-source verification across user-configured endpoints + deterministic tx hashing | mitigated |
Clipboard hijack | Address overwritten between copy and paste | Address book whitelisting, checksum re-display, last-mile confirmation on Ledger | mitigated |
ROFL agent drift | Off-chain agent code drifts from attested manifest | TEE attestation pinned per session — wallet refuses unattested workloads | monitored |
Quantum (long-term) | Future cryptographic break of secp256k1 / Ed25519 | Tracked in roadmap — PQ-signature migration aligned with Oasis Core releases | monitored |
Five tiers. Each one assumes the one above failed.
Secrets descend through five sealed boundaries before reaching disk. A compromise at one tier never grants access to the tier above it.
- No code path can read raw private keys
- Wrapping keys rotate per session
- Biometric unlock is required to derive the session key
- Forensic-grade memory zeroisation on lock
Cryptographic proof, not vendor promises.
Every ROFL agent the wallet talks to must produce a fresh remote-attestation quote. The wallet validates the TEE measurement against the signed manifest before a single byte of agent payload is trusted.
{
"tee_type": "Intel-TDX",
"mr_enclave": "0x9f4c2a01…1b6d5",
"nonce": "0x71ad…03e",
"quote_status": "OK",
"signed_by": "Oasis Attestation Service v2",
"valid_until": "2026-05-13T08:00:00Z"
}Four firms. Full reports. No redactions.
Every audit is published in full alongside the resolved-finding ledger and reproducible commit hash.
Halborn Security
Core wallet + Sapphire signer
Trail of Bits
Ledger integration layer
Least Authority
ROFL attestation pipeline
Zellic
Cipher / WASM signing path
Verify the binary you're running.
Clone the source at the release tag, run make verify, and confirm the SHA-256 matches the artifact you downloaded. If it doesn't, do not run it.
- Bit-for-bit reproducible across macOS, Windows, Linux
- 3-of-5 maintainer signature threshold on every tag
- Public release manifest, signed with the Oasis PGP key
- Independent rebuild attestations from the Oasis Foundation
$ git checkout v3.2.0 $ make verify ==> reproducing build (this takes ~6 min) ==> hashing artifact SHA-256 9f4c2a01e6b3d8c5fa1e0d92b7c4a386de1c0bf21a47e9d2b80c93a4f7e1b6d5 ==> comparing to published manifest ✓ match — release.manifest signed by 3 of 5 maintainers ✓ binary safe to install
Find something. Get paid.
We run a continuous bounty programme with HackenProof. Critical findings are paid within 14 days of triage. Coordinated disclosure required.
Remote key extraction, signature forgery, supply-chain RCE
Privilege escalation, persistent UI spoof, attestation bypass
Information disclosure, transaction manipulation primitives
Hardening issues, deviations from threat model
Built to be inspected.
Read the source, rebuild the binary, verify the attestation. Then take custody.