This article covers the Elastos World Computer Initiative (WCI) and Elacity Labs. The WCI team is building the execution, identity, and compute substrate for user-owned personal clouds (PC2), while Elacity applies that substrate to real markets for media, software, AI, and digital rights.
This week marks a transition from architectural promise to operational reality: WASM binaries now execute on user-owned hardware, AI runs locally with real filesystem access, and marketplace reliability was materially strengthened across playback, royalties, and background workflows. Elacity Founder and CEO Sasha Mitchell breaks down progress to date in this video:
1. World Computer (PC2): WASM execution is live
- PC2 now executes WebAssembly binaries on user hardware, not in the browser.
- Wallet-scoped binary storage ensures strict user isolation.
- Automatic detection of WASI vs non-WASI modules implemented.
- Memory and process sandboxing enforced at runtime.
Proof, not theory: a WASM-compiled calculator now runs as a native-feeling app inside PC2, with all computation happening locally on the user’s node.
2. WASI progress unlocks real applications
- WASI runtime support added.
- In-memory filesystem (MemFS) operational.
- File-I/O mapping to the host filesystem identified as the next step.
What this enables next: file processors, media tools, agent binaries, and enterprise utilities running inside personal clouds.
3. AI inside PC2: production-ready and sovereign
- Multi-provider AI support (local + cloud).
- Streaming responses with real tool execution.
- Full filesystem read/write access.
- App-exposed tools via IPC.
- Image and document inputs supported.
Critical security fix completed: AI memory, chat history, tools, and configuration are now strictly wallet-scoped. One user’s assistant cannot see or leak another user’s data — verified end-to-end.
4. Elacity protocol & marketplace hardening
- Smoother playback session handling.
- Fixed receipt edge cases interrupting playback.
- Improved thumbnail reliability in background lists.
- Mint form state increasingly consistent when restored from background jobs.
5. Smart contracts & royalty flows stabilized
- Contract testing environment restored and hardened.
- Upgrade deployed enabling free transfer of royalty tokens.
- Frontend support completed for:
- Royalty balances
- Governance views
- Revenue tracking
- Transfers on deprecated contracts explicitly blocked.
- Subscription UI state desynchronization fixed.
Impact: rights move correctly, revenue attribution remains accurate, and legacy contract state cannot contaminate current markets.
6. Background jobs, progress & load management
- Advanced resumable mint workflows.
- Identified and reduced heavy load from progress modal rendering.
- Improved recovery for stalled or interrupted background jobs.
- Began fixing listing correctness under direct token transfers.
Why this week matters
This week closed a critical gap between architecture and reality:
- AI now acts locally, privately, and usefully.
- WASM proves computation can be owned, not rented.
- Market and protocol layers are being hardened for real economic activity.
Without reliable playback, royalty movement, resumable workflows, and UI–contract alignment, sovereign architecture collapses under real use. That risk was materially reduced this week.
Outlook
What is now true:
- Executable software runs on hardware users own.
- AI operates with real tools without leaking data.
- Rights and revenue move more reliably.
- Background processes survive interruption.
What comes next:
- More WASM applications.
- File-based WASI tooling.
- Capsule packaging with embedded rights.
- Agent-driven execution flows.
- Composable, market-level primitives.
