Skip to content

ElastOS Runtime v0.3.0

Choose a tag to compare

@andersalm andersalm released this 27 May 23:08
· 3378 commits to main since this release

Added

  • Added Browser as a first-class ElastOS app, routed through Runtime Browser, Net, Exit, Browser Engine, Wallet, and Inbox provider contracts instead of raw host browser authority.
  • Added the Wallet app as the main blockchain authority surface with built-in managed accounts, receive/send flows, account recovery, transaction activity, MetaMask connector support, UniSat/Bitcoin groundwork, and Wallet-owned approval methods.
  • Added passkey-first Home authentication with principal-scoped user roots, admin/guest policy, account recovery/reassignment, full Recovery Kit export/import, and protected root metadata.
  • Added Inbox-backed wallet approval flows so browser and capsule-originated signing and transaction requests are reviewed through Runtime-owned approval paths.
  • Added typed Chain Provider support for proof, transaction prepare, broadcast, sync health, and node lifecycle operations without exposing raw chain RPC to apps.
  • Added Availability, Rights, Key, DRM, and Decrypt provider contracts as the protected-content and dDRM foundation, including sealed-object direction and PQ-hybrid algorithm metadata.
  • Added Net and Exit provider foundations for Browser networking policy, exit routing, and fail-closed external network access.
  • Added PC2 convergence documentation covering wallet bridge, IPFS/content availability, dDRM, provider mappings, and SmartWeb alignment.

Changed

  • Reframed Home, System, Inbox, Wallet, Browser, and Chat Room as first-party capsules operating behind Runtime authority boundaries.
  • Split large gateway surfaces into focused gateway modules for Home/System, Wallet, Browser, Inbox, Room, Site, provider proxy, models, and tests.
  • Moved wallet, chain, browser, pricing, content, and protected-content operations toward typed provider calls and elastos:// contracts instead of app-visible raw APIs.
  • Updated System to focus on runtime/account policy and Webspace/provider visibility while Wallet owns wallet accounts, methods, requests, and transaction flows.
  • Reworked Home realtime behavior toward scoped Runtime events and reduced fixed-interval polling that slowed the desktop when multiple apps were open.
  • Updated README, ROADMAP, TASKS, architecture docs, glossary, provider docs, changelog, and state docs to reflect the 0.3 Runtime model.
  • Expanded release verification with Home entropy, Browser entropy, WCI alignment, auth/wallet focus smoke, wallet product safety smoke, browser/provider smoke, and protected-content smoke checks.

Fixed

  • Fixed passkey and Recovery Kit flows so protected roots and built-in Wallet keys can be recovered under a new passkey when appropriate, while external wallet private keys remain outside ElastOS custody.
  • Fixed guest/admin policy issues, including scoped account roots, safer passkey management, and clearer promotion/demotion behavior.
  • Fixed wallet account creation, recovery import/export, built-in send signing, transaction activity, default wallet selection, and browser wallet defaults.
  • Fixed browser wallet compatibility paths for external sites by routing account discovery, chain reads, signing, and transaction approvals through Runtime Wallet/Inbox/Chain providers.
  • Fixed Browser session handling to support scoped page/session state, independent page capacity accounting, runtime-scoped input/WebRTC signaling, and fail-closed engine/exit behavior.
  • Fixed unsafe or stale authority patterns: hidden request fields are rejected, raw runtime control APIs are blocked, raw RPC/private-key exposure is avoided, and WalletConnect stays hidden/fail-closed until pinned operator configuration exists.
  • Fixed CI clippy warnings in Home realtime tests after the 0.3 merge.

Notes

  • v0.3.0 is the first integrated SmartWeb runtime release: passkey Home, built-in Wallet, Browser, Inbox approvals, typed providers, Carrier-shaped capability boundaries, and protected-content foundations are now part of one coherent runtime direction.
  • Browser is now a real first-party app and provider-mediated browsing path, but the product browser engine strategy remains an active area. Hosted Browser/Selkies is accepted as the current proof path, not the final browser architecture.
  • CI is green on the release commit 8acb72d.