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 the experience can extend across supported blockchain networks.
OPEN → FUND → COMPLETE → RECORDEach supported network provides its own live funding experience.
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 recording its outcome.
A cycle opens
Each funding cycle defines a target, contribution rules, and completion conditions.
People participate
Participants fund directly on-chain. Their participation can be recorded as an on-chain artifact.
The cycle completes
Completion locks the cycle's outcome and begins the winner-selection or distribution process defined for that network.
The record remains
Artifacts, ownership, provenance, and claims form a durable history of what happened in that cycle.
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
A record of participation.
A ParticipationVoucher can provide a deterministic on-chain record of the cycle, token, and original participant.
WINNERNFTCycle outcome artifactOwnership can carry claim rights defined by the active network's funding rules.
WINNERNFT
A record of a completed outcome.
WinnerNFT ownership makes the selected holder and any associated claim rights visible directly from on-chain state.
WHITE 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. On Avalanche, its identity and deterministic artwork are derived from the actual cycle, token ID, and original participant.
What is a WinnerNFT?
It is the artifact associated with a completed cycle's selected winner. Its ownership can carry claim rights defined by the active network's funding rules.
Where do I see the exact funding rules?
Open the active network page to see its current funding target, wallet cap, close conditions, currency, 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.