Project & Team
Description of Project
Provide a concise narrative that clearly states each of (a)–(e) below.
- (a) Problem the project solves — The problem the project is solving.
- (b) Operational priorities — Provide a high-level description of how the project expects to support ongoing development and operations over time.
- (c) High-level project overview — How the project works at a high level.
- (d) Primary token functions — The primary functions of the token (e.g. gov participation).
- (e) Control surface reliance — If any, briefly describe the anticipated or possible evolution of the protocol's governance/control model.
(a) Problem the project solves
The Quip Network is solving coordination failures in quantum and high-performance computing: restricted talent, unclear returns on investment, integration friction, under-utilization, and post-quantum migration. A customer may identify a problem suited to quantum computation but still lack the information needed to buy a solution, including the method’s constraints, how to compare conflicting vendor claims, and how to measure quantum advantage against a tuned classical baseline. Most quantum vendors sell vertically integrated stacks, publish benchmarks that are not obviously comparable, and prevent solutions from porting easily between vendors. At the same time, quantum machines are capital-intensive, carry fixed costs at every utilization level, and create lost revenue during idle hours. The hardware that can address these coordination failures can also break much of the classical cryptography securing the internet, while waiting to rotate keys after the threat appears does not address advance collection of public keys, leaves unmigrated networks exposed to chain-wide reorganization attacks, and turns in-place upgrades into a multi-year coordination problem.
Quip Network solves these coordination problems by sharing a talent pool with open source solvers and infrastructure and providing easy onramps for new quantum devs, by clarifying ROI with a distributed ledger of paid benchmarks and an immutable history showing what consumers are willing to pay for, by reducing integration friction with a unified VM, API, and pricing schedule, under-utilization with a spot-priced, pre-emptive proof of useful work, and post-quantum migration with a quantum-resistant OTC swap protocol and account management system that unifies existing networks with a quantum-resistant account wrapper.
(b) Operational priorities
Quip expects to support ongoing development and operations through a combination of protocol-maintenance incentives, treasury funding, fixed emissions, and staged decentralization. Protocol developers maintain the runtime, execution VM, and Proof-of-Useful-Work parameters, add implementations as algorithms and hardware improve, and receive a share of fees from every solved block and proof. The protocol treasury receives a share to fund maintenance and development, and protocol fees are used to buy QUIP and place it into permanent liquidity positions rather than burning it. Network operations are also supported by a fixed annual emission of 40 million QUIP; the Quip Control Asset divides emissions among subnets, and holders direct emissions each epoch toward the subnets they want to fund. New problem classes must be proposed through structured subnet proposals, and a new problem class receives no emission until the proposal defines how the protocol will score its work and settle its claims. During Genesis and early phases, the Quip Foundation reviews proposals and deploys subnet infrastructure after checking market demand, technical feasibility, available hardware partnerships, and resource requirements. Over time, Quip decentralizes in stages: the Foundation gates Genesis, and permissionless subnets and the Control Asset take over emission routing after the mechanism proves itself.
(c) High-level project overview
The Quip Network is a decentralized high-performance computing protocol built around a spot compute clearinghouse, an open-source library of composable solvers, and a hybrid quantum-classical router and scheduler. Consumers bid for idle compute and use expert-submitted solvers, while operators compete for those bids with CPUs, GPUs, ASICs, and QPUs. The network routes each part of a job to suitable hardware, and the spot clearinghouse routes pre-emptable jobs to available machines, increasing utilization and giving smaller exploratory workloads access to otherwise idle capacity. Quip contracts register, escrow, and settle jobs by binding the consumer’s escrowed bid to a job specification; after a valid result, the contract releases payment, routes royalties, and collects the protocol fee. Each subnet represents a problem class with its own proof-of-useful-work template, verification tier, problem and solution formats, verification functions, and quality-scoring functions. Compute providers execute the work, return the required results, and publish proofs that upper layers can check cheaply. The verified result moves back up the stack for scoring, settlement, and delivery to the consumer. QUIP is the network’s native token and shared unit of compute credit.
(d) Primary token functions
QUIP is the network’s native token and shared unit of compute credit. Consumers can fund accounts with fiat or stablecoins and receive cloud credits, but when a job settles the system converts between credits and QUIP below the interface, consumers see bids and bills in credits, and the network settles in QUIP. QUIP also functions as the reward and fee asset for useful work: useful work at the compute layer triggers newly minted block rewards, most issuance goes to the winning miner, the invoked solver’s algorithm developer receives a royalty, the treasury receives a share, and a verified proof releases the consumer’s escrowed payment while minting the block reward. QUIP also supports governance and emission routing through the Quip Control Asset: in the canonical veQUIP implementation, holders lock QUIP in Interlock-enforced escrow to gain voting weight based on lock duration, voting weight decreases as the lock approaches expiry, and holders use that weight each epoch to direct emissions toward subnets; subnet stakeholders can also pay veQUIP voters through an explicit bribe market to direct issuance toward their problem class.
(e) Control surface reliance
Quip decentralizes governance and control in stages. The Foundation gates Genesis, and after the mechanism proves itself, permissionless subnets and the Control Asset take over emission routing. Vote-escrowed governance starts after the flagship phase proves the mechanism; the Quip Control Asset then begins routing emissions among subnets, and subnet proposals move from Foundation review to permissionless entry. Activation is milestone-based, depending on sustained flagship uptime, fee revenue, unique-user milestones, and clean-security milestones, rather than a calendar date. In Stage 2, the network expands to many subnets competing for emission, and under-performing subnets retire.
Known Project Team
For each existing entity: Labs/DevCo (e.g., Founder, CEO, CTO, COO), Foundation (e.g., President, Executive Director, CFO, COO), and DAO / onchain governance leadership (if applicable) list the:
- (a) full names,
- (b) official titles,
- (c) and prior experience of key team members.
For any non-existent entity, explicitly mention it does not exist. External links may be included but they will not factor into the score.
Labs / DevCo
Full Name | Official Title | Prior Experience |
|---|---|---|
Colton Dillon | CEO | Co-founder of Degen, Hedgehog, Gentleman Labs, and Postquant Labs. Previously CEO/CTO at Hedgehog, CMO at Acorns, and electrical engineer at GM, Intel, and Nike+. |
Richard Carback | CTO | Co-founder of XX Network and Draper Labs. Cryptographer, serial entrepreneur, and founder of the Cyber department at Draper Labs. |
Foundation
Full Name | Official Title | Prior Experience |
|---|---|---|
Not applicable | Not applicable | The Quip Foundation does not yet exist. PostQuant Labs (the DevCo) intends to form a British Virgin Islands (BVI) foundation to issue the token, which will form a Wyoming Unincorporated Nonprofit Association (UNA); upon token issuance, the UNA will become a Wyoming DUNA and the BVI entity will transfer assets and control to it. Foundation officers have not yet been appointed. |
DAO / Onchain Governance
Full Name | Official Title | Prior Experience |
|---|---|---|
Not applicable | Not applicable | No DAO or onchain governance leadership exists. The DAO will not exist until the QUIP token is issued; vote-escrowed governance begins only after the flagship phase meets its activation milestones. |
DAO Structure
Provide a structured description of the DAO's governance, powers, and economic rights. If a DAO does not exist, state so for each sub question. Even if there is no DAO, there must be an answer to (d). Address the lettered items below.
- (a) IP ownership & control — State what IP the DAO owns or controls (e.g., codebases/repos, trademarks/brands). Note any license if relevant.
- (b) Contract/admin powers — List on-chain or administrative authorities and limits: pause/upgrade roles (e.g., multisig pause), governance-executor authorities, and the method of authority for each (e.g., veto, majority, super-majority).
- (c) Locked-token rights (conditional) — If locking/staking for additional rights exists, explain the additional rights and what tokenholders can and cannot decide. If no locking mechanism exists, leave absent.
- (d) Current tokenholder governance rights and economic arrangements — If any, describe the current governance rights of tokenholders and any presently operative rights or arrangements relating to treasury actions, fee-routing, rewards, buybacks, or other protocol-controlled resources. If none, state that explicitly.
- (e) Control surface reliance — If any, briefly describe the anticipated or possible evolution of the protocol's governance/control model.
- (f) Dissolution authority — State who can dissolve/wind up the DAO and by what mechanism (e.g., on-chain vote threshold, board resolution of a legal wrapper).
(a) IP ownership & control
No DAO currently exists, and no DAO will exist until the QUIP token is issued. Accordingly, the DAO does not currently own or control any IP, codebases, repositories, trademarks, or brands. PostQuant Labs, the DevCo, currently owns all project IP. It is the intention of PostQuant Labs to grant unlimited licenses to the project IP to the DAO and the Quip Foundation once those entities exist.
(b) Contract/admin powers
Contract and administrative authority is split between an early Foundation-gated phase and later vote-escrowed governance. During Genesis and early phases, the Quip Foundation gates Genesis, reviews every new subnet proposal, and deploys subnet infrastructure only after checking market demand, technical feasibility, available hardware partnerships, and resource requirements. This centralized period is intended to establish verification playbooks and trust while the mechanism remains unproven. The foundation council will consist of five members voting by simple majority and multisig attestation until the token holders vote to change this structure.
Subnet-creation authority is constrained by a required proposal template. A new problem class receives no emission until its proposal defines the computational domain, admissible claims, verification tier, verification function, quality rubric, expected hardware class, and initial difficulty; a proposal missing any required field cannot activate. After activation thresholds are met, subnet proposals become permissionless, each submission bonds a QUIP stake, and a subnet must attract veQUIP votes before it earns meaningful emissions. A low-quality proposal with no votes receives no allocation, moves toward retirement, and leaves the proposer to bear the cost.
The Quip Control Asset routes emissions among subnets each epoch. In one implementation, veQUIP commits QUIP to Interlock escrow and grants control weight that increases with lock duration and decreases as the lock approaches its end. Each epoch converts control weight directly into proportional emission: a subnet’s share of fixed per-epoch emission equals its share of all weight cast; if no one votes, subnets split emission equally, and rounding remainders go to the largest recipient. The Control Asset binds to a zero-knowledge identity credential and can apply per-identity limits, including quadratic decay in marginal control weight, to reduce capture by an actor splitting balances across wallets.
Retirement authority also runs through veQUIP. A subnet may be flagged for sustained low veQUIP allocation below a viability floor, persistently high failed validations or failed oracle adjudications, or work below the proposal’s quality bar. A subnet that receives no votes loses its emission. A flagged subnet receives a grace period to attract votes, improve verification rates, or restore quality, and unrecovered subnets move operators and open jobs to surviving compatible subnets so committed compute or work in progress is not stranded. A hard wind-down requires a governance action, deregisters the subnet contract, and reclaims its slot; that action uses the same time-weighted vote and the same Foundation-reviewed-to-permissionless progression as subnet creation.
Upgrade authority, administrator fee control, and governance-executor authority is disclosed for protocol and contract surfaces, and will follow Substrate OpenGov voting thresholds and decay curves until such time as the DAO votes to change it. The validator set and tokenholders will use their nominated proof of stake to vote changes, and there will be a decay curve for acceptance starting with 100% required at the initial proposal and decaying to 66% over time, implementing such changes as an onchain upgrade or parameter update. Substrate supports forkless on-chain upgrades, and Quip can use that mechanism to add hash-based account signatures, a post-quantum transaction format, and other quantum-resistant changes to consensus and transactions. Governance upgrades subnet specifications rather than editing them in place, so a live problem class can improve without changing orders already in progress. A Quip Account is scheme-agnostic and upgradeable only under explicit user consent designating a proxy pre-approved by the verifier.
No DAO exists as of filing. Until the Foundation exists, PostQuant Labs' 3-of-4 multisig holds the protocol administrator role, which controls fees only. No pause authority exists.
(c) Locked-token rights (conditional)
Locking exists through the Quip Control Asset, implemented as veQUIP, which has not been deployed yet. Holders lock QUIP in Interlock-enforced escrow to receive time-weighted control weight; longer locks grant more weight, and voting weight decreases as the lock approaches expiry. The escrowed position remains available for lending, borrowing, or use as collateral while locked, allowing holders to participate in governance without leaving the underlying capital idle.
Locked-token holders use this control weight to route emissions among subnets each epoch. A subnet’s share of fixed per-epoch emission equals its share of all weight cast; if no one votes, subnets split emission equally. Holders can also participate in the explicit bribe market: a subnet or backer deposits QUIP for a specified subnet and epoch, and veQUIP holders who voted for that subnet claim the deposit in proportion to their contributed votes. The Control Asset binds to a zero-knowledge identity credential and can apply per-identity limits, such as quadratic decay in marginal control weight, to reduce capture by one actor.
Locked-token holders can influence which subnets receive emissions, vote on subnet proposals and retirements, and, after activation thresholds are met, participate in permissionless subnet entry. A new problem class receives no emission until its proposal defines how the protocol will score its work and settle its claims, and a proposal missing required fields cannot activate. A subnet must attract veQUIP votes before it earns meaningful emission. A subnet that receives no votes loses its emission, and a hard wind-down requires a governance action that deregisters the subnet contract and reclaims its slot.
Locked-token holders do not determine the total annual emission through this mechanism. After the pre-mine has fully vested, subnet emissions continue at 40 million QUIP per year, and Quip emits 40 million QUIP each year regardless of token price, network activity, or the number of subnets. Their voting allocates that fixed emission among subnets rather than changing the fixed emission amount. During Genesis and the early phases, the Quip Foundation reviews every proposal and deploys subnet infrastructure only after checking market demand, technical feasibility, available hardware partnerships, and resource requirements. Vote-escrowed governance starts after the flagship phase proves the mechanism; activation depends on sustained flagship uptime, fee revenue, unique-user milestones, and clean-security milestones, not on a calendar date.
These rights do not exist until the deployment of mainnet and the adoption of the Quip Control Asset by the DAO
(d) Current tokenholder governance rights and economic arrangements
Token holders do not currently have any governance rights, as there is no token to hold. Token holders have no presently operative economic rights or arrangements.
At Genesis and in early phases, the Foundation gates Genesis, reviews subnets, seeds the treasury’s first permanent liquidity positions, and permissioned operator entry uses hardware attestation and KYB where applicable. The staged governance design then moves to tokenholder emission routing after the flagship phase proves the mechanism; activation depends on sustained flagship uptime, fee revenue, unique-user milestones, and clean-security milestones, not on a calendar date. Tokenholder governance is organized through the Quip Control Asset, with veQUIP as the vote-escrow implementation. Holders lock QUIP through Interlock escrow to receive time-weighted control weight; control weight scales with lock duration and decays toward expiry. Each epoch, allocation is proportional to weight cast, with an equal-split fallback if no one votes. Concentration controls are ZK-KYC identity-bound and may use per-identity quadratic decay, though that decay and the control-weight curve are provisional.
Economic arrangements include a disclosed post-premine vesting supply point of 1,000,000,000 QUIP, allocated 40% emissions, 20% premine, 15% insiders, 15% builders, and 10% community. Annual emission is 40,000,000 QUIP on a fixed, flat schedule; implicit decay occurs because fixed emission is divided across a growing subnet set. Useful work triggers newly minted block rewards: most issuance goes to the winning miner, the invoked solver’s algorithm developer receives a royalty, and the treasury receives a share. Protocol fees buy back QUIP into permanent 50/50 liquidity positions, and treasury policy has no burn. Completed QuipSwap fees accrue to the treasury and fund permanent liquidity positions. The protocol also makes vote-buying an explicit permissionless market: a subnet or backer may deposit QUIP into a bribe contract for a specified subnet and epoch, and veQUIP holders who voted for that subnet claim the deposit in proportion to their contributed votes; this turns emission routing into a transparent auction and moves emission toward work buyers will pay most to fund.
(e) Control surface reliance
The protocol decentralizes in stages. The Foundation gates Genesis, and permissionless subnets and the Quip Control Asset are expected to take over emission routing after the mechanism proves itself. Vote-escrowed governance starts after the flagship phase proves the mechanism; at that point, the Quip Control Asset begins routing emission among subnets, surprisal and incentive markets open, and subnet proposals move from Foundation review to permissionless entry. Activation is milestone-based, depending on sustained flagship uptime, fee revenue, unique-user milestones, and clean-security milestones, rather than a calendar date. Stage 2 expands the network to many subnets competing for emission, while under-performing subnets retire. As quantum networking matures, mining pools are expected to connect the network’s compute into globally entangled capacity.
The anticipated governance primitive is the Quip Control Asset, with veQUIP as its vote-escrow implementation. veQUIP uses Interlock-enforced escrow; control weight scales with lock duration and decays toward expiry. Per epoch, allocation is proportional to weight cast, with equal-split as the fallback if no one votes. The control-weight curve is provisional. Concentration controls are intended to be zero-knowledge-KYC identity-bound and to use per-identity quadratic decay; that decay is also provisional.
(f) Dissolution authority
No DAO currently exists, and no DAO will exist until the QUIP token is issued. Accordingly, no person or body currently holds authority to dissolve or wind up the DAO, and no dissolution or wind-up mechanism has been adopted.
Primary Foundation
For the Primary Foundation do the following independently. If a Foundation does not exist, state so for each sub question. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definition: The primary Foundation can be explained as the entity which is directly involved in the issuance of the native token at launch.
- (a) Entity — Type and jurisdiction.
- (b) IP ownership & control — What IP the entity owns/controls (repos/code, trademarks/brand; license optional)
- (c) Powers over DAO, treasury, protocol-controlled resources, and token administration — If any, describe the current powers over DAO governance, treasury actions, protocol-controlled resources (e.g. revenue), token administration, or reward parameters, and the method/threshold for each.
- (d) Powers over DevCo — Explain whether the foundation can exert direct or indirect influence over decision-making of the DevCo.
- (e) Contract/admin powers — Pause/upgrade/governance-executor authorities, and the method/threshold for each (e.g., veto/majority/super-majority).
- (f) Current economic arrangements and distribution policies — Describe any current governance-approved, contractual, or programmatic mechanisms, if any, by which protocol-controlled resources, treasury assets, fees, revenue, rewards, or token distributions may be directed to this entity, its equityholders, contributors, or other participants. If no such mechanism currently exists, state that explicitly.
(a) Entity
The Quip Foundation does not yet exist; attorneys are currently being consulted on its formation. It is the intention of the DevCo, PostQuant Labs, to form a British Virgin Islands (BVI) foundation that will issue the QUIP token. The BVI foundation will form a Wyoming Unincorporated Nonprofit Association (UNA) in parallel. Upon token issuance, the UNA will be converted into a Wyoming Decentralized Unincorporated Nonprofit Association (DUNA), and the BVI entity will transfer its assets and control to the DUNA.
(b) IP ownership & control
The Quip Foundation does not yet exist and does not currently own or control any IP, repositories, code, trademarks, or brand assets. PostQuant Labs owns all project IP until the Foundation and the DAO exist, at which point the IP will be transferred or licensed to them. It is the intention of PostQuant Labs to grant unlimited licenses to the Foundation and the DAO. Once formed, the Foundation is expected to gate Genesis, review subnets during Genesis and early phases, deploy subnet infrastructure after checking market demand, technical feasibility, available hardware partnerships, and resource requirements, and seed the treasury's first permanent liquidity positions.
(c) Powers over DAO, treasury, protocol-controlled resources, and token administration
The Quip Foundation does not yet exist. Once formed, its powers are expected to be concentrated in Genesis and early network operation. The Foundation gates Genesis and, during Genesis and the early phases, reviews every subnet proposal; it deploys subnet infrastructure only after checking market demand, technical feasibility, available hardware partnerships, and resource requirements. Operator entry during Genesis is permissioned through hardware attestation and KYB where applicable. For treasury and protocol-controlled resources, the Foundation seeds the treasury’s first permanent liquidity positions during Genesis. For reward allocation, the Ising optimization and QVRF flagship subnets receive the full emission at launch; vote-escrowed governance starts after the flagship phase proves the mechanism, and the Quip Control Asset then begins routing emissions among subnets. After the network meets activation thresholds, subnet proposals become permissionless; activation depends on sustained flagship uptime, fee revenue, unique-user milestones, and clean-security milestones, and does not depend on a calendar date. The disclosed post-Genesis emission-routing method is that the Quip Control Asset routes emissions each epoch, each subnet’s share of fixed per-epoch emission equals its share of all weight cast, and if no one votes the subnets split emission equally.
(d) Powers over DevCo
The Quip Foundation does not yet exist. Once formed, the Foundation will not exert direct or indirect control over the decision-making of the DevCo, PostQuant Labs. The Foundation will have an arm's-length agreement with the DevCo and will contract with it on an at-will basis.
(e) Contract/admin powers
The Quip Foundation does not yet exist and currently holds no contract or admin powers, including no pause, upgrade, or governance-executor authority. All contract administration currently sits with PostQuant Labs as the deployer and multisig owner (see Section 5e), and will transfer to the Foundation and the DAO once those entities exist. Once formed, the Foundation is expected to gate Genesis, review every subnet proposal during Genesis and the early phases, and deploy subnet infrastructure only after checking market demand, technical feasibility, available hardware partnerships, and resource requirements; after activation thresholds are met, subnet proposals become permissionless.
(f) Current economic arrangements and distribution policies
The Quip Foundation does not yet exist. The Quip Foundation gates Genesis, and the genesis block launches the Sinnet and allocates QUIP. During Genesis, the Foundation reviews subnets and seeds the treasury’s first permanent liquidity positions. When all pre-mine allocations finish vesting, one billion QUIP will have been emitted, allocated as 40% subnet emissions, 20% public and foundation premine, 15% early investors, 15% builders, and 10% community programs. The Foundation receives 150,000,000 QUIP (15%), 100,000,000 at TGE and the rest monthly over 108 months after a 12-month cliff. Allocations for early investors and other team-aligned participants follow a cliff and linear vest, and subnet emissions enter circulation continuously from launch.
Ongoing emissions continue after the pre-mine has fully vested at 40 million QUIP per year, regardless of token price, network activity, or number of subnets. At launch, the two flagship subnets divide the full emission. The Quip Control Asset divides emissions among subnets; in the canonical implementation, veQUIP holders lock QUIP in Interlock-enforced escrow to gain voting weight and direct emissions each epoch. Each epoch converts control weight directly into proportional emission, a subnet’s share equals its share of all weight cast, and if no one votes, subnets split emission equally. Subnets or backers may deposit QUIP into bribe contracts for a specified subnet and epoch, and veQUIP holders who voted for that subnet claim the deposit in proportion to their contributed votes.
Job settlement and useful-work rewards also direct resources to participants. Application developers earn a resale margin and a share of the builder allocation. Algorithm developers receive royalties on invocations. Protocol developers receive a share of fees from solved blocks and proofs. Compute providers earn block rewards and job fees for genuine compute. Validators earn network fees plus emissions, miners earn block rewards and job fees, and nominators stake QUIP behind validators and share the validator’s yield and slashing risk. Useful work triggers newly minted block rewards; most issuance goes to the winning miner, the invoked solver’s algorithm developer receives a royalty, and the treasury receives a share. One verified proof releases the consumer’s escrowed payment and mints the block reward, splitting the emission subsidy among the parties that completed the work.
Treasury and fee policy directs protocol fees into permanent liquidity. The treasury receives a share and converts it into permanent liquidity instead of burning it. Protocol fees are used to buy QUIP and place it in permanent, protocol-owned 50/50 liquidity positions; each purchase adds market depth, lowers the cost of trading QUIP, increases the treasury’s share of pool fees, and keeps the purchased QUIP in the market earning fees.
Primary DevCo
For the Primary DevCo do the following independently. If an entity does not exist, state that explicitly across each sub-question. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist. Definition: The primary DevCo can be explained as the entity which is directly involved in the issuance of the native token at launch.
- (a) Entity — Type and jurisdiction.
- (b) IP ownership & control — What IP the entity owns/controls (repos/code, trademarks/brand; license optional)
- (c) Powers over DAO, treasury, protocol-controlled resources, and token administration — If any, describe the current powers over DAO governance, treasury actions, protocol-controlled resources (e.g. revenue), token administration, or reward parameters, and the method/threshold for each.
- (d) Powers over Foundation — Explain whether the DevCo can exert direct or indirect influence over decision-making of the Foundation.
- (e) Contract/admin powers — Pause/upgrade/governance-executor authorities and the method/threshold for each (e.g., veto/majority/super-majority; "3/5 multisig").
- (f) Current economic arrangements and distribution policies — Describe any current governance-approved, contractual, or programmatic mechanisms, if any, by which protocol-controlled resources, treasury assets, fees, revenue, rewards, or token distributions may be directed to this entity, its equityholders, contributors, or other participants. If no such mechanism currently exists, state that explicitly. Do not discuss hypothetical future dividends, repurchases, or distributions unless formally adopted.
(a) Entity
The Primary DevCo is Hadamard Gate Incorporated, doing business as PostQuant Labs, a Delaware corporation organized under the Delaware General Corporation Law (Action of Incorporator dated December 14, 2024). Its initial board of directors consists of three members: Richard T. Carback III, Colton Dillion, and Darwin Lo. PostQuant Labs is the current developer and deployer of the Quip Network protocol.
(b) IP ownership & control
PostQuant Labs currently owns and controls all IP related to the Quip Network, including code, repositories, trademarks, and brand assets. PostQuant Labs will retain ownership of this IP until the Quip Foundation and the DAO exist; at that point, the IP will be transferred or licensed to those entities. It is the intention of PostQuant Labs to grant unlimited licenses to the DAO and the Foundation.
(c) Powers over DAO, treasury, protocol-controlled resources, and token administration
No DAO or Foundation currently exists. Until they exist, PostQuant Labs, as the current deployer and multisig owner of the protocol contracts, holds administrative control over the testnet protocol, but the mainnet protocol, treasury, and token administration will be under the sole control of the Foundation; this control of the testnet protocol will transfer to the Foundation and the DAO once those entities exist. PostQuant Labs and its members are allocated 15% of the token supply (the Deployers allocation of 150,000,000 QUIP, subject to an 18-month cliff followed by 18 months of monthly vesting). Once governance is live, PostQuant Labs and its members may vote those tokens individually or collectively, on the same terms as any other tokenholder.
PostQuant Labs’ administrative control of the testnet relies on four validators operated by Postquant Labs and a series of 3/4 multisigs owning contracts on other chains.
PostQuant Labs currently has no powers over treasury actions or protocol-controlled resources such as revenue. PostQuant Labs currently has no powers over token administration or reward parameters. Postquant Labs has no unique applicable power over DAO governance, treasury actions, protocol-controlled resources, token administration, and reward parameters.
(d) Powers over Foundation
The Quip Foundation does not yet exist. Once formed, PostQuant Labs will have no power to direct or control the decision-making of the Foundation. The relationship between the Foundation and PostQuant Labs will be governed by an arm's-length agreement, under which the Foundation contracts with PostQuant Labs on an at-will basis.
(e) Contract/admin powers
PostQuant Labs, as the primary DevCo, is the current deployer of the protocol contracts and the owner of the multisig that administers them; the multisig signer threshold is 3/4. Per the Quip whitepaper (Section 12.1), the protocol administrator role controls only fees, and the signature verifier is a non-upgradeable contract pinned as an immutable, so no party can upgrade it. User accounts are upgradeable only with the explicit consent of the account holder. Runtime upgrades use Substrate's forkless on-chain upgrade mechanism, and subnet specifications are upgraded through governance rather than edited in place. Contract administration and multisig control will be transferred to the Quip Foundation and the DAO once those entities exist.
The DevCo has no pause authority, and no unique control over runtime upgrades, governance-executor authority, or subnet specification upgrades through governance beyond the standard rights granted to token holders.
(f) Current economic arrangements and distribution policies
Current programmatic economic arrangements include the following: when all pre-mine allocations finish vesting, 1,000,000,000 QUIP will have been emitted; the first billion is allocated 40% to subnet emissions, 20% to the public and foundation premine, 15% to early investors, 15% to builders, and 10% to community programs. Subnet emissions enter circulation continuously from launch, while allocations for early investors and other team-aligned participants follow a cliff and linear vest. The first billion is not a maximum supply; after the pre-mine has fully vested, subnet emissions continue at 40,000,000 QUIP per year, regardless of token price, network activity, or number of subnets. The Quip Control Asset routes emissions among subnets each epoch; each subnet’s share equals its share of all control weight cast, with an equal split if no one votes. Protocol fees are used to buy QUIP and place it in permanent, protocol-owned 50/50 liquidity positions, and the treasury policy has no burn. The treasury receives a share and converts that share into permanent liquidity. Application developers earn resale margins and a share of the builder allocation; algorithm developers receive royalties on solver invocations; protocol developers receive a share of fees from solved blocks and proofs; compute providers and miners earn block rewards and job fees; validators earn network fees plus emissions; nominators share validator yield and slashing risk; and liquidity providers earn fees and emissions on supplied liquidity. On order resolution, the order divides the reward among the winning solver or solvers, the builder whose specification was used, and the treasury.
The DevCo and its equity holders participate in this economic arrangement to the extent they are miners, validators, stakers, and smart contract deployers on equal footing with other network participants. In addition, PostQuant Labs and its members receive the Deployers allocation of 150,000,000 QUIP (15%), with an 18-month cliff and 18 months of monthly vesting. The protocol developer share of fees from solved blocks and proofs will be paid to a DAO-controlled wallet, and a developer committee elected by the DAO will direct those funds. PostQuant Labs does not receive this share directly; it may receive funds from this allocation only as determined by the DAO.
Token Supply & Allocations
Initial Allocation
Ticker | Date | Allocation Category Name | Recipient Type | Allocation % | Allocation Tokens | TGE Unlock % | TGE Unlock Tokens | Cliff Months | Cliff Unlock % | Linear Vesting Months | Cadence Months | Circulating Treatment | Notes on what each category is used for | If applicable: Contract / Wallet address |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
QUIP | 2026-10-29 | Miners & Ecosystem | Emissions | 0.4 | 400000000 | 0 | 0 | 0 | 0 | 120 | 1 | No | Block-reward emissions to miners, validators, developers and ecosystem partners for useful work; released with every block (target one block per 20 minutes) at 40,000,000 QUIP per year and enter circulating supply continuously from launch as freely transferable block rewards. Per the Quip whitepaper (Sections 5.3, 5.4 and 6.1), most of each block reward goes to the winning miner, with a royalty to the invoked solver's algorithm developer, a share to the treasury and a share of fees to protocol developers; the whitepaper does not set fixed percentages for these shares and does not define a separate ecosystem or grants pool within emissions. The treasury share is converted into protocol-owned liquidity and the protocol developer share is paid to a DAO-controlled wallet, so those portions enter circulation only through treasury or DAO action. Emissions continue in perpetuity after the first billion, so there is no max supply. Source: Quip Network token allocation worksheet (Oct 2026); percentages are of the first 1,000,000,000 QUIP. | |
QUIP | 2026-10-29 | Funders | Private / VC | 0.15 | 150000000 | 0 | 0 | 12 | 0 | 12 | 1 | No | Allocation to funders of initial development (SAFE + token warrant holders). Token warrants recorded on the cap table total 10.79% of supply; the remaining 4.21% (42,100,000 QUIP) is unallocated and will escheat to the DAO for future sale under the same lockup terms. 12-month cliff from TGE, then monthly vesting over 12 months. Source: Quip Network token allocation worksheet (Oct 2026); percentages are of the first 1,000,000,000 QUIP. | |
QUIP | 2026-10-29 | Deployers | Insiders | 0.15 | 150000000 | 0 | 0 | 18 | 0 | 18 | 1 | No | Allocation to protocol deployers (PostQuant Labs and its members). 18-month cliff from TGE, then monthly vesting over 18 months. Source: Quip Network token allocation worksheet (Oct 2026); percentages are of the first 1,000,000,000 QUIP. | |
QUIP | 2026-10-29 | Community | Community | 0.1 | 100000000 | 0.05 | 5000000 | 0 | 0 | 120 | 1 | Conditional | Airdrops to users of the protocol, including Quip Points participants. 5% at TGE, then monthly over 120 months; user airdrops are conditional on network revenue performance (emitting based on the proportion of miner, validator and staker revenue from emissions versus usage fees) and require distribution to recipients. The 120-month schedule is the expected pace, not a fixed maximum or minimum. The DAO may elect a committee or grant control of this budget to an existing committee, and any tokens not released by the end of the 10 years remain under that committee's control. Source: Quip Network token allocation worksheet (Oct 2026); percentages are of the first 1,000,000,000 QUIP. | |
QUIP | 2026-10-29 | Foundation | Treasury | 0.15 | 150000000 | 0.666666666666667 | 100000000 | 12 | 0 | 108 | 1 | Conditional | Allocation to the Quip Foundation for promoting and operating the protocol. 100,000,000 QUIP (two thirds) unlocked at TGE, remainder vests monthly over 108 months after a 12-month cliff; enters circulation only through Foundation spend. The Foundation is not yet formed. Source: Quip Network token allocation worksheet (Oct 2026); percentages are of the first 1,000,000,000 QUIP. | |
QUIP | 2026-10-29 | Market Makers | Market Structure | 0.015 | 15000000 | 1 | 15000000 | 0 | 0 | 0 | 0 | Conditional | Allocation to market makers to facilitate liquidity at centralized and decentralized venues. 100% unlocked at TGE; enters circulation only on market-maker deployment. Market-maker agreements are under negotiation and no tokens have been loaned or allocated yet. Source: Quip Network token allocation worksheet (Oct 2026); percentages are of the first 1,000,000,000 QUIP. | |
QUIP | 2026-10-29 | Launch Distribution | Market Structure | 0.035 | 35000000 | 0.5 | 17500000 | 6 | 0.5 | 0 | 0 | Conditional | Tokens made available for launch activations at participating venues. 50% at TGE and the remaining 50% at a 6-month cliff; enters circulation only when distributed through venue activations. Exchange agreements are under negotiation. Source: Quip Network token allocation worksheet (Oct 2026); percentages are of the first 1,000,000,000 QUIP. |
Airdrop Process
State the project's airdrop status plainly, and back it up:
- Never conducted and none planned for TGE: state so plainly.
- Planned but not yet executed: state the target user segments (e.g., "stakers of X," "Aave users") and the allocation method (e.g., proportional to balance or net position), and commit to publishing a recipient wallet list in a public channel and providing it to Blockworks quarterly until the initial TGE airdrop is fully completed.
- Already executed: state the covered user segments and the allocation method, and point to a per-address source such as CSV/TSV/JSON files, a Dune table, a full Merkle dump, GitHub repo files embedding per-address allocations, or RPC endpoints that expose claim/amount data; explorer links alone do not count.
Status: an airdrop is planned but has not yet been executed. Target user segments: participants in the Quip Points program who contributed to the testing, development, and marketing of the Quip Network. Allocation method: airdropped tokens come from the Community allocation (100,000,000 QUIP, 10% of the first billion QUIP) and are allocated to eligible participants based on the Quip Points they earned. 5% of the Community allocation is released at TGE, with the remainder released over 120 months; user airdrops are conditional on the revenue performance of the network, emitting based on the proportion of miner, validator, and staker revenue earned from protocol emissions versus usage fees. The project commits to publishing the recipient wallet list in a public channel and to providing it to Blockworks quarterly until the initial TGE airdrop is fully completed.
Transactions & Market Structures
Market Maker Agreements & Deals
Projects must disclose all material terms of market-making arrangements that affect token liquidity. If the project has no agreements or deals with market makers, state that explicitly. For each market maker, include in a table:
- (a) Market maker's name — the market maker's name;
- (b) Token allocation or loaned amount — the token allocation or loaned amount as a percentage of total supply;
- (c) Duration/term of agreement — the duration/term of the agreement; and, where applicable,
- (d) Name of agreement structure — label the financial vehicle being used in the agreement (i.e. loan, option/call, retainer model).
If no native tokens were loaned or allocated to market makers, state that explicitly; cash/fiat retainers or fees are not required for (b).
Market Maker Name | Token Allocation Committed | Term Duration | Structure Name |
|---|---|---|---|
No market maker agreements have been executed. Market-making arrangements are currently under negotiation. | No native tokens have been loaned or allocated to market makers to date. The token allocation reserves 15,000,000 QUIP (1.5% of the first billion QUIP) for market makers to facilitate liquidity at centralized and decentralized venues, 100% unlocked at TGE. | Not applicable; terms under negotiation. | Not applicable; structure under negotiation. |
Exchange Agreements & Deals
Projects must disclose all material terms of centralized or decentralized exchange listings that affect token liquidity. For each listing, include in a table:
- (a) Exchange name / DEX pool — the exchange name (and, for DEX, the specific pool/pair);
- (b) Token allocation for listing — the token allocation supplied or committed for listing as a percentage of total supply;
- (c) Term Duration — the duration/term of any listing lockups, liquidity, or incentive programs; and, where applicable,
- (d) Native-token listing fees — whether any listing fees were paid in native tokens, with amounts (tokens or % of supply), recipients, and any vesting or lock terms tied to the partnership.
If the project has no agreements or deals with CEX or DEX, state that explicitly; doing so earns full credit; cash/fiat fee amounts are not required for this item.
Exchange Name | Token Allocation Committed | Term Duration | Native Token Listing Fees |
|---|---|---|---|
QuipSwap (the protocol's own DEX): protocol-owned 50/50 QUIP liquidity positions against USDC. No QUIP pool/pair exists yet because QUIP has not been issued. | 0% of total supply supplied or committed to date. No QUIP has been allocated to QuipSwap pools; protocol-owned liquidity is funded over time by protocol fees used to buy QUIP, and the treasury's first positions will be seeded during Genesis from treasury funds. | Permanent protocol-owned liquidity positions; no lockup or incentive program term applies. | None. QuipSwap is the protocol's own DEX, and no listing fees have been paid in native tokens. Swap fees from QuipSwap accrue to the treasury and fund the permanent liquidity positions. |
Centralized and decentralized exchanges (other than QuipSwap): as of this filing, no CEX or DEX listing agreements or deals exist. Listing discussions with exchanges are currently under negotiation; terms will be disclosed once any agreement is executed, not to exceed 3.5% of total supply. | No tokens have been supplied or committed to any exchange to date. The token allocation reserves 35,000,000 QUIP (3.5% of the first billion QUIP) as a Launch Distribution for launch activations at participating venues, with 50% unlocked at TGE and the remainder after a 6-month cliff. | Not applicable; terms under negotiation. | No listing fees have been paid in native tokens to date. |
Financial Disclosures & Risks
Prior Token Sales & Fundraising
Disclose all prior token sales by the Project — including fundraising rounds, any material OTC sales to investors, and any discounted market-maker sales. For each sale, provide:
- (a) Series Name;
- (b) Early-Stage Investment Instrument used (i.e. SAFT, STAMP, SAFE, SAFE+Token Warrant, etc.);
- (c) Date of sale (at least month & year);
- (d) Number of tokens sold (or % of total supply);
- (e) Vesting schedule.
If no prior sales occurred, state that explicitly (e.g., "No prior fundraising, OTC, or discounted MM sales have occurred.").
Series Name | Investment Instrument | Date Of Sale | Number of tokens sold | Vesting Schedule |
|---|---|---|---|---|
SAFE round | SAFE + Token Warrant | December 2024 | Token warrants for 4.16% of the first billion QUIP; $420,000 invested | Funders allocation: 12-month cliff from TGE, then released monthly over 12 months |
SAFE round | SAFE + Token Warrant | April 2025 | Token warrants for 0.10% of the first billion QUIP; $30,000 invested | Funders allocation: 12-month cliff from TGE, then released monthly over 12 months |
SAFE round | SAFE + Token Warrant | April 2025 | Token warrants for 0.10% of the first billion QUIP; $40,000 invested | Funders allocation: 12-month cliff from TGE, then released monthly over 12 months |
SAFE round | SAFE + Token Warrant | April 2025 | Token warrants for 0.05% of the first billion QUIP; $25,000 invested | Funders allocation: 12-month cliff from TGE, then released monthly over 12 months |
SAFE round | SAFE + Token Warrant | February 2026 | Token warrants for 0.78% of the first billion QUIP; $390,000 invested | Funders allocation: 12-month cliff from TGE, then released monthly over 12 months |
SAFE round | SAFE + Token Warrant | February 2026 | Token warrants for 2.20% of the first billion QUIP; $1,100,000 invested | Funders allocation: 12-month cliff from TGE, then released monthly over 12 months |
SAFE round | SAFE + Token Warrant | February 2026 | Token warrants for 3.40% of the first billion QUIP; $1,700,000 invested | Funders allocation: 12-month cliff from TGE, then released monthly over 12 months |
Previous Exploits Affecting The Native Token
If any, list prior exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply. This question is not asking about general protocol, application, or smart contract exploits unless the incident directly affected the native token itself. If no prior incidents, state this explicitly (e.g., "No exploits affecting tokenholders or protocol funds as of YYYY-MM-DD").
- (a) Date & component affected — Date (YYYY-MM or YYYY-MM-DD), chain(s)/component affected.
- (b) Exploit vector summary — Plain-language summary of the exploit vector (what the hack was).
- (c) Quantified impact — Quantified impact (assets/tokens affected or a clear "no loss of funds" statement).
- (d) Remediation/response taken — Remediation/response taken (patches, upgrades, governance actions, compensation).
- (e) Current status — Current status (resolved, in litigation, under investigation, refunded, etc.).
- (f) References — Link(s) to post-mortem/advisory/PR.
(a) Date & component affected
No prior exploits or incidents affecting the native token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply as of 2026-10-23.
(b) Exploit vector summary
There have been no prior incidents directly affecting the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply as of a specific 2026-10-23 date
(c) Quantified impact
The quantified impact from prior token-related exploits or incidents is zero US dollars or asset equivalents. There has been no loss of funds and no prior incidents as of 2026-10-23.
(d) Remediation/response taken
There has been no remediation or response taken for any prior token-related incident as there have been no prior token-related incidents as of 2026-10-23.
(e) Current status
No exploits affecting tokenholders or protocol funds as of 2026-10-23.
(f) References
No post-mortem, advisory, or pull-request references for prior token-related incidents are disclosed in this filing.
Material Risk Factors (Regulation, Technology, Token Economics)
Describe material risk factors across the three categories below. Each category includes prompts to address at a minimum.
-
(a) Regulatory, Legal & Tax Risks — Describe how evolving laws and regulations could affect the project by answering, at a minimum, questions like:
-
Impact of Regulatory Change on TGE and Listings: (If applicable) How could evolving or conflicting laws and regulations affect your ability to complete the TGE, deliver tokens to purchasers, and list or maintain the token on trading venues in key jurisdictions?
-
Entity-Level Regulatory Impact: (If applicable) How could regulatory or legal changes impact your core entities (Foundation, DevCo, DAO, affiliated service providers), including enforcement actions, licensing requirements, or forced changes to structure or operations?
-
Tokenholder Tax Treatment: (If applicable) What uncertainties exist around how tokenholders may be taxed, and make clear that tokenholders are responsible for understanding their own tax obligations?
-
Jurisdictional & User Access Restrictions: (If applicable) If the project restricts access for certain jurisdictions or user types (e.g., U.S. persons, sanctioned countries, retail vs. professional), what are those restrictions and what risks do they create for users and for the project?
-
(b) Protocol, Technology & Security Risks — Describe risks to network and contract reliability, correctness, and safety by answering, at a minimum, questions like:
-
Bugs and Design Flaws: (If applicable) What bugs, design flaws, or implementation errors could exist in your core protocol code, smart contracts, and any bridges, rollups, or oracles that you depend on, and how could these lead to loss of funds or disruption of the protocol?
-
Security Measures & Their Limitations: (If applicable) What security measures have you taken (audits, formal verification, bug bounties), and what types of failures might these measures still fail to detect or prevent?
-
(c) Token Economics, Unlocks & Incentive Risks — Describe how the token's economic design and supply schedule could affect holders by answering, at a minimum, questions like:
-
Critical Economic Assumptions: (If applicable) Which economic assumptions (e.g., staking yields, fee revenue, liquidity incentives, MEV capture, demand for blockspace) are critical for protocol security, utility, and governance, and what happens if those assumptions fail?
-
Governance Control over Monetary Policy & Rewards: (If applicable) To what extent can governance change monetary policy, fee parameters, or reward allocations (e.g., inflation rate, treasury flows, incentive programs), and how could such changes adversely affect tokenholders?
(a) Regulatory, Legal & Tax Risks
Regulatory, legal, and access-control risk is material because the network routes work based on jurisdiction and compliance attributes. Operator registration records each operator’s jurisdiction and binding regulatory constraints, and the matching layer treats those items as routing predicates; sensitive problem classes, including cryptanalysis subnets and classified or dual-use workloads, are gated against export controls using zero-knowledge proof of identity and program provenance. The network also applies sanctions rules to both sides of a match before offering an order, and dispatch is designed so an operator does not receive a job it cannot lawfully run. As a result, changes in sanctions rules, export controls, jurisdictional eligibility, or other binding regulatory constraints could reduce the set of eligible operators, consumers, workloads, or routes available on the network.
User access may also depend on compliance credentials and operator-specific terms. A zero-knowledge identity credential carries the compliance facts needed for routing; when an operator or problem class requires verification, the credential attests the consumer’s identity and acceptance of the operator’s terms while revealing only the predicate required by the policy. Completing KYC or KYB gives a consumer access to more operators and jurisdictions, and consumers with confidentiality, jurisdiction, or quality requirements can request work only from operators they have vetted. These restrictions may limit access for users that cannot or do not complete required checks, and may create execution risk if a job cannot be matched to an eligible operator.
The network’s most sensitive planned workloads create additional legal and policy risk. The cryptanalysis subnet can break cryptography that protects active financial and communications infrastructure, and export-control and dual-use gates dispatch that work only to operators in jurisdictions where the work is permitted and to operators willing to permit such use. Results follow a coordinated disclosure process instead of unrestricted publication.
Entity-level operational risk is concentrated during the early phases. During Genesis and the early phases, the Quip Foundation reviews every subnet proposal and deploys subnet infrastructure only after checking market demand, technical feasibility, available hardware partnerships, and resource requirements. During Genesis, operator entry is permissioned through hardware attestation and KYB where applicable, and the Foundation gates Genesis. The design later moves toward permissionless operator entry and permissionless subnet proposals after activation thresholds are met, with permissionless subnets and the Control Asset taking over emission routing after the mechanism proves itself.
Export-control risk also applies to the project's core technologies. Both quantum computing and cryptography are regulated in the United States under the International Traffic in Arms Regulations (ITAR) and the Export Administration Regulations (EAR), which treat certain cryptography and compute items as arms or controlled dual-use items. Changes in how these regimes classify or restrict quantum compute, cryptographic software, or related technical data could limit which operators, consumers, jurisdictions, and workloads the network can serve, require licenses or additional compliance controls, or restrict the distribution of software, technical data, or services by the project's entities.
(b) Protocol, Technology & Security Risks
Protocol, technology, and security risks include the following:
- The Sinnet is a sovereign Substrate layer-one whose runtime includes a useful-work mining pallet, a compute-job mempool for the spot market of bids and solutions, an on-chain XQVM execution pallet, and the Interlock protocol for cross-chain compute payments. Defects in those components could affect proof scoring and rewards, job routing, VM execution, or cross-chain payment settlement.
- The XQVM is designed to support attestation, reject malformed bytecode at the submission boundary, emit execution traces, and independently recompute claimed energy exactly, including on-chain where required. These controls reduce reliance on operator trust, but they depend on correct implementation of the static verifier, bytecode validation, trace generation, and energy recomputation.
- The Interlock uses hash locks and a reclaim path. EasyCrypt state-separating proofs are used for formal verification, and passive safety and fairness are proven, but the full active-adversary proof remains open. A hash lock cannot prove without spoofing that a counterparty committed and then abandoned a swap, and the protocol cannot slash a party that grief-locks funds in a denial-of-service attack. The current Interlock uses hash locks and leaves adaptor-based slashing to future work; no well-studied post-quantum construction for verifiably encrypted signatures or adaptor signatures exists today.
- Quip obtains bridgeless, custodian-free cross-chain payments by waiting for the most conservative counterparty network rather than using a permissioned validator set to shorten the wait. DAG-based optimistic transfers add latency, can finalize only when the slowest participating chain reaches finality, and remain exposed to reversal until the last leg’s timelock can no longer be contested.
- The asset surface depends on SHRINCS account key management. A stateful leaf must sign exactly once, and enforcement uses an on-chain leaf bitmap and lifetime spent-tree registries. Accounts rotate to a fresh tree before the budget is exhausted. The dedicated message-verification key is client-bounded, which makes client-side key tracking a continuing operational risk.
- Sinnet accounts and transactions use hybrid signatures combining a classical scheme with FN-DSA-512; the hybrid signature remains unforgeable while either component remains secure. This design addresses the risk that Quip’s quantum miners could eventually forge a single classical scheme and the risk that an unforeseen weakness in young post-quantum cryptography should not compromise the chain by itself. For repeated consensus signing, signatures are derived deterministically from the message and chain state and cached to prevent differential-fault attacks that affect naive randomized signing. A stock FN-DSA implementation has shown side-channel and fault weaknesses in long-lived, co-resident signers, so Quip admits only the deterministic, constant-time signing profile.
- Tier-two and tier-three validation introduce non-cryptographic correctness risks. Tier-two claims use reproducible benchmarks, and tier-three claims use oracle and prediction-market adjudication. Operators may collude on false benchmark reports, oracles may accept bribes or make errors, and a miner may game a naive quality threshold with low-diversity or pre-computed solutions. Surprisal markets add manipulation risk if an actor with private knowledge moves a market’s probability before resolution, inflating the reward multiplier.
- Mitigations for benchmark, oracle, and market failures include verifier and oracle collateral subject to slashing if a community appeal overturns a decision, random re-checks of accepted results by independent operators, quality scoring that rewards solution diversity and low latency, a Foundation-operated oracle for simple objective claims before moving toward reputation-weighted community oracles, cryptographic verification by default, human judgment for novel claims, and an insurance fund for oracle errors.
- Reorganization risk is distinct because the operators whose useful work secures the chain may eventually own enough hardware to build an alternative history faster than the honest majority. The Sinnet chooses the chain with the most total useful work, and heaviest-observed-subtree and uncle-block construction make work add weight even when it does not extend the main chain. During bootstrap, GRANDPA provides validator-voted finality, and under the honest-validator assumption a finalized block cannot be reorganized. Deep-reorganization resistance still requires honest operators to control a majority of total useful work, an honest validator supermajority to participate in finality, and validators to keep an honest local view of recent commitments.
- Concentration risk remains. Superconducting systems cost tens of millions, few operators own frontier QPUs, Stage 3 entanglement requires mining pools, and mining pools concentrate capacity by design. Mitigations include competition among CPUs, GPUs, ASICs, and QPUs, topology-aware difficulty adjustments, Control Asset identity binding with per-identity limits and quadratic decay, and a single-miner alert above approximately 75% of a subnet’s work.
- Privacy and confidentiality features for the quantum kernel remain incomplete. Future iterations will support blind quantum computation, but these methods are information-theoretically secure in principle and have only small experimental demonstrations; the document treats them as aspirational future work.
(c) Token Economics, Unlocks & Incentive Risks
QUIP is the network’s native token and shared unit of compute credit. The initial one billion QUIP is allocated 40% to subnet emissions, 20% to the public and foundation premine, 15% to early investors or insiders, 15% to builders, and 10% to community programs; early-investor and other team-aligned allocations follow a cliff and linear vest. The first billion is not a maximum supply. After premine vesting, subnet emissions continue at a fixed, flat rate of 40,000,000 QUIP per year, regardless of token price, network activity, or the number of subnets. As more subnets are added, that fixed annual emission is divided among more recipients, so issuance per subnet and QUIP emitted per unit of compute decline through “implicit decay.” Tokenholders therefore bear ongoing emission and allocation risk: the economic value of any subnet, miner, builder, or governance position depends on whether the network attracts enough useful compute demand for the fixed emission schedule and expanding subnet set.
Critical economic assumptions include sustained demand for compute, sufficient liquidity between local currencies and QUIP, enough fee revenue for protocol-owned liquidity, and operator willingness to accept QUIP-denominated rewards while paying fiat capital and operating expenses. Consumers may fund accounts with fiat or stablecoins and see bids and bills in credits, while the network settles in QUIP; application developers typically hold QUIP, handle conversion, bill customers in local currency, and keep a working QUIP balance. Protocol fees are used to buy QUIP and place it in permanent 50/50 liquidity positions, and fees from completed swaps fund those positions. If job demand, fees, or liquidity are insufficient, the buyback-into-liquidity mechanism has less revenue to deploy, operators face a sharper mismatch between fiat costs and QUIP rewards, and operators may enter only when expected rewards rise or leave when competition or lower rewards push expected returns below operating cost. Because rewards and consensus weight come from useful compute rather than node count, and because miners solve proofs of useful work and earn block rewards and job fees, reduced operator participation or weak economic demand can adversely affect the network’s useful-work security and utility.
Governance primarily controls reward allocation rather than a disclosed ability to change the fixed annual emission rate. The Quip Control Asset, implemented as veQUIP, routes emissions among subnets each epoch. Holders lock QUIP in Interlock-enforced escrow to gain time-weighted control weight; longer locks grant more weight, voting weight decreases as the lock approaches expiry, and each epoch converts control weight into proportional emission. If no one votes, subnets split emission equally. Governance also registers new subnets, moves proposals from Foundation review to permissionless entry after activation thresholds, and retires under-performing subnets. These powers can materially change which problem classes, miners, builders, and operators receive rewards.
The emission-routing market also creates governance and incentive risks. Quip makes vote-buying an explicit, permissionless bribe market: a subnet or backer deposits QUIP for a specified subnet and epoch, and veQUIP voters who supported that subnet claim the deposit in proportion to their votes. This turns emission routing into a transparent auction and can move emissions toward work that pays most to attract funding, but it also creates risks that well-funded subnet backers influence reward allocation, that bribe prices rather than long-term protocol value drive voting, and that emission moves away from economically important but less-funded work. The design includes time locks, identity-bound limits, provisional quadratic decay, provisional concentration caps, and cartel monitoring, but those controls are themselves provisional in important respects.
The treasury policy also affects holders. Protocol fees buy back QUIP into permanent 50/50 liquidity positions, and the disclosed treasury policy has no burn. This can add market depth, lower trading costs, and increase the treasury’s share of pool fees, but holders do not receive a burn-based reduction in supply from treasury fee use. Miner sales and put options are intended to help hardware partners manage the mismatch between fiat expenses and QUIP rewards, but these mechanisms also make operator economics dependent on treasury capital, guaranteed-price arrangements, and future reward claims.
This Token Transparency Filing is provided for general informational purposes only. Blockworks reviews completeness only and does not verify or warrant the accuracy of individual answers. Quip Network is solely responsible for the content, accuracy, and legality of its disclosures.