Category: grants-program operating system / application-layer grant orchestration / review-workflow infrastructure
Summary: Questbook is best understood not as a single grants portal, but as a grants-program operating system that combines onchain workspace / grant / application contracts with a much thicker application layer for reviewer workflows, compliance, communications, and payout coordination. Its reusable mechanism is the split between a relatively simple onchain grants-orchestrator core and an operator-heavy workflow layer that decides how proposals are evaluated, who may review them, what rubrics matter, and how approved payouts actually get executed. That makes Questbook a useful comparison class for Gitcoin Grants Stack, Allo, and other ecosystem-funding tools where practical authority often sits less in the funding contract and more in the program-management surface above it.
What it does:
Lets protocols create DAOs or workspaces that act as containers for grant programs
Uses a Workspace Registry, Grant Factory, Grant, and Application Registry contract set to create and manage grants and applicant records onchain
Provides a frontend for permissionless grant-program creation, proposal submission, and applicant / reviewer coordination
Supports custom rubrics, multi-stage review workflows, voting setups, and reviewer role / permission design for each grant program
Integrates payout and execution tooling such as Gnosis Safe multi-sig flows and multiple wallet options
Adds compliance and operations surfaces including KYC/KYB verification, legal-document workflows, direct communications, and notifications
Key claims:
The contracts README explicitly calls Questbook a Decentralised Grants Orchestrator and breaks the core onchain architecture into four contracts: Workspace Registry, Grant Factory, Grant, and Application Registry
The frontend README makes clear that the practical product is much thicker than the contracts alone: custom evaluation rubrics, flexible voting and governance systems, multi-stage review workflows, and fine-grained reviewer permissions are treated as first-class features
The strongest analytical point is that workspace creation and grant deployment may be permissionless, while actual decision power still concentrates in whoever defines review criteria, chooses reviewers, and controls payout execution infrastructure
The presence of Gnosis Safe, multiple wallet integrations, and notification / communication tooling shows that Questbook is not just publishing grants onchain; it is trying to become the operating system through which ecosystems run the entire program lifecycle
Built-in Synaps KYC/KYB and DocuSign flows are especially important because they show how compliance and legal gating can be layered directly into an ostensibly open onchain grants process
The live app foregrounds a grantee list, referrals to grant managers, and ecosystem-scale usage metrics, suggesting Questbook also functions as a builder-discovery and application-routing surface rather than merely a contract wrapper
The gap between the simple contract architecture and the much richer frontend workflow is analytically useful: it reveals how much real authority in grants systems migrates upward into application-level review, permissions, and operational tooling
Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest primary materials were the live app plus the official contracts and frontend repositories; see ../whitepapers/questbook-primary-sources-2026-05-09.md.