Welcome to this week’s Behind the Code, your inside look into the engineering teams building the Elastos SmartWeb. This week, NBW delivered a major NBW 2.0 milestone: they launched the BTCD Order Monitoring Dashboard, enabling real-time lifecycle visibility across orders, protocol health, user trends, and automated alerting. In parallel, they completed end-to-end optimization + testing of the BPoS block production contract, upgraded governance UX with Ledger voting support in EE, and tightened automated risk controls by fixing an ECO-chain penalty gap and pushing a new production version.

This week, Elacity Labs and the World Computer Initiative (WCI) tightened the story from “many parts” into one coherent system: PC2 → Wasmer AppCapsules → dDRM markets. Phase 1 execution (wallet login + connect to your own PC2) is now the shared focus across Elacity × ElaHat; Phase 2 (Wasmer capsules) has crossed an integration threshold via MCP; and Phase 3 (dDRM markets) is now clearly framed as the economic extension that makes the whole system sustainable. The pieces are no longer theoretical — they’re starting to behave like a computer.

NBW Team Major Achievements This Week

1. BTCD Order Monitoring Dashboard Launched (NBW 2.0 Phase 1 Milestone)

• Real-time order lifecycle monitoring + full Create → Take → Stake → Mint → Repay → Close flow tracking.
• Exception alerting: overdue orders, issuer unlock anomalies, unclosed orders, dispute / liquidation monitoring.
• System health checks: de-peg alerts, TVL / supply monitoring, anomaly thresholds, risk-state visualization.
• Backend monitoring APIs delivered to power the dashboard with reliable real-time data.

2. BPoS Block Production Contract: Optimization + Testing Completed

• Unit tests + integration tests completed.
• Gas consumption optimized across core paths.
• Deployment scripts finalized + block listening functionality added for validator rotation logic.
• Blacklist automation (e.g., auto-blacklist after extended non-production) tested with new precompiled logic.

3. Governance UX Upgraded: Mainchain Voting Improvements

• EE Wallet added Ledger hardware wallet voting support.
• Fixed multi-signature wallet voting bugs and improved voting flow + status display.
• Memo voting testing support + end-to-end verification work.

4. Automated Ops + Risk Control Strengthened

• Fixed ECO chain penalty gap (some non-repayment flows not penalizing correctly) and released a new version.
• Resolved PGP mainnet proof-submission failure affecting BTC staking proof orders (critical user-path fix).

5. BTCD App Iterations Continued

• Prepared + verified BTCD app versions 1.0.16 and 1.0.17 with ongoing UX refinements.

BTCD Order Monitoring Dashboard

What was shipped

• Operational heartbeat: active orders, supply, TVL, staked distribution, mint-source breakdown.
• Conversion funnel: full lifecycle visibility from creation through closure, with bottleneck identification.
• Exceptions: overdue alerts, unlock anomalies, unclosed orders, proof-related anomalies.
• Dispute / enforcement: arbitration tracking, liquidation record visibility, suspicious activity stats.
• Health + risk: peg monitoring, anomaly thresholds, intervention triggers.
• Workflow visualization: state-machine style UX distinguishing user actions vs issuer operations vs system decisions.

Impact: This is the shift from “blind operations” to “data-driven operations” — knowing what is happening in real-time, surfacing problems early, and turning product optimization into an evidence-driven loop rather than guesswork.

BPoS Block Production Contract

What was completed

• Blacklist automation: auto-blacklisting nodes after extended non-production; statistics + verification via new precompiled logic.
• Block listening: height-triggered calls to identify current validator; validator rotation logic reviewed (current/next round switching).
• Testing: full unit + integration coverage completed for core module collaboration.
• Gas optimization: function-by-function gas review → reduced operational cost for large-scale scenarios.
• Deployment readiness: production-grade deployment scripts prepared; documentation + CR feedback loop initiated.

Impact: BPoS is moving from “contract development” into “deployment-grade infrastructure” — the practical foundation for ecosystem nodes to participate in block production with measurable performance and enforceable liveness guarantees.

Mainchain Voting Enhancements (EE Wallet)

What was fixed + added

• Ledger voting support for mainchain governance participation (security + usability win).
• Multi-sig voting bug fix: corrected execution edge cases and improved status display accuracy.
• Voting flow verification: local compilation, regression testing, and coordination across memo-voting-related checks.

Impact: Governance participation becomes more secure (hardware signing) and more reliable (multi-sig correctness), reducing friction for serious stakeholders.

Automated Operations & Risk Control

Automatic penalty mechanism

• Fixed ECO-chain cases where non-repayment penalty flows were not triggering correctly.
• Published a new version after root-cause analysis + targeted fixes + verification.

Impact: Strengthens protocol enforcement and removes silent failure modes in automated risk control.

PGP mainnet proof submission

• Resolved a mainnet contract issue preventing correct submission of BTC staking proof orders.
• Debugged and patched the root issue to restore smooth user operations.

Impact: Unblocks a critical path in the staking/mint lifecycle and reduces support burden.

BTCD Application Iterations

• Prepared and verified BTCD app 1.0.16.
• Completed pre-release checks for 1.0.17, followed up on PG release coordination, and closed tasks after regression testing.

NBW Conclusion

This week is a clear NBW 2.0 inflection point: the BTCD Order Monitoring Dashboard turns operations into an instrumented system with feedback loops, alerts, and decision-grade visibility — while the BPoS block production contract reached deployment-ready maturity through testing, gas optimization, and validator-rotation tooling. With Ledger voting support, penalty automation fixes, and critical proof-submission patches, NBW tightened the entire stack: observe → govern → enforce → operate.

Elastos World Computer Initiative (WCI) — Elacity Labs

Core Focus This Week — From “apps on a platform” to “self-owned computing”

This week consolidated several months of architectural work into a clearer, end-to-end pipeline: PC2 → Wasmer → dDRM. Phase 1 execution (PC2 connection) is now the shared delivery focus between Elacity and ElaHat; Phase 2 (Wasmer AppCapsules) crossed a key integration threshold via MCP; and Phase 3 (dDRM markets) is ready to attach as the economic extension to the capsule model. The system increasingly behaves like a personal computer for the decentralized web — not a bundle of dApps.

1) PuterOS on PC2 — Phase 1 Execution

Phase 1 goal

A user logs in with a wallet and connects directly to their own PC2 node, not a third-party cloud.

Phase 1 scope (active)

• PC2 installable on personal hardware or VPS.
• Wallet-based login (MetaMask / Essentials / Particle).
• First login binds wallet identity (EOA) to a specific PC2 node.
• Subsequent logins auto-connect to that personal cloud.
• All files + compute run on the user’s PC2.
• Single-process, single-port architecture (same-origin frontend + backend).

Deliverable definition: “I can log in and connect to my own PC2 instead of Puter’s cloud.”

2) MCP + Wasmer — AppCapsules Become Real

MCP status

• MCP (Message / Module Control Plane) refinement is basically complete.
• System-level functions are extracted behind MCP interfaces.
• MCP is now the gateway through which Wasmer applications access system resources.

Why this matters: MCP becomes the system call layer of the World Computer: apps do not talk directly to the internet or host OS; they talk to MCP, which enforces identity, permissions, and resource boundaries.

Wasmer integration

• Wasmer integration via MCP is complete.
• This establishes the runtime foundation for AppCapsules: applications that bring their own execution logic and control surface.

3) AppCapsules and RTOS — Explained Simply

What “RTOS inside a capsule” means here

• Each Wasmer capsule includes a tiny, purpose-built runtime layer.
• This runtime behaves like a minimal operating system: controls execution flow, validates access rights, manages interactions with MCP.
• The capsule does not depend on the host OS for trust or compatibility.

In simple terms: a capsule is closer to a self-contained device than a traditional app.

Capsule mental model

Instead of: Player app + OS + external rights check + external services
We move toward: one binary capsule containing:

• Application logic (player, agent, game, tool)
• Optional embedded asset or model
• Minimal runtime/OS layer
• Embedded rights-validation logic

This aligns with the working formula: Wasmer Capsule = Application × Asset × RTOS × Embedded Rights.

4) Phase Alignment Across Teams

• ElaHat team: finalizing MCP + Wasmer foundations, preparing enterprise-facing narratives and demos.
• Elacity team: executing Phase 1 (PC2 connection) while preparing downstream integration into dDRM markets.
• Joint focus: deliver a credible end-to-end demo showing wallet login → personal PC2 connection → launching a Wasmer capsule inside ElastOS.

5) Core Platform Engineering — Media, Workflows, and IPFS

Background processing & workflow optimization

• Event-driven workflow progression using message listeners.
• Upload/transcode phases stabilized with accurate progress tracking.
• Backend-driven job updates reduce frontend fragility.
• Memory leak fixes advanced across progress modals and providers.
• Workflow stages refactored away from heavy batch jobs toward faster Cloud Run-style steps.

IPFS optimization

• CID detection expanded across servers to identify unused data.
• Thousands of CIDs flagged for safe unpinning to reclaim space.
• Key structural challenge identified: ERC-1155-style metadata URIs are not fully represented in the database; onchain resolution failures complicate automated cleanup.

6) Current Challenges

• Eliminating remaining friction in progress modals during complex event sequences.
• Ensuring cache invalidation behaves correctly across resume and replay paths.
• Final reconciliation of multi-source state (frontend, database, workflows).
• IPFS cleanup complexity due to partial onchain metadata visibility.

What this week really represents

This week marks a transition from “shipping components” to assembling a new computing model:

• PC2 becomes the user’s machine.
• Wasmer capsules become the user’s software.
• MCP becomes the system boundary.
• Elacity dDRM becomes the economic layer that makes the whole system sustainable.

The pieces are no longer theoretical, they are starting to behave like a World Computer.