Welcome to this week’s Elastos SmartWeb weekly update, your inside look into the engineering teams building the Elastos SmartWeb. This week, the NBW team initiated early exploration of BTCD 2.0, focusing on workflow redesign, issuer/keeper logic optimization, and script feasibility. BTCD development will be moved from the testing stage to the user acquisition stage. While for extending Elastos BPoS staking system to EVM chains like PG Chain, the focus is on BPoS block production contract refinements, expanded monitoring backend APIs, and continued Elastos Essentials super-wallet cross chain + governance improvements. The theme is clear: instrumentation and governance maturity on the outside, while the protocol’s economic model and trust surface are being redesigned for whale-grade requirements.

This week also marked a convergence week across Elacity Labs and the World Computer Initiative (WCI). The architecture is no longer just explained, it is being demonstrated. Personal cloud ownership, WASM execution inside user owned compute, and the near term path to cloud to cloud communication are now in active motion, while Elacity continues stabilizing the minting, playback, and background job pipeline to make the system feel reliable and “local.”

NBW Team Major Achievements This Week

BTCD 2.0 Exploration

BTCD has completed its first phase, with the BTC collateralized stablecoin issuance system built and validated, and is now entering a new phase focused on product refinement and user growth. After speaking with potential whale users, the NBW team identified gaps in the current BTCD protocol around the economic model and trust design. BTCD 2.0 aims to adjust these key parts so the system can support large scale users while keeping its core identity as a BTC backed stablecoin.

This week’s BTCD 2.0 work mainly focused on three things.

• Sketching the overall BTCD 2.0 workflow, discussing how the Issuer and Keeper logic should work in practice and beginning to clean up and formalize the related technical documentation.

• Exploring possible script designs, going over the early pros and cons of different technical paths and shortlisting which options are worth deeper research next.

• Discussions of adding an API to show monthly BTCD minting cost statistics and started the technical preparation for it, so users can later rely on real cost data instead of guessing.

Strategically, BTCD 2.0 marks the shift from a first working product toward a mature commercial product. By addressing the core weak points in the economic model and trust mechanisms, the project aims to bring in more whale users and build the base for ecosystem scale growth. This work is still in an early exploration phase, and the next steps will focus on deeper scheme design and technical validation.

Elastos BPoS staking system relay to EVM chains

As part of a strategic decision by the NBW team, PG Chain, which is currently operated only by Elastos DAO council nodes, will be extended to the wider Elastos BPoS validator node system. Development work has started, and the BPoS block production contract is now in progress. This week:

What was improved

• Integrated BEP-131 style block production logic to improve performance, security and BPoS node participation on PG Chain

• Updated the blacklist so inactive nodes are paused for one week, improving stability while keeping participation fair

• Added per epoch block production stats to give a more accurate basis for reward distribution

• Tested the random node selection logic for fairness so all eligible nodes have an equal chance

• Chose a “from top 25 choose 20 randomly” node selection model and shared it with the Elastos DAO council group for discussion and feedback

Impact: The contract is converging on “governance-grade” correctness: measurable liveness, bounded punishments, and selection fairness that can survive community scrutiny.

BTCD Monitoring Backend APIs

What shipped

• Dashboard statistics endpoints (operational summary data for observability UX).
• BTCD Minting source analysis endpoints (multi-dimensional attribution for where minting originates).
• Trend endpoints: staking trends and BTCD minting trends for time-series analysis.
• System health endpoints plus abnormal-order and anomaly coverage expansions.
• Timestamp + historical stats support across key datasets (orders, minting, staking, key assets).

Elastos Essentials improvements + Mainchain Memo Voting 

Wallet cross-chain UX

• Implemented display of mainchain deposit transactions within sidechain transaction records.
• Continued local compilation, regression testing, and issue submission for newly discovered wallet bugs.

Community Memo Voting system improvements (Not yet released)

• Fixed expired vote deduction logic in memo voting indexer (correctness + fairness).
• Improved poll list sorting rules
• Organized full test cases for mainchain polls and continued verification support.

NBW Conclusion

This week marks an explicit transition: BTCD is no longer being treated as “the product we launched,” but as “the product we must mature.” BTCD 2.0 exploration began to address whale-grade requirements around economic transparency and trust mechanics, while the supporting rails kept improving: a more governance-ready BPoS contract (BEP-131 refinements, bounded blacklist validity, fairness testing), deeper observability via monitoring APIs with timestamps and trend coverage, and a tighter governance + wallet experience through voting correctness fixes and cross-chain transaction visibility.

Elastos World Computer Initiative (WCI) — Elacity Labs

This week marked a strategic convergence between vision and execution across Elacity and the ElaHat team. While core engineering continued hardening minting, playback, and background-job recovery, a systems-level alignment took place around World Computer architecture, personal cloud ownership, and WASM-based application execution. The focus shifted from “explaining the model” to “demonstrating the model.”

1) World Computer & Personal Cloud Architecture

Strategic alignment + demonstration

• Deep architectural walkthrough presented to the Cyber Republic Council, clarifying end-to-end system direction.
• Reinforced the core thesis: personal cloud nodes replace centralized servers; wallet-based identity replaces platform accounts.
• Users directly control identity, data, storage, compute, and tokenized value.

Economic model (asset-based income)

• Digital capsules (apps, agents, data, media) become tokenized assets.
• Execution rights are purchased, and revenue distributes automatically to creators and contributors.
• Designed as infrastructure for a shift from wage-based labor to asset-based income under automation.

Roadmap targets for January

• Personal cloud login
• Home screen UI
• File system visibility
• Icon-based WASM execution
• Decentralized analytics tools
• AI agent integration
• Advanced peer-to-peer communication

2) ElaHat Update — WASM Chat & Enterprise Applications

WASM Chat application

• Peer-to-peer chat built to run as a deployable WASM module inside personal cloud nodes.
• Real-time bilingual collaboration (Chinese → English and English → Chinese translation flow).
• Chat instances are owned by the group creator and can be named/branded by the user.
• Core shift: “messaging app ownership” moves from platform-held to user-held infrastructure.

App Store direction + enterprise validation

• Planned local WASM utilities (calculator, notes, calendar) as a starter set.
• Enterprise “cloud boxes” positioning: businesses host their software and data inside the World Computer instead of renting traditional cloud stacks.
• Prototype enterprise demo (“Cow Farm”) validated operational workflows (inventory, CRM, analytics, reporting).

3) Media Pipeline & Platform Stability

Recent achievements

• ProgressModal memory leak fix completed with full frontend review.
• Logging, monitoring, and error handling hardened.
• Redux selector + state management issues cleaned across explore, media, and mint flows.
• Artifacts after mint completion cleaned up for more reliable UI state.
• Network auto-switching enforced for wallet connections.

Ongoing work

• Resume failed/stale background jobs (recovery-first reliability).
• Improve playback session smoothness and consistency.
• Finalize progress modal behavior under complex mint sequences.
• Review/refine scheduled RLI cron jobs.
• Continue mobile UX polishing.

Current challenges

• Coinbase wallet integration blocked by Cross-Origin Opener Policy conflicts.
• Inconsistent behavior during enforced network switching requires further desktop debugging.

4) Near-Term Milestones

Over the coming weeks, the combined teams are targeting:

• Integration of ElaHat’s WASM Chat into the World Computer environment.
• Demonstration of cloud-to-cloud communication.
• DRM-controlled WASM application execution.
• Drag-and-drop asset upload, encryption, and tokenization.
• Marketplace expansion with resale and royalty support.

A first end-to-end demo showing personal clouds communicating, running WASM applications, and enforcing digital rights is targeted within the next month.

Closing Note

This week reinforced that Elacity and ElaHat are aligned on first principles:

• Users own their infrastructure.
• Applications are sovereign digital capsules.
• Rights are enforced at execution, not by platforms.
• Economic value flows automatically to creators.

Despite market conditions, the system is converging toward a post-platform computing model where identity, storage, compute, and rights move with the code.