Welcome to this week’s Behind the Code, your inside look into the engineering teams building the Elastos SmartWeb. This week, NBW team reached a major milestone in BPoS block-production development: they completed core contract modules for Oracle registration, BPoS node registration, blacklist logic, and block-production statistics, bringing the PGBPoS contract to its preliminary completion. On the infrastructure side, NBW resolved critical ECO chain issues blocking proof submission and order closure after unlock, hardened contract event broadcasting security, and extended the monitoring stack with BSC multi-node failover and USDT-balance observability. Governance and UX also advanced: Memo voting indexer/API layer has been developed, BTCD Protocol gained better error messaging and statistics (including expired unpaid orders), and batch proof-submission scripts were upgraded to reduce manual ops.
On the World Computer front, Elacity Labs and ElaHat teams pushed the Wasmer + MCP architecture closer to user-owned personal clouds. MCP’s syscall surface was refined, the Wasmer runtime is now integrated into PuterOS via MCP, and the PC2 roadmap was structured into three phases: (1) decentralized login and PC2 connection via Particle/EOA binding, (2) Wasmer-based AppCapsules such as Elastos Chat running entirely on user hardware, and (3) a rights-aware dDRM market where capsules carry embedded licenses and revenue logic. In parallel, Elacity’s background processing, mint pipeline, and IPFS infrastructure were hardened, eliminating memory leaks, stabilizing async workflows, and moving toward fully resumable, backend-driven media workflows.
NBW Team Major Achievements This Week
1. BPoS Block Production Contract Nearing Completion
- Implemented Oracle registration and BPoS node registration in the block-production contract.
- Added blacklist and blacklist statistics modules for node risk management.
- Built block-production information tracking to measure node inactivity and support reward logic.
- Completed initial integration and testing of core PGBPoS contract functionality.
2. ECO Chain Stability Restored
- Fixed issues where, after BTC unlock on ECO, users could not submit proofs or close orders.
- Refined issuer auto-signing service and legacy data handling.
- Hardened contract event broadcasting against malicious or forged events.
3. Memo Voting Feature Implemented
Memo votings will be used for community related proposals that are difficult to reach consensus on. This feature will not be used for recent BPoS upgrade discussions within the community.
- Designed the Memo voting tech solution for EE Wallet.
- Developed a Memo voting indexer and deployed a dedicated API.
- Completed initial integration and functional verification.
4. Monitoring & Observability Upgraded
- Implemented BSC multi-node automatic switching for ERC20 USDT balance queries.
- Improved monitoring robustness by auto-failing over to backup nodes.
- Verified PGP degradation behaviour on testnet and tested BPoSPool performance boundaries.
5. UX & Automation Improvements Across BTCD & Ops
- Fixed multiple BTCD UI issues, improved error prompts, and added expired unpaid order statistics.
- Optimized automatic proof-submission scripts for batch and specific-order handling.
- Refined EE Wallet transaction-detail links and verified wallet stability.
BPoS Block Production & Governance Mechanics
Core Contract Functionality – What was completed
- Oracle registration logic added to the BPoS block-production contract.
- BPoS node registration implemented, allowing ecosystem nodes to opt in as block producers.
- Blacklist mechanism:
- Blacklist flagging for misbehaving or inactive nodes.
- Blacklist statistics for governance and risk analysis.
- Block-production statistics:
- Per-node tracking of how long they’ve gone without producing a block.
- Foundation for activity-based rewards and penalties.
- Initial full integration of core modules and internal contract tests.
Impact: The PGBPoS contract is now structurally capable of supporting decentralized block production and node governance on PGP Public Chain.
Performance & Security Auditing
- Stress-tested the BPoSPool contract with large numbers of nodes to identify performance boundaries.
- Continued security audit of the BPoS block-production contract:
- Module-level testing.
- Identification of potential attack surfaces and optimization points.
- Iterated on contract design after internal discussions to align with long-term governance needs.
ECO Chain Stability & Order Lifecycle Integrity
Order Unlock & Proof Submission Fixes
- Resolved the bug where, after BTC unlocking on ECO, users:
- Could not submit proofs.
- Could not properly close orders.
- Updated scripts and contracts tied to ECO’s order-unlock pipeline.
- Ensured the full order lifecycle – open → collateralize → unlock → proof → close – works reliably.
Issuer Auto-Signing & Legacy Data
- Investigated issuer auto-signing behaviour around historical/legacy orders.
- Adjusted logic to correctly handle legacy data and edge cases.
Contract Event Broadcasting Security
- Fixed vulnerabilities around event broadcasting that could have allowed malicious or misleading events.
- Strengthened validation and safety checks around event emission.
Memo Voting – Community Governance Feature Rollout
End-to-End Technical Implementation
- Designed full Memo voting support for EE Wallet:
- Voting data format and indexes.
- Interaction flows for governance actions.
- Built a Memo voting indexer to track on-chain voting activity.
- Implemented and deployed a dedicated Memo voting API for frontends.
- Ran functional verification to ensure data correctness and performance.
Impact: Community governance now has a new primitive that integrates cleanly with EE Wallet and backend infrastructure.
Monitoring, Observability & Multi-Node Fault Tolerance
BSC Multi-Node Switching & USDT Monitoring
- Extended monitoring scripts to query ERC20 USDT balances on BSC.
- Implemented multi-node automatic switching:
- Rotate between different BSC nodes/API providers.
- Automatically fall back on failure to avoid rate limits or outages.
- Resolved USDT-balance display issues for monitored addresses.
Deployment & Knowledge Transfer
- Coordinated deployment of:
- Monitoring scripts.
- Batch automatic proof-submission scripts.
- Specific-order proof handlers.
- Walked ops/dev team through:
- Monitoring metrics.
- Technical details of BTCD minting processes.
Impact: The monitoring system is now fault-tolerant, and the team’s understanding of metrics and flows is deeper, improving operational reaction time.
BTCD & EE Wallet UX/Dev Experience
BTCD Portal
- Fixed multiple UI display issues and layout inconsistencies.
- Improved error messaging when a user connects with the wrong wallet:
- BTCD claim page now shows clear diagnostics.
- Added expired unpaid orders to the order statistics view for better lifecycle visibility.
- Locally validated ECO-chain BTCD changes and fed new issues into the backlog.
Elastos Essentials Wallet
- Fixed incorrect cross-chain transaction links in the transaction-details page.
- Improved readability and accuracy of transaction-record views.
- Locally verified modifications and continuously reported issues as discovered.
Automation & Proof-Submission Pipeline
- Optimized batch automatic proof-submission scripts for large-order sets.
- Added specific-order proof-submission capabilities for special-case handling.
- Coordinated deployment with ops to ensure smooth rollout.
NBW Conclusion
NBW’s work this week pushes NBW 2.0 further along two main axes: governance readiness and operational autonomy. BPoS contracts now have real structure and stats for node governance; ECO chain’s order lifecycle is reliable again; Memo voting introduces a fresh on-chain governance tool; monitoring is resilient thanks to multi-node BSC querying; and BTCD/EE Wallet UX continues to tighten. Automated proof-submission now offloads more manual work from operators, moving NBW closer to a self-running BTCFi infrastructure that can scale safely.
Elastos World Computer Initiative (WCI)
World Computer Progress: Wasmer Integration, MCP Finalisation & PC2 Login Architecture
This week, Elahat and Elacity advanced the core World Computer substrate on four fronts: MCP refinement, Wasmer-PuterOS integration, PC2 login design, and Elacity’s background processing stack. Together, these steps move the system from concept toward a demo-ready, user-owned compute environment.
MCP Mechanism & Wasmer Runtime Inside PuterOS
MCP Refinement Completed
- MCP (Message Control Protocol) now cleanly exposes all system-level functions required by Wasmer-executed AppCapsules.
- Interfaces cover storage, networking, identity, environment variables, and future extension access.
- MCP acts as the secure syscall surface for WebAssembly apps inside PC2.
Wasmer Integrated via MCP
- Wasmer is now embedded into PuterOS as the execution engine for AppCapsules.
- AppCapsules run as standalone, sandboxed digital executables with their own micro-OS.
- Execution becomes deterministic, auditable, and bound to user-owned hardware (PC2).
Impact: This completes the runtime glue necessary for Phase 2 of the PC2 roadmap – capsules running locally as first-class system processes.
PC2 Roadmap: Phases 1-3 (Elacity × Elahat)
Phase 1 — PC2 Connection & Decentralized Login (current focus)
- Goal: “I can log in using my wallet and connect to my own PC2 instead of Puter’s shared cloud.”
- PC2 software runs on personal hardware or VPS.
- Particle login integrated by Elacity as a Puter extension:
- Wallet-based login (MetaMask / Essentials / Particle).
- EOA is bound to a specific PC2 node on first login.
- Subsequent logins automatically reconnect to that PC2.
- All storage and compute for that user (uploads, transcoding, AI, chat, capsules) executes on their PC2.
Phase 2 — Wasmer Application Layer (“AppCapsules”)
- First Wasmer application: Elastos Chat, a peer-to-peer chat capsule.
- Capsules run entirely in PC2, with no central server controlling execution.
- Two users can launch Chat capsules and communicate cloud-to-cloud, device-to-device.
- All PC2 “apps” become capsules: media players, AI agents, utilities, automation tools.
Phase 3 — dDRM Capsule Market (future milestone)
- Rights and access encoded in tokens:
- ERC-721 = copyright token.
- ERC-1155 = access, distribution, royalty shares.
- Capsules embed:
- Encrypted content.
- License rules.
- Autonomous revenue logic.
- Elacity provides the market where capsules are bought, sold, and licensed.
Impact: The World Computer becomes directly monetizable for creators and developers – not just an infra layer.
MCP, Marketplace, and Internal Release
- All system capabilities needed by Wasmer apps now have secure MCP interfaces.
- “Get Started” flow is being updated so users can choose capsules during onboarding.
- Apps in the Puter marketplace are being decomposed into , aligned with the capsule model.
- An internal release is scheduled for:
- Decentralized login extension demos.
- IPFS integration via extensions.
- End-to-end PC2 connection & capsule initialization flow.
Elacity Engineering: Background Processing, Mint Pipeline & IPFS
Background Workflow & Mint Pipeline
- Backend event handlers now autonomously update job progress (no more frontend polling).
- Mint workflows are migrating to a fully async pipeline:
- Upload → transcode → encode → mint → verify.
- Resumable after refresh or disconnect.
- Driven by backend events (e.g., listener).
- State management was cleaned up to reduce re-renders and keep Redux / Firestore / DB in sync.
Upload, Transcoding & Workflow Speed
- XHR uploads detached from form state for clearer tracking and reduced coupling.
- Google Cloud workflows reviewed jointly with WAU to speed up transcode/encode stages.
- Alternatives to GCP Batch are being evaluated, especially for smaller (150 MB) media.
IPFS & Infra
- IPFS/NFS node upgraded (4 vCPU / 8 GB RAM).
- CID detection across servers ~70% complete, improving redundancy and retrieval.
- Free-space optimization and caching-behaviour analysis underway.
Memory Leaks & Media Viewer Stability
- A key memory leak in the workflow modal was:
- Identified, reproduced, and mitigated via new state patterns.
- Auto-close behaviour for publish modals now works consistently.
- The media player now:
- Autoplays where appropriate.
- Preloads licenses.
- Handles scaling and cache invalidation cleanly.
Summary: Convergence Toward a User-Owned World Computer
- MCP + Wasmer + PuterOS now form a coherent execution stack for AppCapsules.
- PC2 login and wallet-bound identity are being wired into Particle and extension-based flows.
- Elacity’s mint and media pipelines are transitioning to fully resumable, backend-driven workflows.
- IPFS and infra upgrades support the storage and playback requirements of capsule-based media.
