<100 subscribers
One of the biggest challenges for onchain, permissioned applications is real-time access control. Many applications require onboarding or modifying permissions on an ongoing basis. Some apps rely on centralized databases, while others use Merkle trees for onchain verification. However, Merkle trees introduce delays and friction, which can slow down your application and hurt the user experience.
With Quible, you can onboard users seamlessly while maintaining real-time access control—and keep everything fully onchain. Quible brings permissioned applications to life, providing a frictionless solution.
Merkle trees, while efficient for providing compact, verifiable proofs, are inherently static structures. When you modify an access list—whether adding or removing a participant—you aren't technically updating the Merkle tree itself. Instead, you're generating an entirely new Merkle tree with a new root that must be posted onchain. This process can be slow and cumbersome. On Ethereum mainnet, transactions can take an average of 11 minutes due to confirmation times and network congestion.
For onchain builders, these delays are unacceptable. Whether you're running an NFT drop, token sale, or compliant DeFi app, instant verification is essential for remaining competitive in today’s environment.
Quible enables seamless, real-time access control without the delays of constant Merkle root updates. It also allows you to keep everything onchain, without sacrificing speed or performance.
Here’s how it works: the Quible Network uses Quirkle trees, which are fully onchain. You only need to publish your Quirkle root once on the home chain that your application operates on. Instead of recalculating and updating your root every time there’s a change, you can make updates to your Quirkle tree on the Quible Network—without having to adjust the root.
Contracts on any chain can simply make an RPC call to the Quible Network to verify if a user is on an access list. This verification happens in real time, without the friction of updating an onchain Merkle root.
Faster Onboarding: With Quible, users can be onboarded instantly, without waiting for Merkle root updates or lengthy blockchain confirmations. The moment they meet the conditions or sign up, they gain access— leading to a far smoother user experience.
No Root Updates: Traditional systems require regular Merkle root updates onchain—a costly and time-consuming process. Quible eliminates this entirely by supporting a persistent Quirkle root, which means that its value stays the same while you update your list.
Seamless Integrations: Quible integrates easily with existing applications. Your smart contract makes an RPC call to Quible, checking if a user is on an access list. This works similarly to Chainlink, which operates on its own network while serving data to other blockchains.
Fully Onchain: Unlike some systems that rely on centralized components, Quible is entirely decentralized and trustless. All updates happen on the Quible Network—a decentralized, verifiable layer that provides real-time access control.
In the crowded onchain world, user experience is a major differentiator. Friction during onboarding or access control can frustrate your users and drive them away. Relying on centralized solutions for permission management undermines the ethos of decentralization and introduces potential security risks.
If you’re building permissioned onchain applications, you shouldn’t have to choose between speed and decentralization. With Quible, you get the best of both worlds: real-time, frictionless onboarding, and fully onchain access control. No more waiting for root updates, and no more delays.
Website: https://quible.network
Whitepaper: https://quible.network/whitepaper
Twitter: https://twitter.com/QuibleNetwork
Quible Network
