Witt

⛓️ Since the inception of Bitcoin, the core principle of web3 and blockchain has been clear: allow users to transact without requiring them to trust third parties - or in other words Zero Trust. Blockchain networks embody #ZeroTrust as the most fundamental principle determining their architecture and design. These networks operate as "Zones of Sovereignty" with Zero Trust architecture, that can be inherited by protocols that operate within those zones. Zero Trust architecture means the user doesn't have to trust anyone, not even the network operators (miners or validators) and can always reconstruct and verify the entire state, making sure every transaction ever made was valid. No amount of nodes compromised could generate a signature on behalf of a Bitcoin or Ethereum user. The "Sovereignty Problem" came to light when builders wanted to operate across different networks. Operating across multiple Zones of Sovereignty (interoperability) requires trusting a third party to sync between the states of the zones. If a third party is required, Zero Trust must be abandoned, and builders resorted to 🏰 Castle-and-Moat architecture. 🏰 Castle-and-Moat architecture refers to a "moat", a security perimeter, defending a "castle", a protected asset or system. In the context of legacy web3 interoperability, a bridge is an example of a Castle-and-Moat protocol (CMP) where the castle is the user assets deposited to the bridge, and the moat could be a multi-sig, MPC, hardware security, or any other physical or digital way the bridge defends against malicious actors trying to drain the user's assets. Unlike Zero Trust, where no amount of compromised nodes can generate a signature on behalf of a user and drain their assets, in a CMP that scenario is possible, turning the CMP into a honeypot. Another problem is that this model assumes threats are mostly external, which simply isn’t the case in today’s complex threat landscape. A CMP is especially vulnerable to insider threats and APTs (Advanced Persistent Threats). Relying on trusted intermediaries goes against the Zero Trust principles blockchain was built on🛡️ and over the past years we've seen numerous occasions where the reasoning behind that became painfully evident, as billions of dollars were drained from bridges and other interoperability solutions, exploiting their Castle-and-Moat architecture. The solution is Zero Trust Protocols - ZTPs - that operate across different networks without removing the native Zero Trust security of those networks. ZTPs became possible for the first time with the @dWalletNetwork, utilizing the novel 2PC-MPC scheme to enable the #dWallet primitive, a building block for builders allowing 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 the users' assets. Any logic can be implemented (custody, DeFi etc.) across any network, including Bitcoin, and users can operate with native assets from different networks without the risks of bridging and wrapping. ZTPs flips the script, ensuring that every request is verified, every time. Builders don't need to resort to the assumptions and trust required by CMPs, but can operate freely across networks preserving their native Zero Trust security, exactly as blockchain was designed.

We're thrilled to announce the collaboration with @monad_xyz 🤝 @dWalletNetwork is bringing native multi-chain DeFi to Monad, the fastest EVM-compatible Layer 1 blockchain. This is a game-changer for building secure & scalable DeFi apps. More 👇 dwallet.io/blog/dwallet-mona…