Since Bitcoin's inception, the core principle of Web3 and blockchain has been clear: allow users to transact without needing to trust third parties—embracing the concept of Zero Trust. Blockchain networks embody #ZeroTrust as a fundamental principle shaping their architecture and design. These networks operate as "Zones of Sovereignty," with Zero Trust architecture that can be inherited by protocols within those zones.
Zero Trust means users don't have to trust anyone—not even network operators—and can always reconstruct and verify the entire state of the network, ensuring every transaction is valid.
However, the "Sovereignty Problem" emerged when builders wanted to operate across different networks. Operating across multiple Zones of Sovereignty (interoperability) traditionally requires trusting a third party to sync between zones' states. If a third party is involved, Zero Trust is compromised, forcing builders to adopt Castle-and-Moat (#CMP) architecture.
CMP architecture refers to a "moat"—a security perimeter—defending a "castle," the protected asset or system. In legacy Web3 interoperability, a bridge exemplifies CMP, where the castle is user assets deposited to the bridge, and the moat could be a multi-sig, MPC, or other security mechanisms defending against malicious actors attempting to drain assets.
Unlike Zero Trust, where no amount of compromised nodes can generate a user signature or drain assets, CMP architecture is vulnerable, turning it into a honeypot. CMP also assumes threats are mostly external, which isn't the case in today's landscape. CMP is especially vulnerable to insider threats and Advanced Persistent Threats (#APTs).
Relying on trusted intermediaries contradicts Zero Trust principles, the foundation of blockchain technology. Over the past years, we've seen numerous cases where billions of dollars were drained from bridges and other interoperability solutions due to their CMP architecture.
The solution lies in Zero Trust Protocols (#ZTPs) that operate across different networks without compromising the native Zero Trust security of those networks. ZTPs became possible for the first time with dWallet Network, utilizing a novel 2PC-MPC scheme to enable the #dWallet primitive—a building block for builders that allows them to sign transactions on other networks, requiring both a user and a network to generate the signature.
With ZTPs, the user is always required, so no amount of network participants can drain users' assets. Any logic can be implemented across any network, including Bitcoin, allowing users to operate with native assets from different networks without the risks associated with bridging and wrapping.
ZTPs ensure that every request is verified, allowing builders to operate freely across networks while preserving their native Zero Trust security. This approach not only protects users but also stays true to the fundamental principles that blockchain technology was built upon.