Skip to content

Solution Strategy

Goal/Requirement Solution Details
Flexible and modular backend engine to run decentralized applications Event-driven engine on Wasmtime using the WASM Component Model; all host capabilities exposed via WIT Hermes Engine
WASM application packaging HDF5-based application containers with strict directory layout, metadata, and immutability Packaging Requirements
Application integrity and trust COSE signatures over CBOR payloads; certificate store; API version checks Signature Payload
HTTP and browser integration Built-in HTTP gateway serving static assets and routing API requests to modules by endpoint subscriptions and app hostnames HTTP Gateway
P2P distribution and coordination Embedded IPFS/libp2p node for pub/sub, DHT, and content addressing; signature validation on topics/messages IPFS
Efficient WASM execution Pre-linked InstancePre per module; immutable module state across calls via explicit runtime context Hermes Engine — WASM execution
Data access and isolation VFS backed by HDF5 with permissioned directories (srv, usr, tmp, etc.) VFS Permissions
Event routing and concurrency Global MPSC event queue + thread pool with per-target dispatch; explicit app/module targeting Event Model
Catalyst (Athena) MVP flows Topic schema, receipt model, dependency tracking for event processing Catalyst MVP