Welcome to this week’s Behind the Code, your inside look into the engineering teams building the Elastos SmartWeb. This week, NBW pushed BTCD from “upgrade exploration” into “upgrade refinement,” with a deep technical focus on a BTCD 2.0 flexible repayment period model designed to remove fixed-term constraints and improve competitiveness. In parallel, community governance advanced materially; the BPoS nodes participation in PG chain block production motion passed by community elected Elastos DAO Council members, backed by continued contract audit work, incentive tooling design, and the start of an Oracle service to synchronize node information on-chain.

This week also delivered a step-function in Elacity’s personal cloud roadmap. PC2 moved from “a UI shell” to a production-grade environment powered by a sovereign AI assistant that can act locally with filesystem tools, multi-provider model support, and verified user isolation, the missing layer that makes personal clouds feel alive rather than hosted.

NBW Team Major Achievements This Week

1. BTCD 2.0 Repayment Flexibility

• Multiple rounds of technical discussion on removing the current 90-day fixed repayment period.
• Architecture + implementation path explored for flexible repayment periods.
• Detailed assessment of impacts to liquidation logic, risk controls, interest calculation, and collateralization ratio management.
• BTCD 2.0 scheme refinement continued with broader feasibility discussion and technical framing.

2. BPoS Block Production Proposal Submitted to Cyber Republic

• Completed discussions with Western DAO council members and formalized the design as a DAO proposal, which is now passed.
• Strategy discussions were held with the Elastos Infinity team about designing a clear UI/UX portal for node reward distribution to stakers.
• In-depth discussion of a tool implementation scheme for distributing BPoS node gas fees to voters.
• Distribution methods + implementation logic clarified as a technical foundation for sustainable incentives.

3. Oracle Service Development Initiated

• Started Oracle service development to submit DAO and BPoS nodes information.
• Provides infrastructure for on-chain data synchronization and node management reliability.

4. Monitoring System Data Accuracy Improved

• Changed monitoring API logic so BTCD supply statistics shift from historical aggregation to active data.
• Resolved data consistency issues across ELA/FIST API interfaces and improved observability fidelity.
• Knowledge transfer performed: monitoring code paths, API data generation, and listener script logic explained to team members.

5. Security Audit Fixes and Wallet Release Readiness

• Responded to Beijing Institute of Technology audit findings: implemented stricter value validation for staking scripts and bug fixes.
• Investigated Issuer auto-unlock failures; network anomalies identified as the likely root cause and a target for stability work.
• EE Wallet 3.2.12 development completed with testing, bug fixes, and full release readiness.

Closing

This week, the NBW development team made significant progress in BTCD 2.0 protocol scheme refinement, BPoS block production mechanism advancement, monitoring system optimization, and EE wallet version preparation.

Elastos World Computer Initiative (WCI) — Elacity Labs

This week delivered a major step-function in the personal cloud roadmap: the PC2 environment moved from “a chat box” to a production-ready AI assistant that can safely operate inside a user’s own cloud, with full filesystem capabilities, multi-provider model support, and verified user isolation. This establishes the missing layer that makes personal clouds feel “alive”: an embedded assistant that can read, write, organize, and operate locally without collapsing back into centralized infrastructure.

1) Personal Cloud AI Assistant and Tool System

What “AI inside a personal cloud” means

• Streaming chat interface that feels native inside PC2.
• Local tool execution on user-owned storage (files, folders, metadata).
• Strict user boundaries: one user cannot see another user’s data.
• Local-first by default, with optional cloud providers for users who want them.

2) AI Chat Foundation Completed

• Core AI chat service with streaming responses and tool execution support.
• Chat UI delivered: conversation history, streaming display, tool-call visualization, image/PDF upload support.
• Settings UX delivered: provider selection, API keys, model configuration, wallet-scoped settings storage.

3) Multi-Provider Model Support Completed

Unified provider interface

• Local inference default via Ollama with DeepSeek 5b.
• Optional cloud model providers supported without changing UX or tool interface.

Providers implemented

• Ollama (DeepSeek 5b local default)
• OpenAI
• Claude
• Gemini

4) IPC Tool System and Backend Tool Injection Completed

• Hybrid tool architecture:
  • Application tools exposed by installed apps
  • Built-in filesystem tools injected by the backend
• Apps can register capabilities and the assistant can discover/use them automatically.
• Tool sources tracked for debugging and trust boundaries.

5) Security and User Isolation Completed

• Discovered and fixed a privacy issue where chat history could be visible across users due to unscoped local storage keys.
• Fixes implemented:
  • All conversation storage keys made wallet-scoped
  • Wallet switching logic implemented
  • Cleanup on logout implemented
• Verification performed:
  • Backend scoping across DB/API confirmed
  • Tool execution isolation confirmed
  • Provider configuration isolation confirmed

6) Tool Execution Fixes and Reliability Completed

• Improved tool call finalization (notably Claude tool completion behavior).
• Fixes to backend tool auto-injection and execution flow.
• Database and server startup reliability improvements.
• Improved logging for diagnosis and support.

7) What This Unlocks Next

• Agent orchestration and multi-step workflows inside PC2.
• Deeper tool discovery across installed applications.
• More structured memory/context management.
• Standardized tool protocol integration patterns.

Work completed this week delivered:

• AI assistant with streaming chat
• Filesystem tool execution (15+ operations)
• Multi-provider models (local + cloud)
• Settings UI and wallet-scoped configuration
• IPC tool discovery for app integrations
• Verified user isolation
• Production hardening and documentation

Closing

This week was an architecture week disguised as an implementation week. By turning PC2 into a real AI-capable environment with tools, isolation, and extensibility, the system moved from “a personal cloud that stores files” to “a personal cloud that can operate itself.” That transition is the prerequisite for everything downstream: autonomous personal clouds, tradable digital capsules, local-first agents, and user-owned computation.