Welcome to this week’s Behind the Code, your inside look into the engineering teams building the Elastos SmartWeb. This week, NBW pushed NBW 2.0 progress further into reality: they completed the detailed design of the BPoS block-production solution, began refactoring and implementing the PGBPoS block-production contract, stress-tested degradation and recovery behaviours across test networks, and shipped Elastos Essentials Wallet v3.2.11 with fixes for multi-wallet sidechain deposits and full-amount mainchain withdrawals. On the product side, BTCD’s estimation and statistics views were tightened, while new batch tooling and automation lifted the operational ceiling for PGP ecosystem events.
On the World Computer front, the Elacity / Elahat / WCI teams continued converging around the Wasmer + MCP execution stack and refined how AppCapsules, WebSpaces, ElastOS, and blockchain smart contracts fit into Rong Chen’s third-generation component philosophy. While NBW scaled consensus and wallet reliability, the World Computer work sharpened the architecture for AppCapsules running on WebAssembly “bare metal,” DIDs as substrate for WebSpaces and PC2, and ElastOS as the invisible coordination layer that removes the traditional internet attack surface.
NBW Team Major Achievements This Week
1. BPoS Block Production Solution Designed & Implemented in Contracts
- Completed comprehensive technical solution for BPoS participation in PGP block production.
- Refactored block-production contract architecture and implemented core logic for node registration and selection.
- Established a full contract testing framework for PGBPoS.
2. Consensus Degradation & Recovery Validated
- Systematic testnet validation of degradation → recovery flows under extreme conditions.
- Automated stress-testing with random node stop/start every five minutes.
- Located and fixed DAO node forking issues via targeted code updates.
3. EE Wallet 3.2.11 Released
- Fixed multi-wallet sidechain deposit failures.
- Resolved full-amount mainchain withdrawal failures for ELA between PGA chain and Main chain.
- Completed cross-platform checks and submitted to app stores.
4. BTCD UX & Tooling Improvements
- Corrected BTCD quantity estimation for mintable amounts.
- Optimized order statistics page readability and accuracy.
- Developed batch asset-query and batch-transfer tools for PGA, NFTs, and EVM addresses.
5. PGP Chain Ecosystem Activity Spike
- Third party PGA.fun (pump.fun-like launchpad) Meme-token events drove a surge in transactions and activity.
- Batch tools and gas-optimization scripts ensured smooth, low-cost operations.
- Strengthened the PGP chain’s position as an active, experiment-friendly ecosystem.
BPoS Block Production & Consensus Reliability
Block Production Solution & Contract Work – What was completed
- Multiple deep-dive discussions converged on the final BPoS-for-PGP block production design.
- Defined node-selection algorithms for who produces blocks and how rewards are distributed.
- Implemented the core PGBPoS block production contract with:
- Node registration and participation logic.
- Selection mechanism wiring for future BPoS nodes.
- Set up a complete test-case framework and testing plan for the block-production contract.
Impact: This is the structural base for decentralized governance and node participation on PGP, turning BPoS into a first-class actor in consensus.
Degradation & Recovery Testing
- Ran systematic tests of chain degradation and recovery on testnet.
- Exercised extreme scenarios to validate behaviour under stress.
- Developed scripts to randomly stop/start nodes every 5 minutes for automated stress tests.
- Performed boundary testing of degradation/recovery in a private-chain environment with different node mixes.
- Helped locate CR and fixed-node forking issues, then patched and validated them.
Impact: PGP now has a more thoroughly tested safety net for consensus faults and partial failures.
PGP Chain Ecosystem Building
PGA.fun Meme Launch Events
- PGA.fun, a third-party pump.fun-style launchpad on PGP, hosted Meme launches that:
- Drove a visible spike in transaction volume and chain activity.
- Attracted new users and liquidity into the ecosystem.
- Validated PGP as a high-throughput, event-ready chain.
Batch Tooling & Gas Optimisation
- Implemented batch asset-management tools for:
- NFTs, PGA, and other token types.
- Batch PGA transfers and EVM address/private-key generation.
- Added PGA batch-transfer gas-fee scripts to reduce participation costs.
- Built asset-query tools to simplify on-chain management during events.
Elastos Essentials Wallet 3.2.11 & BTCD UX Improvements
EE Wallet 3.2.11
- Fixed multi-wallet sidechain deposit failures to restore reliability for advanced users.
- Resolved failures when selecting “full amount” withdrawals on the ELA mainchain.
- Ran cross-platform checks (iOS / Android), recorded outcomes, and submitted to app stores.
- Re-verified previously fixed issues to guard against regressions.
BTCD Application
- Corrected BTCD mintable-amount estimation so users get accurate BTC→BTCD projections.
- Improved the order statistics page for clarity and readability.
- Locally compiled and tested BTCD DApp, reporting and validating issues in a tight loop.
Automation & Operations Tools
- Developed batch asset-query, batch-transfer, and address-generation tooling.
- Enhanced gas-fee scripts for efficient PGA batch operations.
- Assisted with Issuer auto-penalty upgrade for user-facing versions.
These tools continue NBW’s shift from manual operations to scriptable, observable, and testable infrastructure – a core NBW 2.0 objective.
NBW Conclusion
NBW is now executing across all three NBW 2.0 pillars at once:
(1) BPoS consensus design and contracts for long-term decentralized governance,
(2) automated testing and degradation/recovery validation for infrastructure reliability, and
(3) user-facing reliability via EE Wallet and BTCD fixes plus ecosystem tooling for PGA.fun launches.
Together, these upgrades move PGP and BTCD closer to a high-throughput, community-governed BTCFi platform with robust operational tooling.
Elastos World Computer Initiative (WCI)
World Computer – Wasm “Bare Metal”, AppCapsules, WebSpaces & ElastOS
This week’s WCI work continued refining the architecture that underpins the Wasmer + MCP runtime and aligned it with Rong Chen’s third-generation component philosophy. The focus: treat WebAssembly as the execution “bare metal,” treat applications as self-contained AppCapsules that bring their own OS, and treat WebSpaces + DIDs as the data and identity substrate ElastOS connects.
Rong’s Third-Generation Elastos Design Philosophy
1. WebAssembly as the Target & “Bare Metal” Runtime
- WebAssembly is the execution target for C++ and other modern languages.
- The 4GB sandboxed Wasm runtime is treated as bare metal, with no traditional OS underneath.
2. AppCapsules – Applications That Bring Their Own OS
- Each AppCapsule carries:
- Its own embedded OS components (interrupt handlers, loaders).
- Its own rules about how to verify user access rights.
- AppCapsules represent and protect the interests of the copyright owner of both data and software.
3. DIDs, WebSpaces & PC2
- Blockchain-issued DIDs identify users, software, devices, and “data hard drives.”
- WebSpaces (e.g., pc2.net://) become NDN-based, dynamic data spaces with no single point of failure.
- They go beyond classic websites and map to the interests of platform operators and service providers.
4. ElastOS – Hiding the Internet
- ElastOS sits between hardware OS and Wasm bare metal.
- Applications never “see” the internet directly:
- DDoS, Sybil, and man-in-the-middle attacks are structurally reduced.
- ElastOS represents user interests and dynamically connects AppCapsules, WebSpaces, and IoT devices.
5. Autonomy, Compatibility, and Revenue Sharing
- Apps verify access rights themselves, independent of host OS vendors or media platforms.
- Games, films, AI agents, and IoT no longer break on OS-version differences.
- Smart contracts handle revenue sharing and access enforcement – turning “data into commodity.”
This philosophy now directly informs how MCP, Wasmer, AppCapsules, WebSpaces, and PC2 are being wired together in Elahat’s implementation.
Runtime & System Integration (Context)
- Wasmer continues to be integrated as the execution runtime for AppCapsules.
- MCP defines the interface between AppCapsules and ElastOS / system resources (IO, storage, identity, network).
- Future AppCapsules (media, AI, IoT) will:
- Run on Wasm bare metal.
- Use MCP for all environment calls.
- Bind to WebSpaces identified by DIDs.
The result is a World Computer where software, data, and hardware each have their own WebSpaces, and AppCapsules coordinate via ElastOS and blockchain smart contracts to enforce access and share revenue.
Strategic Outlook
- NBW is building the BTCFi and consensus backbone (BTCD, PGP, BPoS, wallets, automation).
- WCI is defining the execution substrate (Wasm bare metal, AppCapsules, WebSpaces, ElastOS).
- Together, they converge into:
- A Bitcoin-secured World Computer.
- User- and creator-owned applications and data spaces.
- Composable revenue rails for media, software, AI, and IoT.
