Ready to build with us?
Read the docs and join the community on Discord.
The dWallet Network empowers Web3 builders to create Zero Trust Protocols (ZTPs) operating natively across any blockchain.
ZTPs, or Zero Trust Protocols, are cutting-edge Web3 protocols that ensure every action is continuously verified, eliminating inherent trust, across any network. The core of this architecture is dWallet, empower developers to build ZTPs that provide native Zero Trust security and seamless interoperability, revolutionizing security across diverse networks.
As Web3 evolved, networks with their own "zones of sovereignty" emerged, allowing protocols to inherit their Zero Trust architecture.
Traditional solutions operating across networks rely on third parties, turning Zero Trust Protocols (ZTPs) into Castle-and-Moat Protocols (CMPs).
dWallets empower builders on L1s/L2s to develop ZTPs operating across networks.
dWallet Network introduces Zero Trust Protocols (ZTPs), a revolutionary solution to both the Sovereignty Problem and the Honeypot Problem. dWallets, our innovative cryptographic primitive, can be used by ZTPs to enforce logic on user-generated signatures for transactions on any network.
dWallet is not a user-facing application, it’s a building block empowering Web3 builders to create ZTPs that operate across different blockchains.
A dWallet always requires the user to generate a signature, together with a threshold of validators of the massively decentralized dWallet Network.
2PC-MPC, the state-of-the-art threshold ECDSA scheme created by the dWallet team, enables the first noncollusive scalable signing mechanism.
With dWallets, builders can create ZTPs that operate across multiple networks while maintaining Zero Trust. The logic for what a dWallet signs is determined by the ZTP, and executed by a ⅔ threshold of the massively decentralized dWallet Network - with user participation cryptographically enforced.
ZTPs use dWallet technology to interact with different Zones of Sovereignty without losing Zero Trust.
A dWallet has an address on every network, and ZTPs control the logic of whether a signature is generated.
A ZTP built on an L1/L2 can control a dWallet, and since the user is always required it retains the Zero Trust assumptions.
Read the docs and join the community on Discord.