This repository was archived by the owner on Nov 10, 2026. It is now read-only.
Repository navigation
ElastOS Weekly Shipping Report — Week of September 19 – September 26, 2026 #39
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)
September 19 – September 26, 2026
Runtime into protected dDRM. A protected file was read on an installed Home. The creator chooses the channel. USDC listings settle at the scale they show. The approval screen is readable. The shelf shows protected items again after they had been hidden since late August. Download rebuilds a
.ddrmthe account already owns, and a purchase in progress stays visible after reload. Buying from a live offer, by shared link or from Explore, is on a follow-up branch. PR 62 and PR 70 are open. Runtimemainis still v0.7.0 — no 0.7.1 tag. The preview host is not posted.Home can use an image you own as the desktop, the Assistant toggle carries the Elastos mark, and a phone layout is in progress on a local branch. Models sit on the next runtime line: the public seed completed a short SmolLM2 reply, one Mac share was proved, and Linux containment is still the gate. No 0.7.2 tag. Marketplace (ela.city) shipped search, live activity, notifications and email, cart and batch mint, creator analytics, reports, and referral links. Web still 4.6.8, drm-api still 0.13.2. Playback there of an object protected on a runtime Home is still open. Essentials and the DAO stayed local. The DAO’s old 2021 ELA/ETH position was emptied and a small test position is live; the rest of the liquidity is not in yet. The Ledger app is a private patch of the current app and has not been submitted. Halborn on mainchain v1.0.3 still underway. ESC / EID stay open; PG cross-chain stays off. PC2 product-quiet.
Chain status: mainchain producing under BPoS. ESC and EID producing; main ↔ ESC / EID open. PG / PGP cross-chain ELA stays disabled. Halborn’s independent review of pending v1.0.3 continues (Elastos.ELA only this round). Private ESC / EID / Arbiter trees were quiet. Exchanges that froze ESC / EID deposits should contact the Elastos DAO before reopening. Sidechains resume · Mainchain postmortem.
Key Links This Week
docs/weekly-2026-09-25bash <(curl -fsSL https://raw.githubusercontent.com/Elacity/pc2.net/main/scripts/update.sh)Table of Contents
1. The Big Picture — Runtime into Protected dDRM
This week’s runtime work lands in protected dDRM. #38 left the installed mint → buy → play journey open. A protected file has now been read on an installed Home. See §2–§3.
Protected dDRM (Irzhy). Three squash commits repack the follow-up line. Most of that text was already in #38. What is new: the installed read; the creator picks the channel; USDC no longer settles at the wrong scale; the approval screen can be read; the shelf shows protected rows again; Download rebuilds an owned
.ddrm; a purchase in progress survives reload. PR 62 is still open. Buying from any live offer is PR 70. The long confirmation is still easy to read as a dead end. The full journey is not release acceptance, and there is no 0.7.1 tag.Home and models. Wallpaper from your own Library (PR 67), the Elastos mark on the Assistant toggle (PR 68), alignment rules for the two-platform installer (PR 69). Phone Home layout is a large local branch, not a pull request. Models continued on PR 71. Anders’ written note, pushed 26 September, is the record for what those builds actually proved. See §5–§6.
Marketplace. First-pass Runtime drafts missed this again. ela.city and drm-api shipped search, a live activity stream, in-app / push / email notifications, a cart with one confirmation, batch mint, creator analytics, reports, and referral links. Versions did not bump. Playback on the site, for an object protected on a runtime Home, is still the open piece and can follow the OS release. See §7.
Essentials, DAO, pool, Ledger. All local or private. Nothing in that set is a public release. See §10–§13.
Not this week’s invention: the signed-model Mac journey, custody-only nodes, and the GCloud encode cuts were #38. The three squash commits on PR 62 mostly restate that surface. Say what changed on top.
Chain / PC2. No new public certificate. No PC2 product commits after #38. See §4 and §14.
2. Protected dDRM — Read, Shelf, Owned Copy
PR 62 ·
feat/protected-content-0.7.1-followup· still open.On 21 September the branch was rewritten into three themes. Treat those as a history pack of work #38 already described (Creator → readable object, custody and external wallets, a shelf and replicas), not as a second copy of that week.
New on top of that pack:
/v2domain;/v1mints are refused..ddrmwhen a live access read says the account holds the token. A local purchase note is not itself a grant. A purchase already in progress shows Continue after reload.Still open: the long confirmation wait is still easy to read as a dead end rather than a wait. The full installed mint → list → buy → open → play → close journey is not release acceptance. PR 62 is not merged.
maindid not move.3. Market Buy — Runtime Branch
PR 70 (
feat/protected-content-listing-buy, open). A buyer can purchase from a live offer found through a shared link or in Explore. Lookups cover token URI, the content-id binding, and the live offers. A listing can be rebuilt from shared data. A purchase record is kept.Adopting that purchase onto a Home that did not list the item — from shared metadata, with owned items marked purchased even when this Home has no listing — is in progress. An asset protected somewhere else should open where it was protected. That adoption is not claimed complete. PR 70 is not merged.
4. Elastos Status — ESC / EID Open, Halborn Underway
Public framing only. Finding registers and unpublished recovery trees stay inside the recovery engagement.
No new public blog this window. Operator toolkit remains Elastos.Node v1.2.4. Private ESC / EID / Arbiter / ELA trees were quiet.
5. Home — Wallpaper, Mark, Phone Layout
PR 67 — set one image you own as the desktop background. Runtime reads it under the caller’s own root and accepts PNG, JPEG, WebP, or GIF from the bytes. App tokens and foreign or non-image sources are refused. Library gets the menu item and lazy thumbnails. Wallpaper bytes are served so a locked-down capsule can actually paint them.
PR 68 — the Assistant toggle shows the Elastos mark. A click plays a short motion, then opens. Reduced motion skips it. Focus return no longer pops a dock label. Presentation only.
PR 69 — the alignment gate matches the installer it guards: Linux x86_64 / aarch64 and Apple silicon. Other platforms fail closed. Browser protocol revision is 2.1. No tag. README still says the candidate is not published.
Phone layout — about 64 commits on a local branch (
feat/home-phone-layout). Not opened as a pull request. The phone Home is the app grid: 44 px targets, sheets from the bottom, long-press menus, a push drawer for sidebars, Spotlight and Notification Centre readable on a narrow stage, Reconnecting when the gateway stops answering. This is not in a preview and not onmain. The team kept tightening that layout against the same local build. It is still not a shared branch.Public Home. It received a clearer key message and the desktop-icon persistence fix. It has not received the full source branch. Browser Close is repaired in source and passed an isolated check. That repair is not on the public Home. A reviewed Mac Browser build still needs ordinary navigation, input, media, profile, reload, and close checks.
6. Models — 0.7.2 Evidence, Acceptance Still Open
PR 71 (
feat/0.7.2-models) and the CI pin beside it (fix/0.7.2-model-ci-node) carried most of Anders’ week. A large share of those commits are evidence notes. The code that moved:What the builds proved. The public seed completed Marketplace Get of its signed SmolLM2 capsule, one short reply, then restart and reuse. That was the failure at the end of last week’s runtime report. The seed already held SmolLM2 before that Get, so a fresh download onto the seed is still unproven. SmolLM2-135M shows the install path and a short reply. A useful local Assistant is still open: a measured model on the seed, and the signed Qwen3.5-9B journey on a suitable Mac. Qwen3.5-4B is the first seed candidate, still subject to the engine, signing, answer quality, and resource checks. An earlier Mac build recorded a real Qwen3.5-9B reply, save, reload, and restart. That receipt belongs to the build that produced it.
A fresh Mac Home received the full signed package from another holder. On matching isolated Mac builds, a second Home found that exact model, requested access, and received a reply computed on the owner Home. The owner ended the grant in Inbox, and the other Home lost the offer. Refusal, recovery, and the wider failure cases are still open. The public seed has not run this matching-build journey. Remote sharing is outside the focused 0.7.2 release. The call also asked for a history of handled Inbox requests that stays after dismiss. The written note does not record that history as done.
Earlier Mac builds completed real replies through Venice and OpenRouter. Named connections can be saved and edited. Public hosted calls stay paused. Installed Mac and Linux proof is still required that the model process cannot bypass Runtime’s route, and that approval and End govern every send. Jev stays optional. No 0.7.2 tag. The preview host stays unposted.
Isolation is the largest release gate. The public seed’s local model process does not yet have Linux containment. The installed Mac model process can reach more user files than the capsule contract allows. Controlled tests have moved hosted consent and child isolation forward. The installed paths are still open. Next is a reviewed Linux containment plan for the seed, then installed Mac and Linux proof of the ordinary Inbox approval and End journey.
Where it sits. PR 71 is the model source, stacked on PR 64. The seed preview is separate: Runtime and Home UI. PR 65 through PR 69, and PR 62, stay open. None of that contributor work is in a release candidate. PR 62 adds another external-data consent path, and that path has to use the same Runtime authority as hosted AI. The call also had PR 62 overlapping this model work in about 81 files. Anders’ note is the 19–25 September team sync.
CI. PR 71 failed its UI source checks.
3d51690cpins Node 26, the major used by the passing local checks, onfix/0.7.2-model-ci-node. That pin is not in PR 71. A passing GitHub run is still open.Community room. The release plan now names a public-room journey and the first visit it needs. Chat still needs an owner, a delivery choice, and installed tests. Carrier connects peers directly, so a two-Home test will not prove delivery for people behind home routers. Relay qualification is later. On the call, join and leave lines were still breaking the room.
Update. The plan’s next stable line is 0.7.2, because a preview build already reports 0.7.1 and the updater compares versions. There is no 0.7.2 tag, and this note does not publish that host. The plan calls for an old-client 0.7.1 → 0.7.2 test, then a second signed update with recovery, keeping the person’s state. The updater today replaces its own binary before final validation, and it does not restart Home.
Decisions still in front of a candidate: how Chat ships, which Linux containment method protects model providers, which model the seed offers for regular use, who holds signing keys, who restarts Home after an update, and which public-seed accounts may configure and pay for hosted AI.
Later than this release: the wider Qwen distribution and benchmark matrix, remote model sharing, remote Browser placement, protected purchases, Linux ARM64 delivery, and relay qualification. The focused 0.7.2 shape is a usable public Home with a local Assistant, approved hosted use, Community Chat, a local Mac Browser, and an update that keeps state. There is no date on it.
7. Marketplace — Search, Activity, Notifications, Cart
Versions did not bump. elacity-web ~119 commits and drm-api-layer ~75, both on
release/base-network, plus one events-watcher commit and two on v1-rest. This is the live ela.city path, not a new storefront brand.Search. Navbar search moved to GraphQL
searchAll, then Atlas for ranked results, zero-result analytics, click tracking, and an admin search tab. Result thumbs and vocabulary match the rest of the product.Activity. A live stream: trade, subscription, and reward events fan out as a ping, and the page refetches. Paginated feeds keep the newest page subscribed. Transfer batches are covered. Anonymous subscribe works on public channels.
Notifications. In-app feed, grouping, dismiss, preferences, and badge hygiene. Web push (opt-in, service worker, retry when the worker is still installing). Email for verify, welcome, and the sale / subscription events, branded and pointed at the earnings pages. Alert choices sit on the profile email field.
.cityaddresses are accepted.Buy and mint. A marketplace cart checks out in one confirmation. Multi-asset mint deploys with one signature. Cards show scarcity, ratings, and media type. Sales export to CSV. A one-time install prompt exists for the PWA.
Creator tools. Funnel, audience, and trend panels. Average order value. Page views split from plays. Owner self-ratings are blocked.
Trust. Report on an asset, an admin moderation queue, and a delisted notice.
Referral. An Affiliate tab, short referral codes, and binding when a new creator mints or opens a shop. Eligibility ignores a stored link for wallets that are already creators or holders. This is product wiring on the current site, not a new public launch announcement.
API companions. drm-api holds the search service, the activity fanout, notification feed and push prefs, creator-analytics rollups, flags, CSV-shaped trade history, and Mongo-first listings. Referral and share services were lint-cleaned so CI passes. events-watcher includes the log index on the event payload. v1-rest escapes search input.
Playback of an object protected on a runtime Home, in the ela.city player, is still open. It is the remaining piece on the site. It can follow the OS release. Key handling for that player still has to be walked through before it is a claim.
Still 4.6.8 / 0.13.2. No marketplace release tag this window.
8. Hyper / Hey
Hyper 2 commits on
main: live file-upload percent; VPN egress pinned to Hyper’s own route; block-from-chat writes every block list; one Send tap produces one message id.Hey-engine 2 commits on
field-invite-chatpub: leftover outbox remesh parked; a via-relay hop kept on the first missed stream ack; high-RTT relay video held to a talking-head bitrate; chat restored on Unblock.Hyper homepage 2 commits: a first static homepage pass, then a personal demo host removed from the docs. Do not treat that host as a public URL.
Still source / sideload. No store tag. No ElastOS capsule launch. Group chat on a fresh Runtime install is still not in a preview.
9. Elastos.org — Still the Rebuild Branch
One more commit on
website-rebuild-2026: stats alignment, a photo strip, and a noindex flag so the branch is not treated as the live site.maindid not move. Not a production flip.elacitylabs.com had no commits this window.
10. Essentials Overhaul — Still Local
In development. Not a store release.
This week consolidated an incoming working build into one candidate and checked it in the iOS Simulator. Edit Profile saves only on an explicit Save. Credential import, replacement, and sharing warn on duplicates. Published identity shows a review that says publication is public and permanent. Retries and cancellation stay tied to the profile that started them. Raw identity create, update, transfer, and deactivation get an exact-request review.
Signing requests show addresses, typed messages, token amounts, and approval permissions more clearly. Decline stays reachable on a long request. Unavailable fees and uncertain balances are named. Checks confirm the request, wallet, network, and reviewed payload still match before approval continues. Verification used safe test requests. No financial transaction was signed.
Also: document and credential writes that fail or come back uncertain; browser URL and late search results; Add Token when the wallet or network changes; BPoS node choices kept local until review; Hub still Elastos Main Chain only. Shared menus, sheets, and destructive actions moved forward. Light-theme type is easier to read. Warnings that used to sit too quietly are visible, including a warning when an ESC contract in a signing request is not a verified one. Session screens from the last system meeting are connected in the simulator. The full visual audit is not done. Real deletion of accounts and credentials was not broadly tested.
11. Elastos DAO — Local Participation, Not Public
In development and local verification. Not deployed.
The local stack is running again: PostgreSQL, backend, and the site, on the 410 retained legacy records. Accounts and protected sessions. Suggestion drafts, saved revisions, and explicit publication. Comments and replies on proposals and suggestions. Public profiles and private following. Those screens were exercised locally with a synthetic identity, not live Essentials sign-in.
Native governance moved on registration and voting history, withdrawal references, signature verification, transaction preparation, and council / proposal reads. That is not a claim that live voting or staking is safe to open. Live Essentials sign-in is still the replacement for the synthetic authority, and it is not in this build.
Comments, drafts, and the rest of participation stay in the DAO database. The identity chain is not being extended to store that discussion. The person still owns their identifier; the signature check stays with them. A visual pass on the DAO site is in progress on that local line and is not the live site. Small Explorer and RPC fixes continued. How mainchain and the sidechains should relate stays research. It is not a decision this week.
12. DAO ELA/ETH Pool — Test Position Only
Rebuild in progress. Not a request to send funds.
The inactive 2021 position was emptied. 16.97 ETH and 125,211 ELA returned to the DAO wallet, including about 17 ETH of uncollected fees. A new range of $0.20 to $1.00 was chosen. A 0.5 ETH test position is live and trading. Recorded cost of the test so far is about $10.
The rest of the liquidity has not been added. Adding it waits on an explicit DAO go-ahead for this range. The live test is not that go-ahead. There is no date on that step. A trade of about $1,000 is estimated to move the price by under 2% once the planned size is in. That estimate is not a promise, and the size is not in the pool today.
13. Elastos Ledger App — Review Branch, Not Submitted
Private review branch. Not released. Not submitted to Ledger.
Ledger asked for security and compliance changes before the next listing review. Two reviews were combined into one issue list. The choice is to patch the existing app so people who have it can update and Essentials compatibility stays. A replacement app would put the current listing at risk, so that stays later.
The review list is larger than the first patch set. Five items were called critical. The class that matters most: a transaction on the review screen has to be the transaction that is signed. Destination and amount have to be visible. Those checks are in the private branch, with clearer review screens, general hardening, and Ledger’s current build layout. The build reports zero compiler warnings and asks only for the minimum device permissions. Reported test runs passed. One Ledger-controlled database entry is still outside local sign-off. Cosmetic cleanup is not the priority while those checks are open.
Ledger no longer accepts Nano S app updates. The planned device set for a later build is Nano X and Nano S Plus. Touchscreen devices are a later discussion. Still ahead: remaining review items, the GitHub build, a physical device, and only then a submission. The patch is not submitted.
14. PC2 — Quiet by Design
pc2.net— zero commits after #38. Operator line remains v1.4.0.0.7.1 is still a Runtime-only line. PC2 waits until the protected-content surface on PR 62 is what the node consumes.
15. Release Engineering
main8ac18becfix/0.7.2-model-ci-node· not integrated16. Convergence Lens
17. Looking Ahead
main. The preview host stays unposted until the team says otherwise.18. Summary Statistics
Week of September 19 – September 26, 2026 (after #38). Counts are commits on the active branch in the window, not a claim each one is new product. Runtime SHAs were deduped across remotes (~220 unique). The 0.7.2 model branch and its CI pin overlap heavily, and many of those commits are evidence notes. The three PR 62 squashes restate #38.
mainunmovedfield-invite-chatpubwebsite-rebuild-2026)Runtime: Anders Alm — models, seed receipt scope, Browser close evidence · Irzhy Ranaivoarivony — protected content and offer buy · SashaMIT — wallpaper, Assistant mark, alignment, phone layout.
Marketplace: SashaMIT — ela.city, drm-api, events-watcher, v1-rest.
Also this week, not in those repos: Essentials consolidation, review flows, and an unverified-ESC-contract warning · DAO local accounts, comments, profiles, participation kept in the DAO database · ELA/ETH pool test position · Ledger patch branch. Anders’ team-sync note is on
docs/weekly-2026-09-25, outside the commit counts above.Releases. None tagged. Latest Runtime tag v0.7.0. PC2 v1.4.0. Marketplace 4.6.8 / 0.13.2. Essentials, DAO, and the Ledger app are not public releases.
19. Notes
Quick fact card
.ddrm· PR 62 openCadence: weekly updates. Previous report — Week of September 14 – September 18, 2026 (#38). This report — #39.
All reactions