Summary: Confetti is best understood not as a generic polling app or grants form, but as an onchain contest market where communities turn subjective choices into priced participation. Each contest is its own smart contract; voters buy votes on a time-rising price curve; 90% of vote spend flows into a rewards pool; and only voters on winning entries can claim a proportional share of that pool. The reusable mechanism insight is that Confetti packages decision-making, attention-routing, reputation signaling, and incentive funding into one contest primitive, then exposes the resulting state as permissionless onchain data for extensions, analytics, role assignment, points systems, and downstream execution.
What it does:
Lets creators launch contests where entrants submit entries and voters buy votes on their preferred submissions
Routes 90% of voting fees into a rewards pool and pays that pool out to voters on winning entries according to configurable placement splits
Uses rising price curves so early votes are cheaper and potentially more profitable, explicitly rewarding early conviction rather than late consensus-following
Treats each contest as its own smart contract and exposes contest, submission, voting, and rewards data directly onchain rather than through a proprietary API
Supports allowlists for submitters and voters, creator-defined fields on submissions, and extension hooks that let third parties build analytics, reward, reputation, or execution layers on top
Positions contests as reusable infrastructure for demo days, hackathons, grants, feature prioritization, community awards, memes, and other collective decisions
Key claims:
The official FAQ makes the core mechanism unusually explicit: a contest is a market where people buy votes, 90% of those funds go to a rewards pool, and winning voters split that pool. That means Confetti is closer to a persuasion market or attention auction than to ordinary governance polling.
The price-curve design is the main analytical reason to catalog the project. By making votes more expensive each minute, Confetti tries to reward early conviction, increase strategic play, and bootstrap a liquidity flywheel in which early participation seeds larger rewards that attract later participants.
The docs repeatedly stress that Confetti is fully onchain and has no API because the chain itself is the API. That matters because it pushes downstream power into indexers, dashboards, extensions, and smart-contract integrations rather than a centralized application backend.
The extension docs show Confetti aiming to become a decision layer rather than only a contest front end. Existing examples include Hats-based role assignment, analytics, NFT rewards, and points allocation, while the suggested future uses include multisig membership, capital deployment, node-operator slashing, and AI-agent action approval.
The “fields” mechanism in the FAQ is especially important because it turns submissions into structured metadata that other contracts can parse permissionlessly. This creates a bridge from subjective contests into executable funding, attestation, and access-control logic.
The manual tie-handling and creator withdrawal rules reveal the remaining control surfaces. Creators can withdraw seeded rewards until the first vote is cast, and ties route affected rewards back to the creator for manual distribution, so some dispute resolution and payout discretion still sit with the organizer.
The official docs and repos are also useful evidence of a live branding transition: the current product brand is Confetti, while the docs repository and some ecosystem references still use the older Jokerace naming. That makes the project a good reminder to track mechanism continuity across rebrands instead of indexing only brand labels.
Confetti is a strong comparison class for Prop House, grants contests, hackathon judging, and reputation systems because it compresses proposal intake, community signaling, rewards, and extension-ready execution into one reusable contest primitive.
Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest primary materials were the official docs pages and official repositories collected in ../whitepapers/confetti-primary-sources-2026-05-10.md.