ElastOS Weekly Shipping Report — Week of August 22 – August 28, 2026 #35
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.
Uh oh!
There was an error while loading. Please reload this page.
Elacity Labs — Weekly Team Update for the World Computer Initiative (WCI)
August 22 – August 28, 2026
ElastOS Runtime v0.7.0 is released. #38 merged to
main31 August; the GitHub Release went up 1 September. That release is the Runtime foundation for ElastOS v2. Coming out of #34: last week’s source became the stacked review train (#29 → #36) that 0.7 rolled up. Marketplace cut elacity-web 4.6.1 → 4.6.6 and drm-api 0.13.1. Hyper/Hey had a real mesh week. Halborn Secure Code Review of mainchain v1.0.3 started 28 August. ESC / EID / Arbiter / the bridge stay closed on purpose. PC2 product-quiet. ELA tip ~2,284,075.Chain status: mainchain producing under BPoS and still being hardened. Halborn’s independent review of pending v1.0.3 is underway (Elastos.ELA only this round). Private ESC / EID / Arbiter fix-and-proof work continues — still not on public GitHub. Restart is still not cleared. Do not send funds into paused sidechain or bridge flows. Mainchain postmortem.
Key Links This Week
main8ac18bec) · #38 merged · stacked #29–#36 · #39bash <(curl -fsSL https://raw.githubusercontent.com/Elacity/pc2.net/main/scripts/update.sh)curl -fsSL https://elastos.elacitylabs.com/install.sh | bashTable of Contents
1. The Big Picture — Runtime v0.7.0 Released
The headline this cycle is the release. ElastOS Runtime v0.7.0 is on GitHub. #38 merged to
main31 August; the Release was published 1 September on tip8ac18bec.What 0.7 is: the reviewed 0.7 workspace on
main— protected-content foundation, collaboration, Home/platform, Wallet, Assistant / model-provider, Library / Marketplace / player UIUX, GBA, receipted source-home install. That is the Runtime line we take into ElastOS v2. See §3.#34 said the freeze contracts had entered published source. This cycle split that source into a reviewable PR train, then rolled it up.
Zeroth — chain doors. Mainchain is live. ESC, EID, Arbiter, and the bridge stay closed. Halborn opened the independent review of v1.0.3 on 28 August. That is not a reopen, and it is not “trust us.” See §2.
First — how 0.7 was assembled. Eight stacked PRs, one contract each: #29 identities and grants; #30 threshold custody; #31 bridge-authenticated reconstruction; #32 custody-provider process; #33 Wallet-signed rights; #34 Runtime release authority; #35 chain evidence + typed decisions; #36 lifecycle (mint / buy / play / closeout). #16 merged onto
upstream/0.7-dev; #38 merged that line tomain. #39 continues Library/marketplace and two-Runtime work on the v2 path. See §3.Second — Assistant grew a real substrate. Typed model boundary, private workspace persistence, Chat and Build workflows, offer-driven Studio runs, safe markdown + math rendering. Model side: provider coordinator, bounded adapters, durable offer/run state, verified native provider execution. Legacy AI provider paths were retired, not deprecated in place. See §4.
Third — Home became authority-conscious, and the shell family got its reviewed UIUX pass. Recovery Kit is now required before first Profile (last cycle it was skippable). Authority-safe lock face, canonical window chrome, Sign Out gated on signed authority. Assistant, Browser, Chat, Documents, Inbox, Library, Marketplace, People, Services, System, Wallet, Wallet-Connectors, Archive, GBA — one shared token vocabulary. See §5.
Fourth — marketplace kept shipping. elacity-web 4.6.6: Home/Explore cards stop asking the chain for every listing; grids use stored prices and slim documents; Flint stills when media is missing; shops-list density. drm-api 0.13.1: poster stills from the token image CID, not the media file; cheap-grid fetch. Edge: HTTP/2 + gzip + immutable
/assets/on base.ela.city. See §7.Fifth — Hyper / Hey after a quiet week. Desktop (Skia
hyper-desktop) landed in the Hyper repo, plus Android CI and a Mac DMG packager. Android: group member cards, workspaces vs private groups, force-relay for hide-IP contacts, talking-head video adapt, a signed-APK workflow so sideloads can replace earlier builds. Engine: sealed 1:1 DMs, unpublished media that stays unpublished across restart, radio self-heal that does not remesh every few seconds. Android CI is green; desktop CI is still red on HEAD. No GitHub Release tag — source and sideload, not a store launch. See §8.Also: browser-local-exit orphan reap #24 merged. Source-home CI matrix now emits a proof artifact. WSL-first Windows strategy is a written doc.
elastos-loggerwent from PoC to a crate with a tracing migration. PC2 shipped zero product commits — quiet by design.2. Elastos Status — Halborn Underway, Sidechains Still Closed
Public framing only. Finding registers, live-defect recipes, and unpublished recovery trees stay inside the recovery engagement — same discipline as #32–#34.
What is open vs shut
Long form: Mainchain postmortem (August) · honest recovery log.
External audit (community-safe)
Halborn started the independent Secure Code Review of the pending mainchain release (v1.0.3) on 28 August. Scope this round is Elastos.ELA only: post-incident hardening (consensus and merged-mining, reorg and mode transitions, P2P/RPC resilience, activation and mixed-fleet checks), static review plus dynamic testing against a running node where required. SPV, Arbiter, and sidechains are not in this pass. We will post again when there is a public certificate to point to; do not expect a running feed of engagement detail before the report lands.
Layers
Mainchain remains live. ESC, EID, and the Arbiter bridge remain offline on purpose. Public GitHub for those trees did not move this week — recovery work stays on the private org until it is safe to publish. Operator toolkit remains Elastos.Node v1.2.3. Mainchain private tree was quiet this window (Halborn is reviewing the pending v1.0.3 line).
Private ESC / EID / Arbiter prep (high level)
The private fix-and-proof cycle continued. Roughly 159 commits landed on the private trees this window (ESC 59, EID 59, Arbiter 41) — release stamps, rehearsal/test integrity, and follow-through on last week’s audit line. Nothing from that cycle is on public GitHub. Restart is still not cleared; remaining blockers are operational (rehearsal completion, soak, fleet readiness), not “code is done so we turn it on.”
Adversarial review continues to reject proposed fixes that are worse than the defects they address. That is the bar. We will announce reopen — we will not surprise people into a half-open bridge.
3. Runtime v0.7.0 — What It Contains
Release: v0.7.0 · 1 September 2026 ·
main8ac18bec· CHANGELOG [0.7.0] - 2026-08-31. Stamped artifacts report0.7.0; unstamped source builds report0.7.0-dev.This is the coordinated workspace release. It is on
mainand tagged. Next: ElastOS v2 on this foundation.In the tag (from CHANGELOG / annotated tag)
model-provider,assistant,elacity-player, andgba-nonogram.publish-release.sh --dry-run(local rehearsal, no network). Wallet-connect asset hashes restamped.How it was assembled (the PR train)
Last week’s source became eight stacked PRs, one contract each, then #38 rolled them onto
main.#16 (collaboration candidate + #24 orphan reap) merged into
upstream/0.7-devon 28 August. #38 merged that line tomainon 31 August.#39 continues Library video / marketplace browse-buy / two-Runtime work toward ElastOS v2.
4. Runtime — Assistant + Model Provider Substrate
Assistant is no longer a thin wrapper on an external AI SDK. It has typed contracts on both sides of the Runtime boundary and durable state that survives restarts.
Assistant surface. Chat and Build workflows; private workspace persisted; typed model boundary. Offer-driven Studio runs; copy transcript through Home; safe markdown + math rendering (largest single non-merge landing this week). Object-studio outputs rejected in Assistant. Access bound to exact runs.
Model boundary. Offer and run contracts; bounded backend adapters; strict stdio process; durable offer/run state and run journal; provider coordinator. Runtime registers a verified model provider, authorizes typed model resources, loads private provider config, and requires verified native provider startup. Legacy AI provider paths were retired (
−4,248in that refactor) — gone, not deprecated in place.PR anchor. #17 remains the review path for the model side; this week it grew a Runtime-side coordination story.
No external-provider credentials or private-provider secrets travel through Home or Runtime durable state.
5. Runtime — elastos-logger, Home, and Reviewed UIUX
Logger (PR #25)
The logger crate stopped being a PoC. Per-component ring files, per-record component override,
component!modules, server bootstrap withELASTOS_LOGroot, and a coordinated tracing → logger migration across server and library crates. VM provider payloads no longer leak into logs. Developer guides updated. #25 is the extraction path from the dKMS/ESP branch.Home (PR #23 still the review path)
Recovery Kit is now required before first Profile — last cycle’s Profile-first welcome made Recovery skippable; that is closed. Authority-safe lock face; canonical window chrome modes; object-first desktop defaults; Home-owned Trash; Runtime-owned appearance preferences; mobile Control Centre. Sign Out gated on signed authority. Connector ceremony stays on its authorized sheet. Canonical DID key authority enforced.
Reviewed UIUX (~15 apps + platform)
The
feat/0.7-uiux-candidateline landed a coordinated pass: Assistant, Browser, Chat, Documents, GBA, Inbox, Library, Marketplace, People, Services, System, Wallet, Wallet-Connectors, Archive. Wallet-family apps vendor shared UI tokens; capsules carry their own icons; first-party apps align with Home chrome. This is on the v0.7.0 line.6. Runtime — Capsules, Collaboration Hygiene, CI
Content capsules. gba-nonogram and licensed Nonogram Advance on the 0.7 line. #26.
Collaboration. Bootstrap peers pinned by canonical DID. Deterministic product acceptance test added. #27 + #28 remain the two-PR collaboration stack onto
main/ foundation. #24 (browser-local-exit orphan reap) merged into the collaboration candidate — a real orphan under crash-restart.CI / Windows. Source-home matrix now emits a first-class proof artifact, not just a green tick. Home CLI is exercised directly in local carrier smoke. Source-home stays portable across hosts; collaboration mode is explicit. WSL-first is the written Windows target; the experimental native Windows source gate stays experimental. #19 is still the matrix review path.
dKMS / ESP. #15 remains open as the ESP substrate review; logger extraction toward #25 is the split we wanted.
7. Marketplace — elacity-web 4.6.6, drm-api 0.13.1, Edge
Indexer readiness and storefront shipping — not an ESC reopen. The first-pass Runtime-only draft missed this entirely.
elacity-web — 4.6.1 → 4.6.6
Release train on
release/base-networkafter last week’s 4.6.1:fetchNFTItemson Home, Explore, and shop grids/viewchrome before accessMerged PRs #47–#51.
drm-api-layer — 0.13.0 → 0.13.1
Poster stills written from the token image CID, not the media file. List fetch skips the metadata N+1. Named bump 0.13.1; follow-on cheap-grid work is on the same line (HEAD package 0.13.2).
release/nextwas not re-bumped this window (still last week’s 0.8.3 align).Adjacent infra
/assets/on base.ela.city (#7). ipfs.ela.city gateway work closed at the edge of last weeketh_getLogs+ Base 8453 genesis) — treat as the #34/#35 seam, not a new ship this week8. Hyper / Hey — Mesh Week After Quiet
Last window these two were quiet. This window they were not. Hyper is the Android + desktop client; Hey-engine is the shared Rust core (same engine the Runtime capsules use).
Shipped in source / sideload — not a store launch, no GitHub Release tag.
~42 Hyper commits and ~44 Hey-engine commits in the window. Dependabot noise on Hyper is open and not the story.
9. Essentials Overhaul — Still Local (Not Shipped)
No new push on the Essentials GitHub trees this window. The local overhaul from #34 remains uncommitted — not a store release. Nothing new is claimed shipped. Independent custody review still sits in front of production changes.
10. PC2 — Quiet by Design
pc2.netmainafter #34 — zero product commits, no PRs, no release. Operator line remains v1.4.0.Convergence holds: PC2 is a consumer of Runtime’s finished contracts. This week those contracts moved from a review train onto
mainand v0.7.0 (§3). PC2 consumes that line as we move toward ElastOS v2. First seams: dDRM viewer path and marketplace buy/trade against Wallet-signed rights.11. Release Engineering
main8ac18bec(1 Sep) · 0.7-dev merged 31 Augmainmain· #16 → 0.7-dev · #24 orphan reap12. Convergence Lens
13. Looking Ahead
14. Summary Statistics
Week of August 22 – August 28, 2026 (facts through 1 September amend: v0.7.0).
Runtime volume below is the first-pass dedup (unique SHAs collapsed across the 12-branch protected-content stack). Raw undeduplicated Runtime was 240 commits / +439,929 / −74,930 / 2,773 files — the same logical change on multiple stacked branches.
Runtime commit-type histogram (dedup by subject): feat 116 · fix 45 · docs 32 · merge 17 · test 12 · refactor 9 · chore 6 · style 2 · build 1.
Runtime PRs. Opened #26–#36 in-window, plus #38 (28 Aug) and #39 (29 Aug). Merged: #38 →
main(31 Aug), #16 → 0.7-dev, #24 orphan reap. Closed: #18.Releases. Runtime v0.7.0 (1 Sep). PC2 still v1.4.0. Marketplace in-repo bumps as above. Node still v1.2.3.
People (workstream lens): Anders Alm — protected-content stack, Assistant + model substrate, UIUX rollout, Home authority, Chat + capsules, CI · Irzhy Ranaivoarivony — elastos-logger + tracing migration, custody-provider hardening, stack merges, #38 / #39 · SashaMIT — Recovery-Kit-first Profile, gba-nonogram capsule, source-home portability, marketplace grid/stills, Hyper CI/DMG · Hyper/Hey mesh (EverlastinOS) · chain recovery / Halborn coordination.
15. Notes
main. Next product line: ElastOS v2.Quick fact card
main· #16 → 0.7-dev · #24 orphan reapCadence: weekly updates. Previous report — Week of August 15 – August 21, 2026 (#34). This report — #35.
All reactions