RGB super-compatibility is not a promise but an engineering discipline enforced with zero tolerance for regression. RGB on Lightning: Walking with Upstream While the previous release proved that RGB could connect to Lightning through full LDK state machine compliance, 1,019 tests, and CLN/LND interoperability, the latest release now answers the harder question of whether RGB can evolve at Lightning's pace without friction — and it does. We synced our upstream dependencies with the Lightning mainline, absorbing 16 medium-or-higher security fixes, including critical vulnerabilities that were never backported. We’ve formalised this approach as bLIP-0070, encoding super-compatibility at the protocol layer via feature bits 826 (mandatory) and 827 (optional), along with TLV type 827167. Compatibility only earns the right to the real work of making Lightning’s most advanced primitives asset-native: Splice support, already live in BTC channels, will extend to RGB channels for adjusting capacity without closing, while Async Payments and offline receipt of value will carry over to RGB assets, and JIT liquidity will follow—all without bridges, custodial wrappers, or separate networks, leaving simply the Lightning Network with RGB as its invisible programmable layer. Compatibility is not pitched as a feature; it is shipped as infrastructure, making Bitcoin smart.