Last updated
| Roadmap🗺️ | Tokenomics📊 | Fundraising💰 | White paper📄 | Blog📰 |
|---|---|---|---|---|
Yes✅ | Yes✅ | No ❌ | Yes✅ | Yes✅ |
Mainnet: Q3 2024 | Supply: WARP: 250M WARD: 250M | ➖ | April 17 2024 | Website |
Alfama Testnet - Completed ✅
Buenavista Testnet - Completed ✅
Chiado Testnet - Currently Live 🔥
The Warden Protocol is a modular L1 blockchain for omnichain applications, "OApps". Our mission is to empower developers to simply launch secure OApps by giving them modular infrastructure for security, interoperability and chain abstraction.
Its main goal is to provide developers with the ability to easily launch secure OApps using a modular infrastructure for security, interoperability, and chain abstraction. The project distinguishes security at both the protocol and application levels, providing isolated security for each OApp inherited from the Warden Protocol. This allows each application to define its own security and reduces the threat risk at the protocol level. Inheriting security at the application level also ensures resilience against various types of attacks and maintains network effects, ensuring uniform protection when scaling the number of applications.
Web3 will not onboard billions of users unless we rethink and unbundle the security stack.
Shared protocol security entails applications on a given infrastructure adhering to the infrastructure’s security requirements, like L2 solutions. These monolithic systems impose equal security on their applications. A vulnerability on a monolithic protocol suddenly doesn’t affect a single application, but depending on the type of bug, it can impact several, leaving developers and users with no means of recourse or correctional mechanism.
In contrast, isolated security allows each application to define its own security. This is sometimes seen on apps built on messaging protocols, like LayerZero. Each application developer defines its own relayer, oracle and validation libraries alongside a set of other security configurations. Each user has to separately validate the risk inclined with every application they want to use. It also assumes developers are trusted, reliable and honest third-parties.
Warden Protocol distinguishes between application, and protocol-level security. Each OApp inherits protocol security from Warden Protocol. The protocol acts as a security aggregator and stabilizing force for the OApp ecosystem. Security guarantees include its replicated, permissionless proof-of-stake consensus mechanism, the fault-tolerant and liveness properties of consensus, the validator set and node authentication, its secure channel communication, fork detection and handling, as well as its finality and censorship resistance. OApp developers retain network effects, and they don’t have to bootstrap new validators for nascent applications. They don’t incur the overhead of having to operate their own infrastructure, they have a lower security budget and are less susceptible to sybil-, long-range, eclipse or 51% attacks which will all contribute to lowering the barriers to new deployment. Each OApp is collectively secured by all the WARD staked on Warden Protocol.
Additionally, OApps inherit application-level security from keychains, and their Intent Engines. This is critical, because the application layer is closest to users, and represents the largest attack vector. With keychains and the Intent Engine, OApp users can configure distributed key creation, signatures, threshold signature schemes, role-based access controls and administrate signing authorization. This creates resilience against private key exploits, theft, spoofing and sweeping.
Thanks to this modularity, OApps can support the same application deployed with different security models, achieving homogeneous protocol security with heterogeneous, isolated application security. Users can choose their trust assumption, while application developers retain the network effects of being able to use the same shared protocol security without incurring security fragmentation when scaling the number of applications. In addition, they stay responsive when new security technologies emerge.
Warden Protocol is a high-throughput, low-latency, instant-finality blockchain platform for OApps developers. In monolithic blockchain architectures, all security components of an application are tightly integrated into a single, centralized unit. Due to this component bundling, a vulnerability in the system can compromise any and all applications. Contrary to monolithic end-to-end blockchain architectures, we have modularized the Warden Protocol for security, interoperability, and chain abstraction.
Application developers can assemble and disassemble a set of composable modules and use standardized, chain-agnostic syntax to create a new type of user experience - OApps. Each OApp component is developed, tested, documented, and benchmarked distinctly and can be used individually or in combination with other components. All components are configurable by OApp developers. Any application developer can add Warden Protocol custom modules to their existing base app to turn their application into an OApp.
Utilizing Warden Protocol as a shared platform, OApp developers can tap into established infrastructure and pool resources, granting them a competitive advantage that’s lacking in standard applications. They can sidestep establishing and maintaining a validator set and relayer network, and can leverage built-in support for keychains, intents, block explorers, wallets, oracles, bridge, data indices and security monitors. This reduces development costs, accelerates deployment timelines, and permits OApp developers to concentrate on creating application specific moats, rather than duplicating tools, resources and infrastructure.
