|
Editor’s Note — added 20 May 2026 This page is retained as a historical record. The work described here was carried out by the NBW Foundation (formerly the Elastos Foundation) — not by Elastos DAO. Elastos DAO did not issue, fund, operate, guarantee, or approve BTCD or any of the activity reported on this page. For the current position of Elastos DAO and Elacity Labs, please read: Elastos, Where We Stand Today. About this specific update: This is a weekly report from the NBW Team (led by Sunny / Feng Han) covering BTCD 2.0 Keeper decentralization discussions, Oracle service integration testing for BPoS/DAO node lists, and BTCD operational responses. The NBW Team is part of the NBW Foundation. Elastos DAO did not commission, fund, supervise, or approve any of the work reported here. |
Note: Behind the Code is now being discontinued. Going forward, updates will be published as shorter, separate articles per team to make them easier to read and share.
This article covers the NBW Team, led by Sunny (Feng Han). NBW builds and maintains core Elastos infrastructure and ecosystem systems including: Elastos Essentials Superwallet, the Elastos blockchain, Elastos sidechains, the BTCD Protocol, the BTCD Keeper (previously BeL2 Arbiter), and the BPoS staking / block production system. Despite limited working days, NBW advanced BTCD 2.0 Keeper decentralization discussions[1], initiated Oracle service integration testing for BPoS/DAO node lists, and responded rapidly to a live ecosystem security incident by implementing blacklist contract functionality to protect assets.
NBW Team Development Weekly Report
1. BTCD 2.0 Keeper Decentralization — design discussions progressed
- Multiple rounds of technical discussion continued toward a Keeper decentralization scheme.
- Assessed impacts on current architecture and trust model.
- Evaluated feasibility and security trade-offs across approaches.
2. Security Incident Response — Filda attack handled
- Rapid response and remediation planning with community members.
- Developed a blacklist contract mechanism to add attacker addresses to a blacklist via DAO member cooperation.
- Cross-chain arbiter blacklist support: blacklisted addresses cannot withdraw to mainchain.
- Tested ESC sidechain blacklist contract and resolved deployment issues.
3. BPoS Infrastructure — Oracle integration testing started
- Continued Oracle development to submit BPoS and DAO node lists.
- Initiated Oracle server integration testing.
4. BPoS Contract Ops — node processing scheme explored
- In-depth discussion on the technical scheme for BPoS contract node processing.
- Ran related script tests to validate direction and edge cases.
5. Product QA — BTCD + EE Wallet
- BTCD app: local compilation, verified fixes, discovered and filed new issues, continued tracking.
- Elastos Essentials Wallet: processed issues from released versions to keep stability high.
Next Week
- Deepen BTCD 2.0 Keeper decentralization design and start documenting an implementable path.
- Complete Oracle service integration testing and continue refining BPoS node-processing scheme.
- Finish testing and verification of blacklist functionality to harden ecosystem security.
- Continue BTCD + EE Wallet issue verification, fixes, and regression testing.
Conclusion
Even with holiday constraints, the week delivered meaningful progress on three priorities that matter operationally: (1) BTCD 2.0 decentralization planning, (2) Security response, and (3) BPoS governance infrastructure. The Filda response, in particular, demonstrated that NBW can deliver protective mechanisms quickly under pressure while keeping the roadmap moving.
Footnotes
- [1] BTCD 2.0 Keeper decentralization is an NBW Foundation roadmap item. Elastos DAO did not approve, fund, or commit to this roadmap.
