ElastOS Weekly Shipping Report — Week of June 12 – June 19, 2026 #21
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)
June 12 – June 19, 2026
The week dDRM went live — then got hardened all the way to a pre-mainnet product. Two arcs defined the week. In the first half (Jun 12–16), the dDRM-into-Runtime epic came alive end-to-end over the real transport: a consumer opens a protected asset whose content key is released by a live 2-of-3 quorum over Carrier, the asset streams and renders byte-identical to PC2, and a creator mints a real protected asset that persists as an owned Library object + a
.ddrmcapsule — with popup-free re-opens and live staged progress making it feel human. In the second half (Jun 16–19), the team turned the working demo into something shippable: a pre-mainnet security and audit hardening pass (CEK integrity, tamper-evident custody, threat model, fail-closed egress), forensic watermarking (visible + invisible DCT-QIM, authenticated by the buyer's signed grant), a brand-new Capsule Inspector "glass box" for auditing capability/authority live, and a CI gate that runs the full verify on Linux. Around the runtime,media-playershipped DRM releases 0.12.6 / 0.12.7,elacity-webreached 4.4.0 with a tier-4 web-security remediation, ElacityLabs.com gained a Fourthwall merch store + on-site network map, the Elastos website finished its rebuild pass, and Node for Ubuntu v1.1 (Jun 15) gave operators a safety release. PC2 v1.3.0 stayed the frozen conformance oracle throughout.Table of Contents
1. The Big Picture — From Working Demo to Pre-Mainnet Product
The dDRM convergence epic crossed two thresholds in one week. Early in the week it crossed from "implemented" to "working": a protected asset's CEK is released by a real 2-of-3 threshold quorum over Carrier, the runtime runs the multi-segment CENC decrypt, and it streams cleartext to the viewer — proven byte-identical to PC2 by an end-to-end render test — while the creator path went end-to-end (encrypt → package → on-chain mint persisting an owned Library object +
.ddrmcapsule). Later in the week it crossed from "working" to "shippable": the team ran a pre-mainnet security/audit hardening pass, added forensic watermarking that binds a leak to a buyer's signed grant, built a read-only Capsule Inspector so authority and provenance can be audited live, and put a full Linux CI gate around the dDRM crates. Across two runtime branches (feat/ddrm-hardening-and-creator-parity,feat/capsule-inspector) that is ~81 commits for the week. Beyond the runtime, the platform repos converged on releases:media-playercut 0.12.6 / 0.12.7 DRM fixes,elacity-webreached 4.4.0 with a tier-4 web-security remediation, ElacityLabs.com shipped a Fourthwall merch store + on-site network map, and the Elastos website finished its rebuild. Node operators got the v1.1 safety release (Jun 15). PC2 v1.3.0 remained the frozen conformance oracle.2. Runtime — Creator Mint + Live Quorum Consumer-Open Over Carrier
Both halves of the dDRM loop run live, against the real Base chain and the real Carrier transport:
33b6088, roadmap A2), replacing mocks with the production contract surface.73d80ee); the object-provider was wired into the creator-gateway launch (1e9d6c1); the Mac dev gateway launch was fixed (dc32fa0, Day 136 handover)..ddrmcapsule, with trade-approval and a recoverability keystone fix (45f094b).4ccf3f5); Day-139 docs record it wired + tested (e32a045).27fb1f0) — the conformance bar held all the way through the live path.--quorumopen mode —ddrm-media-authoritygained a--quorumopen mode + helper verify (daa1141).viewer_open(855d3a9) and brings the dKMS recovery quorum LIVE, consumer-open ready (af60f44).d53bd68): the full loop runs over the real Carrier transport.3. Runtime — Frictionless Re-Open, Warm Quorum & Live Progress
Making the live path feel instant and human:
d6412e0, Phase A) — a long-lived key-provider reuses node sessions across opens, so the first protected open isn't penalised by cold-start latency (open-latency Tiers 1+2).018900d) — re-opening previously-authorised content skips the per-open wallet prompt via a cached wallet-signed delegation (PC2's secure-view session, ported) while keeping bearer-token / owner / expiry checks intact.4fc4cf5) — Home surfaces real staged progress for protected (dKMS) opens (key release → fetch → decrypt → render) instead of an opaque spinner.adc14ba).4. Runtime — Cross-Device Parity, Chat & People (June 12 Update)
Reported in the June 12 Runtime update, the main line reached cross-device coherence (team-reported; not all of it is on the public remote yet — see Data-Quality):
elastos://chat/join?..., People refresh behaviour, app-opening paths, and local smoke tests.5. Runtime — Pre-Mainnet Security & Audit Hardening
With the loop working, the back half of the week was a deliberate pre-mainnet hardening pass on
feat/ddrm-hardening-and-creator-parity— the work that turns a demo into something safe to put real value behind:3f282dd) — CEK integrity, a tamper-evident audit trail, and action enforcement across the dDRM path; a broad hardening pass.b08d5d8, pre-audit ElastOS Weekly Shipping Report — Week of Mar 2–6, 2026 #5) — reduced what protected-content metadata leaks, with an explicit written threat model.622fe69) — channel padding made negotiated and off by default, so it's available without imposing cost on every exchange.2a4ca10) — a dead node can no longer wedge an open: recovery tolerates a missing share within the threshold rather than stalling.0e1bd96) — validate wallet linkage before resolving the rights-provider binary, closing a resolution-order gap.0eac1d0) — the forensic grant anchor is retained inside the tamper-evident custody chain, so a later leak is provable against the original grant.58380d3) — audit item 6 cleanups, and media-tier egress reclassified as closed-by-construction (the path can't leak by design, not by check).ca3e5d9) — documented findings, a confidential-compute audit, README + lockfiles for reproducibility.6228407) — wrote down the containment model per asset tier and the protected-content update.5bc2381) — a consolidated fix-pack and a repeatable runbook for testing a dKMS open ahead of mainnet.6. Runtime — Forensic Watermarking & Asset-Tier Protection
A major new capability landed: protect rendered output (not just the key) and make a leak traceable to the buyer who leaked it:
c580160) — images, comics, text/code, and SVG render through a pixel-lock path rather than handing raw bytes to a viewer.4df439b) — PDFs render server-side with a warm session + watermark, so plaintext never reaches the client.1cba0f7) — a visible full-address mark plus an invisible DCT-QIM (frequency-domain) mark that survives casual re-encoding.b01ed34) — the forensic mark is bound to the buyer's signed grant, so a leaked asset points back to a specific authorised open.273d0aa) — pixel-lock decode/raster size is bounded to stop a malicious asset exhausting memory.eae67ff,9bc2c54) — serve-time content sniffing plus an html-lock CSP / nosniff to prevent mislabel and EPUB-style escape, with an honest written scope of what the watermark does and does not defend.b8cafe3design;fadad72Phase 5;681d10aPhase-0 feasibility) — roadmap + design for audio/video forensic watermarking, then Phase 5 chunks 1/2/6: a variant schema, a canonical codeword, and an offline extractor to recover the mark from a leaked file.294884e) — rendering parity across tiers, a faster mint, and Library UX polish.d418117) — protected audio now routes through the media player rather than the object viewer (pairs with themedia-playerreleases in §10).7. Runtime — Capsule Inspector: The Glass Box
A brand-new branch,
feat/capsule-inspector(~31 commits, Jun 17–19, AI-pair-programmed under the team's direction — see Data-Quality), built a read-only "glass box" so the authority a capsule actually holds can be inspected live instead of trusted blindly:879a5ea, Phase 1) and a live read-onlyelastos://inspect/*handler with conformance tests (741ca98).ef0b19d) — a tested two-tier scope ensures inspect can't be used to widen authority; later proven with a contract-fidelity + no-authority-leak test that documents the object-capability reality (7d85ec9).9c8078a), product-side inspect provider on the shared registry (261d77a), manifest-backed catalog product view (df03702), sub-provider coverage + per-capsule audit (6fa942b), typed affordance schemas via metadata reflection (04039d3), and provider authority rendered "in the glass box" (28ed9b9).997569c) and an invoke preview that shows the gate a provider operation would require (a4a032b), plus a provenance CID surfaced per object (9ae8e12).4d88281) — surfaces the signer DID + signed attestation for live-data fidelity.f7d191f), carrier-leg e2e verification reaching ~65% plan reachability (f25e330), a fail-closed approval decision core with inspect/intent preview (1bfe59f,2b413b0), and a KNOWN_GAPS ratchet that turns build-visible gaps into#[ignore]d tests so they can't silently regress (f32f29f).8. Runtime — CI Hardening, Playback Fixes & Release Hygiene
9f57172) — the dDRM capsule crates are now gated and the fulljust verifyruns on Linux CI.verify-cisplit (2ecb7a6) — split out averify-cijob (the full gate minus the Carrier-network smoke) suited to GitHub Actions, with a branch-scoped trigger so the feature branch is gated too (a01cecc).e350a49,46cbeed) — pinnedwasm32-wasip1inrust-toolchain.tomland installed the target for the verify job's Carrier smoke;rustfmt+ripgrepinstall for the verify job (391a438).dade8af) — cleared pre-existing clippy drift sojust lintis green.2b4ea05), dev-mode fencing out of release builds + PC2 creator-core parity (ab3adb3), and Day-138 handover (a22d73c).9. Elastos Node for Ubuntu v1.1 — Operator Safety Release
Elastos Node for Ubuntu v1.1 went live (June 15) — a safety release for Council members, BPoS operators and ELA node operators that makes node operation safer, clearer and easier to manage while keeping existing keystores, chain data, node layout and familiar commands intact:
This is the operator-facing counterpart to the runtime's "least authority, fail closed" posture — the same principles applied to the L1 node fleet that the WCI mandate (proposal HeyPuter#212) supports. Full update: https://elastos.click/Node-v1-1
10. media-player — DRM Releases 0.12.6 / 0.12.7
media-player(Jun 17, Irzhy Ranaivoarivony) shipped two tagged DRM releases that tighten the web3 decryption path — the consumer side that pairs with the runtime's protected-audio routing (§6):788d587) — reject deprecated Lit DRM systems and restoreweb3-drm-v1as the default, removing a stale decryption route.f7251cb) — override a down RPC with the Elacity RPC so playback isn't blocked by an unhealthy upstream endpoint.43862db) — convert Ed25519 → X25519 for the ECDH operation on the web3-based path, the correct key form for the key-agreement step.11. Elacity Web App — 4.4.0, Brand Identity & Tier-4 Security Remediation
elacity-web(Jun 12–18; SashaMIT, Irzhy, AI-assisted) drove the marketplace toward go-live acrossfeature/brand-identity-2026,release/go-live-integration,release/4.4.0andrelease/base-network:5e91ff89); shared Lottie logo on splash + welcome modal (eadd77d4); restored the pulsing splash logo and refreshed favicons to the 2026 brand (1173f402).e2aad409) — the large deletion count is this cleanup, not regression — and unified the wallet-mode switcher with the Explore segmented control while decluttering the sidebar header (82035f98). The notification icon was swapped to an Alarm icon (e3e4dcbd) and then reverted to the original Bell (433c3c37).05b70e4e, ELACITY-2235) — a dedicated web-security remediation, plus client-side hardening (headers, session, telemetry, service-worker cache) (f5700f5d) and an nginx header snippet for the rsync/nginx prod deploy (a869f43a).818067aa) and merged throughrelease/4.4.0intorelease/base-network(01a57cf9), lining the brand refresh and Base-network work up for a coordinated launch.12. ElacityLabs.com — Merch Store, Network Map & Homepage
ElacityLabsWeb(Jun 16–19; SashaMIT, AI-assisted) grew from a narrative refresh into a feature push:20aaab8a0) at/merch, with product-page accordions from the Fourthwall API (2fb7953b2), env vars declared on the Render API service (835a3c0f6), a dev-origin default for the merch API base (c6d584217), and merch UX, section headers, and discount pricing (5c3b79af3).1f658fd82), plus merch store + homepage polish and a brand logo refresh (dfb0d8c84), wider FinalCTA copy + inline attribution + spacing fixes (4d6a79c58), and the earlier "Need help?" docs link in the Quick Start commands (5489fc9b2).d7fe04815), then a perf + hygiene sweep toward 10/10 (code-split, sanitize, dedup, request-abort) (0356dc9ec).13. Elastos Website — Final Optimisation & Professional README
elastos(website-rebuild-2026+main, Jun 16, SashaMIT) finished its pre-go-live pass: full site overhaul, asset optimisation, SEO, and orphan cleanup (1e2efd3f) — the very high deletion count is removal of legacy/unused assets, not content loss — and a professional README for the Elastos.net website (eddc14d1). The rebuilt site is staged and optimised, awaiting a coordinated launch alongside the Elacity web refresh.14. PC2 — Stable at v1.3.0
PC2 (
pc2.net) remains at v1.3.0 with no newmaincommits — still the conformance reference the runtime dDRM port is validated against (the byte-identical render test in §2 measures against PC2's output). The live node fleet continues on v1.3.0 + Launcher v1.2.9. (Documentation/licensing housekeeping — rootNOTICE, AGPL §13 operator note, and an IP/licensing strategy memo — landed off the release line and don't change runtime behaviour.)15. Other Repositories This Week
web3-drm-v1), Elacity-RPC override, Ed25519→X25519 ECDH on the web3 path.release/base-network.website-rebuild-2026; professional README onmain.KNOWN_PARTNERS.Audited, no in-window activity:
v3-drm-protocol,ddrm-reader,js-sdk,lit-keystore-moleculer.16. Convergence Lens — The Proof Became a Hardened Product
Last week the convergence thesis became something you could watch happen: a quorum cooperates over Carrier to release a key none of them holds whole, the runtime decrypts in containment, and it renders byte-for-byte identical to PC2. This week the thesis grew up. The same open is now defensible: the key path is tamper-evident and fails closed, a dead quorum node can't wedge an open, and the rendered output carries a forensic watermark bound to the buyer's signed grant — so the question shifts from "can it leak?" to "if it leaks, who leaked it?". The Capsule Inspector makes the authority model auditable rather than asserted — you can see, before you grant, exactly what a capsule can touch and what gate an operation requires. And a full Linux CI gate now stands behind the dDRM crates so the bar can't quietly slip. Outside the runtime, the platform repos all moved toward release in lockstep —
media-playerandelacity-webcut versioned DRM/marketplace builds, ElacityLabs.com and the Elastos website staged their refreshes, and the L1 node fleet got a safety release on the same "least authority, fail closed" principles. The remaining work is soak-testing, breadth and launch coordination — not proof, and increasingly not hardening either.17. Looking Ahead
elacity-web4.4.0 / Base-network, the ElacityLabs.com merch + map refresh, and the Elastos website rebuild together.18. Summary Statistics
Window: 2026-06-12 → 2026-06-19 (full week)
feat/ddrm-hardening-and-creator-parityfeat/capsule-inspector*Runtime insertion totals include vendored/generated content; commit counts are the truer effort signal.
†elacity-web deletions are dominated by the XMTP-stack removal (cleanup, not regression).
‡Website deletions are legacy-asset / orphan removal (optimisation); the portal journal entries are image/video-only (binary), so line counts aren't meaningful.
feat/ddrm-hardening-and-creator-parity(50, SashaMIT) +feat/capsule-inspector(31, AI-pair-programmed under team direction).feature/brand-identity-2026/release/go-live-integration/release/4.4.0/release/base-network— SashaMIT (9), Irzhy (3), AI-assisted (2).feat/merch-store+wip/homepage-narrative-refresh— SashaMIT (6), AI-assisted (5).19. Data-Quality & Off-Repo Notes
feat/capsule-inspectorbranch and parts of the web hardening were committed under the author name "Claude" — these are AI-pair-programmed changes produced under the team's direction and review, not a separate human contributor. They are counted as real shipped work but attributed accordingly here.elastos-runtimeremote yet (publicmainstill ends at the v0.4.0 line), so it is reported as context and excluded from commit counts.2026-06-12 → 2026-06-19; web counts are non-merge to avoid merge-commit inflation.v3-drm-protocol,ddrm-reader,js-sdk,lit-keystore-moleculeraudited via authenticated read-only clones: no in-window commits.media-player(private) did have in-window activity this week (see §10).feature/brand-identity-2026,release/*,wip/homepage-narrative-refresh,feat/merch-store,website-rebuild-2026) are staged and not all live at time of writing.upstream/*Puter remote.20. Key Links This Week
feat/ddrm-hardening-and-creator-parity+feat/capsule-inspector(elastos-runtime)player-0.12.7(Elacity/media-player)Beta Was this translation helpful? Give feedback.
All reactions