Runtime Roadmap
Current Implementation Status
Version: RC4 / 0.19.0-rc4 (March 2026)
This is a pre-release. The runtime is under active development and not suitable for production workloads.
Verified and Working
- Fresh install to working chat via
curl | bashon x86_64 and Jetson (aarch64) - 3-mode chat: native, WASM, and microVM capsules running on one runtime
- Cross-network P2P: seed server to Jetson via DHT (Iroh/QUIC), no manual tickets
- Rootless microVM: runs without sudo on Jetson and WSL
- Data capsules: signed content + viewer (markdown viewer, GBA emulator)
- AI provider: LLM routing via
elastos://ai/ - Content sharing:
elastos sharebundles files, publishes to IPFS, produces browser link - Signed releases: Ed25519 publish/install/update pipeline on both platforms (x86_64 and aarch64)
Verified Platforms
| Platform | Architecture | Status |
|---|---|---|
| Linux | x86_64 | Full runtime baseline |
| Linux (Jetson) | aarch64 | Full runtime baseline |
| WSL | x86_64 | Verified |
| macOS | x86_64 / arm64 | Developer workstation only (KVM unavailable) |
Convergence Timeline
The runtime converges with PC2 in phases:
| Phase | Timeline | What Happens |
|---|---|---|
| v1.2-1.5 | Now | Ship PC2 + dDRM + dApp Store (no Runtime needed) |
| v1.5 | 3-6 months | Modularize PC2 into capsule-shaped interfaces |
| v1.6 | 6 months | Signed capsule format (bridge to Runtime) |
| v2.0 | 6-12 months | Runtime hosts PC2 as Shell capsule -- same UX, new security model |
At v2.0, the current Puter desktop becomes the shell capsule, dDRM becomes a provider capsule, and dApps become sandboxed app capsules. The user experience stays the same; the security model changes underneath.
What's Next
The following capabilities are planned but not yet available:
Blockchain Integration
- ACCESS_TOKEN to capability token bridge: on-chain access tokens will map to runtime capability tokens
- DID sidechain bridge: the runtime's local
did:keyidentity will bridge to on-chaindid:elastosDID - Payment-aware flows: on-chain purchase triggers capsule access
Platform Expansion
- macOS support: KVM is unavailable on macOS, so a WASM-only mode is needed for full runtime support
- Source publication: cleanup and audit before open-source release
Shell Evolution
The shell capsule -- currently an auto-grant loop -- will evolve through three stages:
- Current: 50ms loop that auto-grants everything
- Bridge: Shows permission prompts ("Media Player wants to decrypt video.mp4. Allow?")
- Future: AI agent shell that makes intelligent, conversational permission decisions
A Note on Stability
This is a pre-release. If you build against the current APIs, expect breaking changes. The architecture and capability model are the stable commitments; the specific commands, paths, and contract interfaces are subject to change as the runtime matures.