Over the past four weeks, Elastos progressed across PC2, Runtime, Carrier, and the blockchain layer.
Runtime v0.4.0 and Elastos Node for Ubuntu v1.1 were released earlier in the period. The work that followed built on both releases: dDRM moved further into the Runtime capability model, the Runtime marketplace gained buy and trade flows against live Base contracts, and public RPC infrastructure moved to an Elastos-run stack across two regions.
Across the same period, a standalone protected-content reader shipped as a family of 11 npm packages. Elastos Node Manager entered PC2 as an installable service-type app. The Elastos Node Monitor relaunched with Telegram alerts. The Elastos website completed its rebuild. Essentials returned to the Elastos GitHub with Base-chain support. A coordinated security pass landed fixes across four repositories. Hyper, the post-quantum messaging app previously called Hey, completed an independent multi-round audit.
Runtime: v0.4.0 becomes the base for the next stage
Runtime v0.4.0 introduced the Library, Marketplace, Archive, Spaces, Trash, WebSpaces, and first-party capsule packaging. The release gave Runtime a provider-backed object model, where the desktop and the system underneath work with the same files, shared objects, and permissions.
The work after v0.4.0 focused on extending that base.
dDRM is moving from PC2 into Runtime’s capability model. The protected-content engine is being rebuilt in Rust and Runtime in stages, starting with 2-of-2 XOR splitting, then Shamir 2-of-3 over GF(256), followed by a reconfigurable threshold quorum, verifiable distributed key generation, and post-quantum threshold attestation using ML-DSA-65.
When a quorum approves a content-key release, it creates QuorumReleaseProofV1. This proof can be checked offline and carried independently of the system that produced it.
A pre-audit pass later resolved seven of eight dDRM findings. The work includes single-copy CENC decryption with byte-identical output checks, strict limits on untrusted box counts, a single-use grant refresh during quorum retries, per-capsule WASM memory budgets, and a way for operators to stop runaway capsules.
Runtime also reached the same core feature set on Mac and Linux. Both now run the same Home, the same first-party apps, shared Documents as Runtime objects, and two-way Carrier Chat.
A new Capsule Inspector inside Home shows which capability tokens each running capsule holds. The Browser VM now acts as the boundary between web content and the rest of the system. A Jetson Browser VM can browse ela.city end to end on-device, while the Mac Browser VM passed its acceptance audit and signed-app proof.
The Runtime marketplace arrived later in the period. A new branch went from empty to a working buy and trade backend in three days, using live contracts on Base.
The flow includes buy authority, trade authority, a KID-to-tokenId resolver, the routes behind market, vault, and acquire, and an Acquire action that pins a purchased encrypted asset into Library. The current end-to-end path is around 72% complete.
Minting remains in Studio. Playback remains in the Runtime viewer.
PC2: Node Manager and more
PC2 remained on v1.3.0 during the period and continued to act as the reference point for Runtime convergence work.
The main addition was Elastos Node Manager entering the PC2 integration tree as the first installable service-type app.
This app type runs as a long-lived service rather than a one-time launcher. It includes Ed25519 verification during installation, device checks through platform requirements, and packaging for amd64, arm64, and macOS from one packager path.
The production registry entry is staged but not yet live.
For Council and BPoS operators using the lower-level node runner, v1.1 provided the safety base for follow-up work. It binds EVM RPC and WebSocket services to loopback by default, removes the unauthenticated unlock flag from mining chains, and adds firewall and hardening tools. Existing nodes can adopt it without restarting the live signing node.
The native media player released versions 0.12.6 and 0.12.7 during the period, bringing client-side decryption in line with the new quorum custody work on the server.
The marketplace web app moved from version 4.3.0 to 4.4.0. The update adds the 2026 brand identity, removes the legacy XMTP messaging stack, moves the wallet-mode switcher into Explore, and includes security work around response headers, session handling, telemetry, and service-worker caching.
Carrier: cross-platform Chat, Remote Exit on Mac, and Hyper
Carrier added visible cross-platform work during the period.
Runtime now carries two-way Chat between Mac and Linux on its main line, with the same Home, identity, and room state on both platforms.
The Mac Browser VM also gained a Remote Carrier Exit with route tickets, principal-scoped streams, and route-bound cleanup records.
Hyper, the post-quantum messaging app previously known as Hey, runs on Carrier.
Encrypted audio and video calls now use ML-KEM-768 with X25519 and ChaCha20. Users can verify each other through an out-of-band safety-number check. Nearby Mesh provides offline peer discovery without an active network connection.
An independent multi-round adversarial audit found and fixed a group-media fail-open. Previously, one member claiming not to support media could push an entire room toward plaintext. The fix keeps media encrypted and removes that member from the media mesh instead.
A live network-exposure check confirmed that Hyper has no internet-facing server. The only listener on the host is loopback.
Blockchain: public RPC moves in-house, protocol v0.9.2, and Term 7
The blockchain layer moved on several fronts.
Public RPC has been a recurring issue for Elastos users and dApps over the years, especially when endpoints were slow, unreliable, or unable to return older blockchain data.
The new stack replaces the previous managed setup with Elastos-run infrastructure across two regions. It is a drop-in, byte-compatible replacement for api.elastos.io, and it now serves all production traffic.
Wallets and dApps did not need any changes.
Two active-active bare-metal servers, sit behind Cloudflare. Cached reads return in about one millisecond. Cold reads return around 1.5 to 1.8 times faster than the older endpoints.
The stack holds a full archive of more than 10 million blocks, so historical reads that previously failed can now resolve. Managed-cloud cost is now zero.
The on-chain DRM protocol released v0.9.2. It rejects the native sentinel in createOffer and buyAccess, fixes an unbuyable-channel issue caused by channels with no royalty holders, and moves MultiChannel child wrapping until after creation.
The key-transfer service now uses HPKE-sealed content-key transfer under RFC 9180. The transfer route checks live on-chain access before allowing a key transfer.
On the governance side, Term 7 Council election concluded. The mainchain explorer received a fix for its claim-window state. ECO was removed from Elastos Node, and the chain is now terminated. The Council node setup guide was rewritten and published on docs.elastos.net.
A dDRM reader for protected non-media content
A standalone reader for protected non-media content was built from scratch and released as a family of 11 dDRM reader npm packages.
The model is direct. The backend decrypts the content. The frontend renders a typed render layer. Plaintext does not leave the backend.
PDF content renders through pdf.js with scripting disabled. EPUB content renders in a no-scripts iframe with content security policy enabled. It includes a table of contents, font-size controls, themes, and chapter progress.
Support for images, 3D content, fonts, archives, and comics followed.
The reader started at version 0.0.1 on May 31 and reached the 0.2.0 package family on June 4. Later point releases through 0.2.4 added 24-hour wallet-delegation persistence.
The Elacity platform then connected the reader to its protected-content path and tightened secure-view session behavior underneath.
Website rebuild, Essentials return, and monitor relaunch
The Elastos website was rebuilt from the ground up around six core routes: the homepage, Elastos, ELA, About, Build, and supporting pages.
The previous five-dropdown navigation was replaced with a flat five-link navigation. The ELA page became the canonical token page, with Bitcoin merge-mining security and hashrate at the centre of the story.
The new hero reads: “The internet you own.” Twenty-one redirects keep older links working. The rebuilt site is approaching launch.
The Essentials super-wallet codebase was moved back to the Elastos GitHub. Base-chain support was added, with testing to follow.
The Elastos Node Monitor was rebuilt and relaunched at monitor.elastos.io.
It shows live BPoS validator status, Council node health across the main chain, arbiter, sidechains, and oracles, plus a status panel for current problems.
A Telegram alert bot now sends node owners a direct message when their node goes offline and another when it recovers.
ElacityLabs.com also added a Fourthwall merchandise store, an on-site map of the Elastos node fleet, a Resend newsletter, a Notion-to-blog relay, and social publishing through Postiz.
The Elastos DAO Play Store account suspension has been escalated to Google Support, requesting its immediate reinstatement.
Platform-wide security sweep
A coordinated security pass landed fixes across four repositories.
The marketplace frontend fixed CSV-export injection, a service-worker race in the in-app browser, an EIP-1193 cache invalidation issue, and an undercount in market statistics.
The transcode service restricted its Bento4 execute endpoint to the intended binary directory and removed an unauthenticated code-execution surface.
The on-chain DRM and key-transfer changes are part of the same security work.
What comes next
- The final dDRM audit finding is scheduled for the next cycle. Once it is complete, the team can hand the work to an external auditor.
- The Runtime marketplace still needs its first live Base purchase through a real wallet to complete the integration test.
- Elastos Node Manager needs more time on the integration branch before its production registry entry goes live.
- macOS notarisation for the ElastOS Launcher is complete. The coordinated PC2 node release and Launcher publish are next.
- The rebuilt Elastos website is expected to go live in the same release window.
- Elastos main chain testnet getting back.
- Essentials overhaul.
