ElastOS Weekly Shipping Report — Week of May 29 – June 4, 2026 #22
SashaMIT
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Elacity Labs — Weekly Team Update for the World Computer Initiative (WCI)
May 29 – June 4, 2026
The week node operators got a safer toolkit, the dDRM reader was born, and the public surfaces were rebuilt. Last week's report (#20) closed PC2 v1.3.0 and Runtime v0.3.0 — both held at those tags this week to absorb cleanly — so the team's energy spread across four fronts that all advance the WCI mandate: Elastos node operations (council/BPoS infrastructure work, a rewritten supernode guide, an ECO-sidechain removal, a node.sh Arbiter fix, and a rebuilt Elastos Node Monitor at monitor.elastos.io with a Telegram alert bot); a brand-new standalone protected-content reader (
ddrm-reader) that went from inception to a published family of 11@elacity-jsnpm packages rendering PDF, EPUB, image, 3D, font, archive and comic content client-side; the Runtime Library/Explorer brought onto ElastOS-native rails (the groundwork that lands as v0.4.0 next week); and a full Elastos website rebuild (26 commits) onto an honesty-first six-route IA. Essentials also returned to the Elastos GitHub with Base-chain support underway. By core-commit volume the two flagship cores are quiet by design; by breadth this is one of the busiest weeks of the quarter.This report is the first of a three-part catch-up batch (#22–#24) covering May 29 → June 19, restoring an interrupted cadence.
Table of Contents
1. The Big Picture — Cores Steady, Everything Around Them Moving
After two release weeks, the flagship cores were deliberately frozen — PC2 at v1.3.0 (now the conformance oracle for runtime convergence) and Runtime at v0.3.0/v0.3.1 — and the team fanned out across the rest of the WCI surface. Two strategic threads dominate. First, protected-content reading became a product: the new
ddrm-readerrepo shipped a full standalone reader (backend + frontend + decoders) for non-media dDRM assets, published as eleven@elacity-jsnpm packages, while the Elacity platform integrated it and hardened its secure-view sessions. Second, node-operator safety and observability advanced sharply: council/BPoS infrastructure was cleaned up, a bulletproof supernode setup guide was published, and the Elastos Node Monitor was rebuilt with public real-time status and a Telegram alert bot. Underneath, the Runtime Library/Explorer was re-implemented on ElastOS authority rails (the v0.4.0 groundwork), the Elastos website was rebuilt for honesty and clarity, and Essentials returned to GitHub with Base support underway.2. ddrm-reader — A New Standalone Protected-Content Reader (11 npm packages)
The biggest single body of new work this week was the inception and first releases of
ddrm-reader(private repo, ~33 in-window commits, Irzhy Ranaivoarivony) — a standalone reader for non-media dDRM-encrypted assets where the server decrypts and the client renders a decoded render-IR, so plaintext never leaves the backend. It went from empty to a published package family in days:decoder-documentthat decodes PDF/EPUB to a typedDocFilerender-IR with magic-byte format detection (f72152e,ad8f0d2,76ad374); a PdfViewer rendering via pdf.js with the canvas + text layer and scripting off (87a670f, fits to container width via ResizeObserver478484a); an EpubViewer rendering via epub.js inside a no-scripts iframe + CSP (a5716a0), with EPUB reader options — TOC sidebar, font size, themes, chapter/progress, collapsible nested TOC (5e81361,3ff5bf4).31932ef), font + archive renderers and code/CSV text routing (9311c01), content detection with magic-byte checks for image and mesh formats (4b5f88e), and aspect-correct 3D camera framing (6f136b9).data:/blob:only and disposes textures (57b5159), with viewer/security hardening woven through (31932ef).4dee68a), GitHub Actions for tests and npm/Docker publishing (aad1f30), per-package READMEs (5ad86bb), and a CI fixture (d6a12ca); CI later built for linux/arm64 + amd64 and aligned the backend image publish with lit-keystore (db40cf2,0102827).@elacity-js/ddrm-reader-*0.0.1 packages were tagged May 31 (backend,ui,ir-schema, and thedecoder-text/mesh/kit/image/font/document/comic/archiveset;acabb94), followed by the 0.2.0 family on Jun 4 (460f39a, "completed implementation + CI/CD") and backend point releases v0.2.1–v0.2.4.This is a genuinely new product surface: a portable, security-first reader that any Elacity property (or third party) can pull from npm.
3. Elacity Platform dDRM — Reader Scaffolding + Session Hardening (ELACITY-2233 / 2224)
In parallel, the Elacity platform side wired the reader in and hardened sessions (reported under ELACITY-2233 / ELACITY-2224):
ddrm-readerto mirror pc2.net's behaviour and implementation (ddrm-decryptin the backend, a frontend-based reader), with support for all content types via the new npm module group, passthrough based on pc2.net support, and a stabilised backend.req_stale_or_future, limiting testing; tracked for resolution.4. Runtime — Library/Explorer onto ElastOS-Native Rails (v0.4.0 groundwork)
This week's Runtime work (reported in the weekly Runtime update) moved the PC2 file-manager concept onto ElastOS Runtime rails — the groundwork that tags as v0.4.0 next week (see #22). The intent is explicit: not a PC2 transplant, but PC2-familiar Explorer UX under ElastOS authority boundaries.
Elacity/pc2.netmainata0a910…— key files inspected includedUIItem.js,UIDesktop.js,open_item.js,refresh_item_container.js, and the PC2 filesystem/file APIs./nullfallbacks, signed-file-URL shortcuts, global socket/session assumptions, or direct filesystem/IPFS GUI access. Library is an app capsule that owns UI only; Runtime injects the signed principal; mutable files/folders/Desktop/Documents/Trash are mediated bylibrary-provider; published content goes throughcontent-provider; Kubo/IPFS stays behind the provider layer.5. Elastos Node Operations — Council / BPoS Infrastructure
A substantial body of council/BPoS infrastructure work landed against the WCI mandate (proposal HeyPuter#212), much of it in the
elastos/Elastos.Noderepo:docs.elastos.net/blockchain/governance-elections/setup-council-node.Elastos.Node(commit2b5e89d3), tested on live and test nodes with all checks passing.node.shwhere a PGP 5-second sidechain dependency prevented the Arbiter service from initialising on new servers (commitd09830e0).6. Elastos Node Monitor — Real-Time Validator & Council Health (monitor.elastos.io)
The Elastos Node Monitor was rebuilt and relaunched at monitor.elastos.io (Jun 4):
7. Essentials — Codebase Repatriated + Base-Chain Support
The Essentials super-wallet workstream resumed: the latest codebase was brought back to the Elastos GitHub safely, Base-chain support was added (testing to follow), and the team helped two council members set up their nodes — directly supporting the operator base the node tooling above serves.
8. Elastos Website — Full Ground-Up Rebuild + Honesty Sweep
The Elastos marketing site was rebuilt on
website-rebuild-2026(26 commits, Jun 3–4, SashaMIT) using a disciplined PBI structure:99aa0751), stood up four survivor route shells/elastos/ela/about/build(3c448fab), and replaced the five-dropdown nav with a flat five-link nav (f79df841); page wrappers converted to lazy + Suspense (fc974955)./elastosas the product page (98cd2309),/elaas the canonical token page with Bitcoin-merged-mining security, hashrate visualisation, exchange grid and supply (95fce61f,ed155134),/aboutas the consolidated story page (13d05a7d), and the Whitepaper folded into/build(ebe1eb3d); 21 redirects + a six-route footer (a911433b).096d572f), sub-brand sprawl + dead imports cut (85265f3d), ScalingSection realigned (34275f70), CTA copy aligned (039a9d81), stats culled 8 → 4 with a BTC-security reframe (0457154a,64b1762c), logo carousel trimmed and renamed "Where to buy ELA" (5a8b6be9); a polish pass cut founders, rewrote the trust block, expanded DAO messaging and added a hero product showcase (bb39862a).a08a6cfa), removed "most secure"/"Bitcoin-Grade" parity claims (136b0d71,54130e8d), removed Marshall Islands DAO plumbing from outward copy (f51a82e1), fixed canonical/OG URLs (b6f9a9b5), and ran a "SmartWeb"/buzzword sweep with aHeroSectiondelete (db893db0).The rebuilt site is staged and not yet live — queued for a coordinated go-live.
9. Elacity Web App — Non-Media Reader + Cinema Re-Route
elacity-webopened its 2026 content work (Jun 4, Irzhy): introduced the non-media content reader (7905e3b7) tied to the newddrm-readerpackages, and re-routed/cinema/**to/**with breadcrumb/route consistency and a cleanup pass (6dcbd4e1,02f2893c,f1d0c763,38482d04). This is the first slice offeature/brand-identity-2026, which accelerates in #22–#23.10. Runtime — Mac VZ Integration Review + v0.3.2 Reframe
The Runtime held v0.3.0/v0.3.1. Its only in-window commits were a documentation pass on
sash/local-test-v030(021f620,ec5d731) recording the Mac-VZ integration-review decisions and formally reframing native macOSVirtualization.frameworksupport as a v0.3.2 candidate — gated on a current-mainrebase, a Darwin socket-path fix, Mac-hardware smoke, and hunk-level review.11. PC2 — Stable at v1.3.0 (Convergence Reference)
PC2 (
pc2.net) had no newmaincommits — it remains on v1.3.0 (paired with Launcher v1.2.9) and serves as the reference implementation the runtime convergence work is validated against, and the baseline the Runtime Library/Explorer was checked against (a0a910…, §4). The live node fleet continues on v1.3.0 with in-place auto-update.12. Other Repositories This Week
@elacity-js/ddrm-reader-*packages (0.0.1 → 0.2.0, backend v0.2.1–2.4).website-rebuild-2026: six-route IA, new pages, hero, 21 redirects, honesty/stats/buzzword sweep. Staged, not yet live.feature/brand-identity-2026).2b5e89d3), fixednode.shArbiter-init PGP dependency (d09830e0); supernode guide rewrite + validator monitoring.Audited, no in-window activity:
v3-drm-protocol,media-player,lit-keystore-moleculer. Off-audited-repos (narrative):Essentials(Base-chain support; repatriated to GitHub),monitor.elastos.io(Elastos Node Monitor rebuild).13. Convergence Lens — One Reader, Many Surfaces
The through-line this week is the same protected-content capability appearing on every surface at once, each on the right trust foundation. PC2 ships dDRM playback with host-process CEK containment;
ddrm-readerpackages that capability as a portable, security-first npm family (server decrypts, client renders a render-IR, plaintext never leaves the backend); the Elacity web app consumes it for non-media content; and the Runtime re-implements the file-and-content experience around it on capability-brokered providers. Even the node-operator work rhymes with the thesis — the supernode hardening, ECO-sidechain removal and monitor's "fail-closed, show-what's-wrong" posture mirror the runtime's "least authority, always auditable" principles. The cores are frozen, but the capability model is propagating outward to every surface a user — or a node operator — actually touches.14. Looking Ahead
req_stale_or_futuretimestamp issue, finish CI/CD to github-action deployment, and continue platform integration via the new npm modules.15. Summary Statistics
Window: 2026-05-29 → 2026-06-04 (since report #20)
Stats source:
git logon local/public/private clones, bucketed by author date and deduped by SHA. Line counts omitted for the runtime doc-only commits and the elastos-org node-ops commits (not cloned).main(~33, + 11 package tags), websitewebsite-rebuild-2026(26), elacity-webfeature/brand-identity-2026(5), runtimesash/local-test-v030(~2).@elacity-js/ddrm-reader-*0.0.1 (May 31) and 0.2.0 + backend v0.2.1–v0.2.4 (Jun 4); Elastos Node Monitor relaunch (monitor.elastos.io, Jun 4). No new PC2/Runtime core tags (those were cut in the previous window).16. Data-Quality & Off-Repo Notes
ddrm-readerandjs-sdkwere audited this cycle via authenticated read-only clones (serialised, no bulk operations).v3-drm-protocol,media-player,lit-keystore-moleculerwere audited and had no in-window commits.Essentialsandmonitor.elastos.ioare summarised from team updates (not cloned/measured here);Elastos.Nodecommits are cited by hash from the elastos org (not cloned).upstream/*Puter remote.17. Key Links This Week
Elastos.Node@2b5e89d3· node.sh Arbiter fix —Elastos.Node@d09830e0Beta Was this translation helpful? Give feedback.
All reactions