The last eight weeks changed where ElastOS is being built.
Elastos Runtime v0.7.0 was released on September 1 as the foundation for the upcoming ElastOS v2. Runtime is now the base for protected content, local AI, collaboration, wallet authority, Carrier transport, and the Home desktop.
New product work is moving from PC2 into Runtime rather than continuing across two separate product lines. PC2 remains available for current users and node operators, while the desktop, Wallet, Carrier, recovery tools, and capsule system are now being built together inside Runtime.
Protected content now covers documents, images, books, comics, archives, 3D models, audio, and video. Marketplace installed the first local AI model onto a fresh machine. A Linux Runtime also used a model hosted by a trusted Mac, with the Mac owner approving the request through Inbox.
During the same period, the main chain recovered, ESC and EID reopened, and Halborn began its independent review of the next main-chain release. Separate security notices covered those events. This article focuses on the product work that continued around them.
In one breath:
- Runtime v0.7.0 shipped as the foundation for ElastOS v2.
- Protected content expanded beyond video to nearly every major file type.
- Users can now install local AI models from Marketplace.
- PC2’s main product functions are moving into Runtime.
- ESC and EID resumed, while Halborn began its main-chain code review.
- Elacity Marketplace reached version 4.6.8, with faster browsing and background uploads.
- Hyper gained a desktop client and one shared Rust engine.
- New versions of Essentials, the DAO portal, and Elastos.org remain under development.
1. Runtime becomes the centre of ElastOS
Runtime v0.7.0 and app permissions
Runtime v0.7.0 brings several months of work into one release, including the AI agent mandates covered in the July update.
The main change is how apps receive authority.
Apps no longer choose which identity they use or reach directly into system services. Runtime determines the active identity, checks each request, records sensitive decisions, and sends approved work to the correct service.
Wallet keeps the keys and handles signing. Apps never receive the keys.
First-party apps are moving to one capsule format and one permission model. This gives every app the same basic rules for asking to use files, Wallet, networking, AI models, and other parts of the system.
Protected content and collaboration
Runtime v0.7.0 connects protected content to the blockchain and Runtime Library.
Each protected listing links to an on-chain record and a content fingerprint. A buyer can import a listing created on another Runtime, verify it, purchase it, and open the same item through the rights record attached to it.
Testing covered the full process across two separate Runtime machines. Before purchase, the second machine refused access. After purchase, it could open, read, and close the content. The content key remained under 2-of-3 custody throughout the test.
During the same period, the team fixed eight security findings in the distributed key system.
Two marketplace issues were fixed as well. One involved a trade approval that could succeed under the wrong conditions. The other involved confusion over ownership during a legacy repurchase.
Collaboration arrived beside protected content. Profiles carry DID identities, Runtime signs updates between machines, and messages can arrive even when no browser tab is open.
Removing a contact requires approval from both sides. Direct conversations remain text-only by design.
Home, Assistant, and Browser
Home gained a system bar, per-app menus, system-wide search, virtual desktops, an overview screen, and quick file previews.
Users can run it as either a graphical desktop or a command-line shell. Both use the same apps, data, identity, and permissions underneath.
People is now its own app rather than part of Home. Sign-in has a dedicated lock screen with the ElastOS wordmark and a large clock.
The team rebuilt the Assistant with separate Chat and Build modes.
Chat handles normal conversations. Build can start Studio jobs from clear offers and instructions. The Assistant safely displays markdown and mathematics and keeps its state after Runtime restarts.
Old AI provider routes were removed. Credentials for outside AI providers do not pass through Home or Runtime’s saved state.
Browser runs inside a contained virtual machine with networking controlled by Runtime. Websites can detect the ElastOS Wallet, but account access, signatures, and transactions still return to Wallet for approval.
For now, Browser remains a preview. Login retention, restart reliability, speed, and recovery still need more work.
Any-file protection
Not yet public, the next Runtime release expands protected content well beyond video.
Documents, images, books, comics, archives, fonts, datasets, 3D models, audio, and video can all use the same rights and custody system.
Each protected file carries a record inside its media container. That record identifies the authority, key, token, and ledger connected to the content, but does not include the content key itself.
A machine can now serve only as a custody node. It can hold encrypted files and policy records without installing a viewer. It uses standard IPFS and keeps a limited number of replicas across trusted peers.
Testing showed that the custody system remained available when parts of the network temporarily lost contact with one another.
External wallets now work with the minting process. Once a mint confirms, the item appears in Library. A new Creator app gives creators one Runtime-owned screen for minting and selling their work.
Runtime now uses one protected-content authority rather than keeping the old and new systems active together.
Local AI and agents
Users can now install local AI models from Marketplace.
Its signed catalogue currently lists SmolLM2-135M-Instruct and Qwen.
On a fresh Apple silicon Mac, the team found a model in Marketplace, approved it, installed it, and used it through Assistant. After reloading Home and restarting Runtime, the model remained available without another download.
Remote model use works too.
A Linux Runtime requested a Qwen response from a trusted Mac. The Mac stored and ran the model, while Linux kept the conversation. The Mac owner reviewed and approved the request through Inbox.
Home now has a dedicated place for agents. The Shelf acts as a composer, and sending a request opens Agent Space.
Agents run inside their own capsules rather than inside Home. They must ask Runtime for model access and other permissions in the same way as any other app.
First setup and release testing
A fresh installation opens to an empty desktop with Marketplace pinned. The user chooses which apps to add rather than receiving a desktop filled with unwanted software.
Recovery Kit now comes before passkey creation, so every new identity begins with a recovery method already in place.
A one-command installer will come with the next release and open Home when setup finishes.
Installations and updates verify each downloaded release before replacing an existing version.
Publication will wait until five complete user journeys work on the same tested build:
- Installation and first setup
- Updating from v0.7.0
- Local AI
- Browser
- Protected video
PC2 and the World Computer structure
New product work has moved from PC2 into Runtime.
PC2 proved the personal-cloud model, multi-architecture app packaging, background services, Node Manager, the dApp Centre, operator workflows, and the idea of a capsule as an app.
Those product patterns now sit inside Runtime. Rust services, WebAssembly capsules, Home, Carrier, Wallet, recovery, and app permissions are being built as one system.
The aim is a native ElastOS stack that does not remain dependent on outside desktop or cloud frameworks.
PC2 is not being abandoned. Current users and operators will continue receiving fixes where needed. Its longer-term product functions are moving into Runtime rather than being built twice.
The structure is now clearer:
- Runtime runs capsules and controls what each one may do.
- Home is the user desktop, available as a graphical or command-line interface.
- Carrier carries private, signed communication between Runtime machines.
- Blockchain handles rights, settlement, consensus, and DAO activity, secured through Bitcoin merge mining.
Runtime now contains PC2’s main product patterns and Carrier communication. Wallet and blockchain capsules connect Runtime to the Elastos chain.
The blockchain remains separate, with its own releases, security work, and audits.
A capsule asks Runtime for a specific permission. It never receives a key, socket, file, or service that the user did not approve.
An agent can suggest an action, but it cannot approve its own request. Installs, protected-content releases, and other sensitive actions create receipts that another person can verify.
The next Runtime release begins bringing these pieces together as one user-facing ElastOS system.
2. Main chain recovery, sidechains, and audit
Main chain recovery and Halborn review
Since July 31, the Elastos main chain has produced blocks through BPoS.
Recovery returned the chain to block 2,260,450, the final unaffected block. Proof of work restarted at 2,260,451, and BPoS resumed at 2,261,186 under ELA v1.0.2.
ELA v1.0.2 included 87 correctness and security fixes. A read-only scan across the restart range found no violations, and balances confirmed before the incident remained unchanged.
By September 18, the chain had passed block 2,297,000.
Halborn began an independent Secure Code Review of the pending main-chain release, v1.0.3, on August 28. Its report is expected in early October.
The review covers:
- Post-incident main-chain hardening
- Consensus and Bitcoin merge mining
- Chain reorganisations and changes between consensus modes
- P2P and RPC resilience
Sidechains and cross-chain status
ESC and EID resumed on September 1.
Although the July 20 incident affected the main chain, it did not compromise either sidechain. Operators paused both while the main chain recovered and the team reviewed the full sidechain stack.
That review covered ESC, EID, the Arbiter, the oracles, and the software that reads main-chain data. It produced more than 200 corrections, all of which are now active.
Transfers between the main chain and ESC or EID are open. Each deposit is checked against its main-chain record before the sidechain credits it.
Around 6.03 million ELA created on ESC during the July 13 incident has been fully accounted for through burns and recovered backing.
A separate 1,585,252 ELA remains frozen on the main chain. A forthcoming release will credit it to the ESC reserve, and the transaction will be published on-chain.
PG continues to operate for activity that stays on PG, but cross-chain ELA transfers involving it remain disabled.
A separate team outside the Elastos DAO and Elacity Labs maintains PG. Its cross-chain service will remain closed until that team completes its own audit.
Node operators should use Elastos.Node v1.2.4. ELA v1.0.2 remains the current main-chain version until the formal release of v1.0.3.
Automated monitoring now scans Elastos repositories for known bug patterns and sends possible findings for human review.
3. Elacity Marketplace: versions 4.4.0 to 4.6.8
Elacity Marketplace moved from version 4.4.0 to 4.6.8. Its API moved from 0.11 to 0.13.2.
Most of the work reduced the cost and delay of browsing.
Home and Explore no longer query the blockchain separately for every listing. Grids use saved prices and smaller records. Poster images come from token artwork rather than loading the full media file.
Transactions now use atomic batches with a simulation before submission. After a write, the page refreshes instead of showing old data.
Uploads now run as background jobs.
Creators see a job card with live checkpoints and a time estimate based on the current transfer rate. If the backend stops reporting progress, the card turns amber and offers a Retry button.
Cloud encoding now processes multiple renditions at the same time rather than one after another. Small-file uploads dropped from six sequential job starts to three, and the team removed a 90-second startup delay from each encoding branch.
Its API now uses 24-hour session tokens instead of 14-day tokens. It has rate limits, query-depth limits, grouped listing and offer events, and build rules that prevent payable server actions from appearing without permission.
ESC now uses the faster event indexer first built for Base.
4. Hyper gains a desktop client
Hyper now uses one shared Rust engine across Android, desktop, WebAssembly, and future clients.
Android uses a user interface built on top of that shared engine. A desktop client now sits beside it, with Mac packaging and automated testing for both.
Current Android tests pass. Desktop testing remains underway, so that client is not ready for release.
Hyper received a security pass as part of the same work.
The pass removes location and EXIF data from sent media, redacts DIDs from logs, limits incoming message sizes, and uses rotating per-contact tokens for nearby discovery instead of one permanent identifier.
Hyper now creates a local post-quantum identity key, though more work remains before that key protects every communication feature.
Direct messages are sealed. Deleted media cannot return after a restart. Group calls use a video grid. Workspaces remain separate from private groups. Hide-IP contacts stay on relays after a restart. Delivered indicators appear only after the recipient receives the message.
Hyper remains available through sideloading. There is no app-store release yet.
5. Essentials, the DAO portal, and Elastos.org
Three large rebuilds are underway. None of the new versions is public yet.
Elastos Essentials
Essentials continues in private testing.
A security review found no remote code-execution issue, though previously known findings remain open.
Several previously broken flows now work:
- Adding a widget
- Finishing a second profile
- Creating a developer app
- Staking before wallet setup is complete
Inside the app, the browser no longer reveals a wallet address until the user connects. One website cannot read another website’s connected address. Three separate review rounds tested this behaviour.
An independent custody review must still take place before any production release.
Elastos DAO portal
Work on the DAO portal continues ahead of broader governance participation.
It now reads 410 retained proposals, including original Chinese text. Council, suggestion, proposal, and home pages are working internally, with complete light and dark themes.
Migration from the old DAO systems remains underway, so the new portal is not public yet.
Elastos.org, currently live on Elastos.com
The Elastos.org rebuild covers the homepage, Build, About, live Bitcoin hashrate history, a new DAO Council graphic, and mobile fixes across the main pages.
Its new version is not public yet.
Broader Elastos Ecosystem work
Meanwhile, the Main Chain Explorer received fixes for reorganisation history, election counts, address direction, and exports.
Research confirmed that ELA held on Ethereum could move directly to the Elastos main chain without passing through ESC.
Researchers documented the route, custody, and signer requirements. The team has not built the transfer system or moved any funds.
What comes next
- Repeat the remote Qwen test on the next Runtime release.
- Complete the full mint-to-play process for protected content.
- Continue work on Browser reliability, login retention, and recovery.
- Release Runtime 0.7.1 only after installation, updates, local AI, Browser, and protected video all pass on the same tested build.
- Publish Halborn’s main-chain v1.0.3 report, expected in early October.
- Continue Marketplace 4.6.8 testing and verify the new encoding changes.
- Keep Essentials, the DAO portal, and Elastos.org private until their testing and reviews are complete.
- Keep PG cross-chain transfers closed until its development team completes an audit.
ESC and EID are open, an outside auditor is reviewing the main-chain code, and Runtime has protected its first non-video files and installed its first AI model from Marketplace onto a fresh machine.
Together, the blockchain, Runtime, personal cloud, and Carrier are beginning to operate as one ElastOS system rather than separate projects moving beside one another.
The pc2.net discussions contain the full technical reports, covering reports #31 through #38. Runtime release: v0.7.0.
