Funding advances through explicit cycles and stages rather than a single opaque pool.
SWAGBALL PROTOCOL
Funding becomes a sequence, not a black box.
SwagBall organizes project funding into visible on-chain cycles. Participation is recorded, cycle outcomes are auditable, and each supported network can present the same core sequence through its own token, contracts, and live state.
Participation can produce on-chain records tied to the cycle in which it occurred.
Cycle completion, selection, ownership, and claims can be inspected from public state.
HOW IT WORKS
One idea. Four moments.
SwagBall turns funding into a visible sequence of on-chain events, from opening a cycle through selecting and recording its outcome.
A cycle opens
Each funding cycle defines a target, contribution rules, and completion conditions.
People participate
Participants contribute the active network token while funding capacity remains available in the current cycle.
The cycle completes
There is no countdown by default. The cycle stays open until its funding capacity is filled, and that completion is the duration.
The record remains
When funding is complete, one participating wallet from that cycle is selected, and the resulting artifacts, ownership, provenance, and claims form a durable history.
WINNER SELECTION
Funding capacity is not an odds multiplier.
Most people naturally think in raffle tickets: contribute more, get more chances. SwagBall’s current design is intentionally different. This is a race to occupy funding capacity before more wallets can enter — not a race to buy extra chances.
1 participating address
=
1 selection position
Contributing more Token increases how much of the current cycle’s fixed funding capacity that wallet occupies. It does not create more selection positions for that wallet. More Token means less remaining room for other wallets.
01 FIRST CONTRIBUTION→02 WALLET JOINS CURRENT CYCLE→03 CAPACITY SHRINKS FOR OTHERS→04 RANDOM SELECTION
The first contribution places the wallet in that cycle’s participant set. Later contributions from that same wallet affect funded amount and available capacity, but not the number of chances for that wallet inside the same cycle. The only way shared odds change is by changing how many wallets fit into the cycle before it closes.
COMMON MISUNDERSTANDING
More Token ≠ more tickets
That raffle-style assumption does not apply here. This system does not multiply chances by contribution size.
SWAGBALL RULE
More Token = less room for others
The wallet still counts once in the current cycle’s selection set, but it can reduce how many additional wallets fit before the cycle closes.
EXAMPLE · SAME CURRENT CYCLE
Different contribution amounts. Equal per-address selection weight.
WALLET A0.001 Token
WALLET B10% of cycle target
WALLET C20% of cycle target
IF THESE ARE THE ONLY 3 PARTICIPATING WALLETS IN THE CURRENT CYCLEA = 33.33% · B = 33.33% · C = 33.33%
NO TIME LIMIT BY DEFAULT
The funding capacity is the duration.
A cycle can complete in seconds or in weeks depending on participation. It remains open until its current funding capacity is filled. When that funding cycle completes, one winner is chosen from all participating wallets in that current cycle. That completion is the windfall moment.
It reduces the remaining funding opportunity for other wallets. Fewer wallets fitting into the cycle is the only way shared odds become less crowded.
If participants contribute below their cap, more wallets can fit into the cycle before it closes. That increases participation and spreads the odds across more wallets.
In the current live configuration, each address can occupy up to 20% of target. Six fully capped addresses are the mathematical minimum needed to fill a 120% cycle, but the protocol does not assume those addresses belong to six different people.
Strategic implication: each participating address has the same selection weight regardless of how much that address contributed. Larger contributions matter by consuming capacity, not by buying extra entries.
ADDRESS ≠ PERSON
SwagBall does not ban multiple wallets. The reward punishes concentration when those wallets consume capacity.
The protocol deliberately counts addresses, not human identities. A separate participating address is a separate selection position. The 20% cap is therefore not a proof-of-personhood rule; it is a concentration rule. When one controller uses several addresses to occupy more of the cycle, that controller puts more capital at risk for the same cycle-target payout.
If one participant controls four addresses at the full 20% cap and two other full-cap addresses complete the cycle, the controller funds 80% of target and holds 4/6 of the selection positions. A winning controlled address can redeem up to the 100% target reserve, producing a maximum +20% of target relative to that controller’s 80% contribution. Each outside address risked 20% of target for the possibility of receiving the same target-sized reserve.
If one controller fills all six full-cap positions, that controller funds the entire 120% cycle and guarantees that one controlled address wins. But the WinnerNFT reserve is still only 100% of target. Full redemption returns at most the target reserve, leaving a guaranteed 20% of target net funding cost before gas or other costs.
The intended tradeoff: SwagBall does not try to police how many wallets a person owns. It makes heavy concentration less reward-efficient when those wallets are used to consume funding capacity. More controlled positions can mean more probability, but also more capital exposed to the same fixed target-sized winner reserve.
Current Fuji limitation: any positive accepted contribution creates one address entry. That means low-value address splitting can still add selection positions without consuming a full 20% of capacity per address. The wallet cap is an economic concentration mechanism, not a complete Sybil defense. This remains a production-design consideration for mainnet.
YOU'RE DOING IT WRONG.
If the NFT stops at the picture — or the utility comes later — then you have an overcomplicated nothing thing.
This JPEG has a job on day one. SwagBall's live visual engine can produce 75 unique candidate artworks per second. That speed is not the utility. When a cycle completes, one live frame becomes the cycle artifact and the WinnerNFT is minted with its claim permission already active.
The WinnerNFT is the key to the safe. Before any partial claim, the key controls a protocol-defined claim right equal to that cycle's target reserve. No shilling required. The claim exists at mint; hype does not create it.
You can copy the pixels. You can't copy the permission.
THE PIXELSPUBLICScreenshot them. Share them. The artwork is not the lock.
≠
THE NFTTHE KEYCurrent ownership controls permission to the remaining cycle claim.
→
THE CONTRACTTHE SAFEFundingManager enforces the remaining reserve, approvals, transfer, and redemption.
75 / SECONDCandidate artworksUnique live visual states generated in real time.
1 / CYCLECommitted artifactThe completion-state frame becomes that cycle's WinnerNFT artwork.
AT MINTPermission is liveThe token already controls its cycle-specific claim right.
THE TARGETReserve behind the keyBefore any partial claim, the claim right can equal the full cycle target.
WINNERNFT · CURRENT AVALANCHE CLAIM MODEL
Ownership is permission.
The selected winner receives the key first. The utility is already present at mint: current WinnerNFT ownership controls the cycle's remaining claim right. Transfer the NFT and that permission moves with it.
Current WinnerNFT holder
=
Holds permission to the remaining cycle claim
When a wallet holding an unredeemed WinnerNFT connects to the network site, the interface can read the NFT owner, cycle target, amount already claimed, and full-claim state directly from the contracts. It can then present only the claim actions that are still available for that specific NFT.
01 WINNER SELECTEDWinnerNFT minted to selected wallet→
02 HOLD OR TRANSFEROwnership and remaining claim move together→
03 OPTIONAL 50% CLAIMTake partial liquidity and retain the NFT→
04 FULL REDEMPTIONTrade NFT to project wallet for remaining reserve
The cycle target remains the protocol’s claim reserve for that NFT, less anything already claimed. This is a redemption right, not a guarantee that the NFT’s secondary-market price equals the target.
The claim is checked against the NFT’s current owner, not only the original winner. If ownership changes, the new holder controls whatever claim balance remains.
The current holder can claim half of the cycle target without surrendering the WinnerNFT. The remaining half stays reserved for that same cycle and continues to follow the NFT.
The holder approves the FundingManager contract to transfer the WinnerNFT, then completes the full claim. The NFT moves to the project wallet and the holder receives the cycle’s remaining unclaimed reserve.
EXAMPLE · 10 AVAX CYCLE TARGET
The reserve is attached to the cycle. The right to claim it follows the NFT owner.
WINNERNFT MINTED10 AVAX target reserve
Holder owns NFT + claim right
↓
OPTIONAL PARTIAL CLAIM5 AVAX paid to holder
WinnerNFT stays with holder · 5 AVAX remains
↓
OPTIONAL TRANSFERNFT moves to another wallet
New owner now controls the remaining 5 AVAX claim
↓
FULL REDEMPTIONRemaining 5 AVAX paid
WinnerNFT moves to project wallet · claim closes
FULL REDEMPTION DOES NOT REQUIRE A PARTIAL CLAIM FIRST
If nothing has been claimed, the holder can approve and redeem the WinnerNFT for the full 10 AVAX target reserve in one full-claim transaction.
THE APPROVAL TARGET MATTERS
Approve the FundingManager, not the project wallet.
Open the current Avalanche Fuji experience
The FundingManager performs the atomic redemption: it transfers the NFT from the current holder to the project wallet and pays the holder the remaining cycle balance. Once fully redeemed, that cycle cannot be claimed again.
NO SHILLING REQUIRED.The safe is already funded.
The WinnerNFT does not need hype to manufacture a reason to exist. At mint, its current owner already controls a protocol-defined claim against funds reserved for that completed cycle. That claim is real contract utility from day one — not a promise that someone else will pay more for the NFT later. Secondary-market price is never guaranteed; the redemption right is defined by the protocol.
UTILITY COMING SOON?You're doing it wrong.
SwagBall does not mint a picture and promise future utility. The WinnerNFT's ownership permission and cycle-specific redemption right exist when the token is minted. The artwork is the public artifact; the token is the transferable key.
The NFT is the key. The contract is the safe. The original winning wallet does not permanently own the payout right. After minting, the contract checks who owns that cycle’s WinnerNFT when a claim is made. Transfer the key and you transfer the permission to control the unclaimed reserve.
NETWORKS
Choose where to participate.
Choose a supported blockchain network to view its live funding cycles, assets, and participation experience.
AAVALANCHE · COMING SOON
SwagBall on Avalanche
Avalanche mainnet is being prepared. The Fuji test environment is available now for public testing with test AVAX.
Mainnet coming soonTEST NETWORKFor public testing before mainnet
F
FujiAvalanche testnet · Test AVAX has no monetary value
+FUTURE NETWORKS
More networks can follow.
SwagBall is designed to extend to additional blockchain networks while keeping the same core funding-cycle experience.
Additional networks can be added over time.ARTIFACTS
Participation leaves something inspectable.
Artifacts are not used to explain the project; they are evidence that a specific interaction or outcome occurred.
SwagBall
PARTICIPATION VOUCHER
VOUCHER #100000CYCLE #1ORIGINAL PARTICIPANT
0x3F2a...9C4d
0x3F2a...9C4d
S
swagball.io/v/100000
PARTICIPATIONVOUCHER
Participation that can become governance weight.
A ParticipationVoucher is a deterministic on-chain record of participation. Unspent vouchers can second public petitions, and holders may later exchange them for binding voting weight by burning them: one voucher equals one unit of governance weight.
WINNERNFTCycle outcome + claim instrumentOn Avalanche, the remaining cycle claim follows the current NFT owner until full redemption.
WINNERNFT
This JPEG has a job.
Up to 75 unique candidate artworks can pass through the live generator each second; one cycle-closing frame becomes the artifact. The artwork is public. The permission is on-chain. The current owner controls the remaining cycle claim until full redemption.
PARTICIPATION GOVERNANCE
Participation can become a voice.
Governance is separate from FundingManager. Public petitions are qualified by ParticipationVoucher holders, while binding votes permanently exchange vouchers for voting weight.
PETITION → SECOND → MOTION
1 ParticipationVoucher=1 seconding unit
A petition created during cycle C snapshots a seconding quota of C vouchers. Seconding does not consume the voucher; each voucher can second that petition only once.
01PUBLIC PETITION→02VOUCHER-WEIGHTED SECONDS→03QUOTA REACHED→04QUALIFIED MOTION
PETITION LIFEAt least 7 days. Normally up to 3 cycle advances. Never more than 30 days.
If the snapshotted quota is still unmet, an old petition expires rather than remaining open indefinitely.
BINDING VOTEVoting spends governance weight.
A voter chooses how many ParticipationVouchers to commit. Those vouchers are permanently burned, and the wallet receives one locked VoteReceiptNFT recording the motion, weight, and ranked preference.
2 OUTCOMESWeighted majority
One burned voucher equals one unit of ballot weight.
3+ OUTCOMESWeighted ranked choice
If a preferred option is eliminated, the same ballot weight moves to the next surviving ranked choice.
NO RANDOM TIEBREAKSExact unresolved ties require a voucher-funded runoff.
VoteReceiptNFTs are locked to the voting wallet and carry zero future voting weight. A completed motion also mints one locked MotionRecordNFT to the project wallet as the protocol's governance archive.
GLOBAL GOVERNANCE HUBLearn globally. Petition, second, and vote on the network where your ParticipationVouchers live.
Open governanceWHITE PAPER · V0.2
The protocol, mechanics, trust model, and path forward.
Read the White Paper inline or download the PDF for the protocol architecture, current Avalanche design, trust assumptions, and roadmap.
PAQ · PRE-ANSWERED QUESTIONS
Answers before they become questions.
SwagBall uses PAQ rather than FAQ because a new project does not yet have frequently asked questions. These are the answers a new participant should have before needing to ask.
What is SwagBall?
SwagBall is a protocol and user experience for structured on-chain funding cycles. It makes participation, cycle progression, outcomes, and ownership visible on-chain.
Where can I use SwagBall?
fuji.avax.swagball.io is currently available for public testing on Avalanche Fuji. Avalanche mainnet is being prepared and will become available at avax.swagball.io when it is ready.
Does SwagBall require Avalanche?
No. Avalanche is the first blockchain ecosystem being validated for SwagBall, and the protocol is designed to support additional networks.
What is a ParticipationVoucher?
It is an on-chain record of participation and the unit of SwagBall governance weight. A holder can use vouchers to second public petitions without consuming them. During a binding vote, each surrendered ParticipationVoucher is permanently burned for one unit of ballot weight.
How does a petition become a governance vote?
A public petition snapshots the current funding-cycle number as its required seconding quota. ParticipationVoucher holders contribute one second per voucher without burning them. If the quota is reached before expiration, the petition becomes a qualified motion and voting opens.
How are multi-option governance votes decided?
Two-outcome motions use weighted majority voting. Motions with three or more outcomes use weighted ranked-choice voting: the weight from burned ParticipationVouchers follows the voter's next surviving preference when an option is eliminated. Exact unresolved ties require a new voucher-funded runoff; governance is not settled by randomness.
What is a WinnerNFT?
On the current Avalanche implementation, it is both the on-chain artifact for a completed cycle and the instrument that controls that cycle’s remaining reserved claim. The selected winner receives it first, but the contract checks the current NFT owner when a claim is made, so the unclaimed right follows ownership.
Why use an NFT at all?
Because the WinnerNFT is not relying on image scarcity as its utility. The image can be copied, but the on-chain permission cannot. The token gives SwagBall a unique, transferable ownership object that the contracts can verify, approve, transfer, and redeem. In that sense, the NFT is the key and the FundingManager-backed cycle reserve is the safe.
Does SwagBall mint 75 NFTs per second?
No. The live generator can produce up to 75 unique candidate visual states per second. NFT minting remains tied to completed funding cycles: one completion-state frame is captured as that cycle's WinnerNFT artwork. The high-rate generator creates the evolving visual field; cycle completion decides which frame becomes the permanent artifact.
What gives the WinnerNFT utility at mint?
The utility is not deferred. When the WinnerNFT is minted, its current owner already controls a contract-defined, cycle-specific claim right backed by the winner reserve for that completed cycle. Before any partial claim, that remaining claim can equal the full cycle target. This is a protocol redemption right, not a guarantee of secondary-market price.
What happens if a WinnerNFT is transferred?
The new holder becomes the wallet authorized by ownership to use the remaining claim options for that cycle. If no payout has occurred, the full target reserve remains available. If a 50% partial payout already occurred, the new holder controls the remaining 50%. A transfer does not reset amounts that were already claimed.
How does a WinnerNFT holder cash it in?
The current holder approves the FundingManager contract to transfer that cycle’s WinnerNFT, then submits the full claim. The FundingManager transfers the NFT to the project wallet and pays the holder the remaining unclaimed cycle reserve. If no partial claim occurred, that can be the full target amount; after a 50% partial claim, it is the remaining 50%.
Does contributing more Token increase my chance to win?
Not directly. SwagBall does not treat contributed Token like extra raffle tickets. Selection is one position per participating wallet, not weighted by token amount and not multiplied by contribution count. A wallet contributing 0.001 Token once can have the same chance to win as a wallet contributing 10% of the cycle target over five contributions or 20% in one contribution, assuming all three participate in the same current cycle.
How long does a cycle stay open?
By default, SwagBall is not a countdown-based funding window. The cycle stays open until its available funding capacity is filled. That means the funding capacity is the duration, and when the current cycle completes, one participating wallet from that cycle is selected.
If more Token does not buy better odds, why would someone contribute more?
Because the cycle has limited capacity. Larger contributions consume more of the available room, which can leave less opportunity for other wallets to enter before the cycle closes. That does not add extra entries for the same wallet, but it can reduce how many total wallets participate in that cycle.
Can one person participate with multiple wallets?
Yes. SwagBall counts participating addresses; it does not attempt to prove that one address equals one human. Each participating address receives one selection position. The 20% cap limits how much one address can fund, not how many addresses a person may control.
Does using more wallets guarantee a better economic outcome?
No. If those wallets are used to occupy more of the cycle’s funding capacity, the same controller must put more capital at risk while the winner reserve remains fixed at the cycle target. In the extreme full-cap case, six controlled addresses can guarantee the winning address by funding 120% of target, but full redemption returns at most 100% of target, guaranteeing a 20% target-sized net funding cost before gas. Current Fuji still allows very small accepted contributions to create entries, so low-value address splitting remains an explicit mainnet design consideration.
Where do I see the exact funding rules?
Open the active network page to see its current funding target, wallet cap, close conditions, token, contract addresses, randomness provenance, and claim controls.
Where is the technical specification?
The current White Paper documents the system architecture, Avalanche design, trust assumptions, storage model, oracle role, security considerations, and path toward mainnet.
Why is there a Degen UI?
The Standard UI is designed for people discovering the system. Degen UI exposes more raw state and controls for advanced users without forcing those details into the first-time experience.