Sovereign computing infrastructure spanning operating systems, identity, and autonomous agents. **Esver OS · Visage · Mr Haven**
Joined December 2025
- Tweets1.3K
- Following90
- Followers64
- Likes274
For DeFi auditors:
the source is now public.
SECURITY.md defines the disclosure workflow.
For protocol builders:
MIT-licensed interfaces and libraries are designed for composability and vendor-friendly integration.
For the Base ecosystem:
this is what production-grade digital-asset protection infrastructure looks like.
@base @CoinbaseDev @baselatam
System architecture:
• Per-user vaults deployed as EIP-1167 minimal-proxy clones
• Shared yield routing through Aave V3
• User-defined distribution plans
• Scheduled and inactivity-triggered execution flows
• Beneficiaries specified by wallet or email via hash-locked escrow
852+ tests passing.
Vendored dependencies are pinned to deploy-time trees to support deterministic recompilation and bytecode reproducibility.
Dual-licensed:
AGPL-3.0 + MIT.
• AGPL for the protocol implementation
• MIT for interfaces, libraries, and integration tooling
A licensing structure influenced by projects like Uniswap Labs and Warp:
protect the protocol core, keep the integration surface open.
This is now the Sovren standard.
github.com/sovren-software/m…
The complete V1.0.2 contract source, exactly as deployed on @base.
Live since December 2025:
mrhaven.io
These contracts are currently securing real user vaults.
Verified on Basescan.
Reproducible from the v1.0.2 release tag.
Bytecode parity is the proof.
Sovren Software now maintains two flagship public OSS repositories.
Visage
Linux face authentication through PAM.
Rust. v0.3.0.
Mr Haven V1
Programmable time vault infrastructure on Base.
Solidity. v1.0.2.
Different domains.
Same engineering discipline.
Voice surface: @openhome | Action surface: Esver OS
Both local. Reliable computer-use agents need substrate and executable skills, not bigger models.
$0 marginal model cost. Deterministic workflows. Private context that never leaves the machine.
Design-partner conversations open.
Voice request to an @openhome speaker. A local AI books a real Delta flight end to end on a fresh Minisforum X1 iGPU. No human clicks. No cloud agent. 73 seconds. The video is the demo.
Numbers below. 🧵
Our founder on the benchmark that defined our wedge:
Repeated company workflows compiled into local executable skills; verifiable, auditable, customer-owned execution.
Reliable agents need more than bigger models. They need substrate.
The question is not whether you need privacy. The question is whether the systems you use structurally guarantee it or merely promise it.
Accountability is an infrastructure problem, not a policy problem. You cannot audit what you cannot trace. You cannot trace what does not produce receipts. Receipts are architectural, not optional.
The question is not whether AI agents will manage money. The question is who holds the keys. We built infrastructure where the answer is always: the owner.
An AI agent without a persistent identity is a stranger every session. Identity is not authentication. Identity is continuity.
Agents are actors, not tools. Actors need identity that persists. Authority that has bounds. Accountability that is permanent.
This is not a feature request. It is an infrastructure problem.
Sovereignty is not a product feature. It is an architectural commitment made before the first line of code. Every component we build assumes the network is hostile and the user owns their data.