Access control is crucial for onchain applications, with use cases ranging from NFT drops to real-world asset (RWA) issuance and everything in between. Traditional methods like Merkle trees have served this purpose, but come with limitations. Today we introduce Quible, a novel protocol designed to be the onchain Authentication Layer for Web3 —our answer to these limitations.

Quible is a next-generation blockchain network that redefines access list management. By enabling real-time access control, Quible ensures decentralized applications (dApps) can adapt to dynamic user lists. At the core of Quible is the Quible Network - a decentralized storage and signature generation network, and Quirkle trees—a powerful, efficient, and flexible alternative to Merkle trees for storing and verifying access lists.

Current access control methods like Merkle trees are becoming increasingly outdated as onchain applications scale. They come with significant limitations for developers - for one, these solutions place a heavy burden on applications, requiring them to generate, store, and distribute Merkle proofs to users. This burden translates into the need to write and maintain substantial amounts of code—often involving 1,000-1,500 lines and 50-100 developer hours, assuming the leanest implementation. For more complex systems, these requirements are even higher.

As onchain applications scale, these methods are becoming increasingly outdated, requiring frequent and costly updates that are cumbersome to manage, especially in high-traffic environments.

Quible offers a streamlined solution to these challenges. By managing access lists with Quirkle trees, Quible significantly reduces the codebase and development time needed to implement secure, real-time access control. Quirkle trees allow for real-time updates without the need for gas-consuming transactions on the host chain, eliminating the need to store and share proofs. This makes Quible particularly useful for compliant DeFi apps, RWA issuance, NFT drops. In addition to cutting down on code bloat and simplifying processes, Quible helps teams save valuable time and resources, ensuring you remain lean.

Quirkle trees offer several key advantages over traditional Merkle trees, making them the superior choice for modern onchain applications:

• Root Persistence: One of the major benefits of Quirkle trees is root persistence. Unlike Merkle trees, where the root changes every time you add or modify data, Quirkle roots remain consistent. This stability simplifies operations and reduces the need for continuous updates, making the system more efficient.

• Incremental Updates: Quirkle trees enable incremental updates, allowing you to add or remove individual addresses without recalculating the entire tree or pushing a new state. This feature drastically reduces computational overhead and simplifies the process of managing dynamic lists.

• Bringing More Operations Onchain: Quirkle trees bring more of your operations onchain, which is beneficial for transparency and aligns with this industry's values. By keeping more processes onchain, you enhance trust and visibility, the primary reason many are here.

These features make Quirkle trees not only more efficient but also better aligned with the needs of scalable, transparent, and dynamic onchain applications.

The Quible Network's architecture includes the following participants:

• Authors: Entities that create and update access lists in real-time. Authors can add or remove addresses, ensuring that access data is always accurate and up-to-date.

• Nodes: These validate updates through a consensus process and store the access lists for quick verification, ensuring reliability and security.

• Requestors: Client-side applications or users that gain access to services by requesting proofs from Quible’s nodes, ensuring seamless and secure user experiences.

Consider a permissioned crypto application. Traditionally, developers would need to create and store a Merkle tree, generate proofs, and share them with users—adding unnecessary complexity and cost. This process often involves writing 1,000-1,500 lines of code, even on the lower end, to handle these tasks. Managing these proofs, as well as building and maintaining the system, can be resource-intensive and prone to errors.

With Quible, the process is streamlined. Developers can author a Quirkle tree, add user addresses, and configure the application using the Quirkle root. Users then obtain proofs directly from the Quible Network, eliminating the need for teams to manage storage and reducing the resources required to implement access control.

If the application needs to update the access list—such as adding or removing a user—this can be done instantly via the Quible Network, in an incremental update. The changes are reflected in real-time, ensuring your permissioning remains seamless.

For a deeper dive into how Quible and Quirkle trees are set to revolutionize access control and save you countless developer hours, visit our whitepaper. It provides detailed insights into the vision behind Quible, as well as additional architectural details.

Get involved early by joining our Guild and following us on Twitter!

Website: https://quible.network
Whitepaper: https://quible.network/whitepaper
Twitter: https://twitter.com/QuibleNetwork