Crowdloans
A crowdloan is a Bittensor funding structure for pooling TAO toward a specified action. The documented action can be an extrinsic execution or a balance transfer, with subnet creation as the primary example in Bittensor’s crowdloan documentation (Crowdloans, Crowdloan Lifecycle).
The concept is narrower than general fundraising. In Taopedia prose, crowdloan names the campaign structure that gathers contributions and applies them to the selected action; it does not by itself prove subnet launch, future emissions, or any particular contributor outcome (Create a Subnet: Burn cost, Understanding Subnets).
Funded Action Model
Crowdloans collect TAO toward a campaign-defined target. The target gives the campaign its meaning: contributors are not simply placing TAO into a generic pool, they are funding a named action under the crowdloan rules (Crowdloans, Crowdloan Lifecycle).
That makes the campaign goal part of the article context. A crowdloan for subnet creation should be read differently from a crowdloan whose funded action is a transfer, even though both use the same collective-funding vocabulary.
The useful distinction is between funding structure and funded action. Crowdloan describes how TAO is gathered and conditionally applied; the selected action describes what the campaign is trying to fund.
Subnet Creation Example
Subnet creation is the main example in the Bittensor crowdloan documentation. That example connects collective funding to the burn-cost context for bringing a subnet into existence (Crowdloans, Create a Subnet: Burn cost).
Burn cost and crowdloan are related but not interchangeable. Burn cost names the TAO cost attached to subnet creation; crowdloan names one way multiple contributors can fund an action that may include that creation cost (Glossary: Burn Cost, Crowdloans).
This keeps the subnet example from turning into a universal definition. The crowdloan concept is collective funding, while subnet creation is the documented use case that explains why the funding structure matters in Bittensor.
Campaign Outcome
A campaign can succeed or fail to finalize. If it succeeds, the funded action is performed. If it does not, the documentation describes a refund path instead of treating the attempted campaign as a completed subnet or transfer (Crowdloans).
That outcome split is central to the term. A crowdloan is conditional while the campaign is open or unfinalized; only the finalized result tells the reader whether the funded action occurred or whether contributors remain in the refund path (Crowdloans).
Emission Sharing Context
When the documented subnet-creation crowdloan succeeds, resulting emissions are shared according to contribution share. That pro-rata relationship belongs to the subnet-creation case, where contributors funded the path that brought the subnet into existence (Crowdloans, Emissions).
This does not make a crowdloan an emission guarantee. Emissions still depend on subnet behavior, consensus results, and the broader reward-distribution context (Yuma Consensus).
For reference prose, the safe reading is contribution-linked sharing, not performance prediction. A crowdloan can explain why contributors may have a pro-rata claim in the documented example without claiming that the subnet will receive a particular emission amount.
Lifecycle Boundaries
Crowdloans sit near subnet creation because subnet creation is the primary documented example. They also remain distinct from later lifecycle events such as subnet removal or dissolution (Crowdloans, Subnet Deregistration).
That boundary keeps lifecycle vocabulary precise. Crowdloan describes funding for a selected action, often at the creation side of a subnet story. Deregistration describes a later subnet removal process governed by separate rules (Subnet Deregistration).
This distinction also helps with refund language. A failed crowdloan does not create the same lifecycle evidence as a launched subnet, and a launched subnet can later face lifecycle events that are no longer part of the original funding campaign.
Reader Boundary
Crowdloan examples should keep their campaign and network context attached. A cap, end block, contribution set, refund path, or emission-sharing result belongs to the campaign where it was observed, not to every possible Bittensor crowdloan (Crowdloans, Bittensor Networks).
This article defines the concept, not a participation workflow. It should not be read as staking advice, a yield estimate, a campaign recommendation, or a step-by-step funding guide.
Unfinalized Campaigns Keep the Refund Path Open
Crowdloan documentation describes campaigns that can succeed and execute the funded action or fail and follow a refund path instead. Until finalization, the outcome remains conditional rather than completed (Crowdloans, Crowdloan Lifecycle).
For readers, an open campaign is not the same lifecycle evidence as a launched subnet or completed transfer.
Burn Cost Names Creation Price, Not the Crowdloan Mechanism
The Glossary: Burn Cost and subnet creation documentation describe the TAO cost attached to bringing a subnet into existence. Crowdloan names one collective-funding structure that can help fund an action such as subnet creation (Create a Subnet: Burn cost, Crowdloans).
Burn-cost and crowdloan vocabulary should stay separate. One names the creation price context; the other names how contributors pool TAO toward a campaign-defined action.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For crowdloans, that sequence gives readers a boundary for interpreting campaign examples, refund paths, and subnet-creation funding notes.
Localnet examples are isolated and reflect local chain state, so they are useful for controlled experiments rather than evidence of live Bittensor behavior. Testnet examples add shared non-production conditions, which can reveal integration behavior without touching mainnet state.
On mainnet, crowdloan examples should be read as live production funding campaigns on the production Bittensor network.
The Bittensor Networks reference separates mainnet, testnet, and localnet, so outcomes from one environment should not be treated as proof of behavior in another environment.
Crowdloans Fund Actions, Not Delegation Stakes
Crowdloan vocabulary describes collective funding for a named extrinsic or transfer, commonly subnet creation. Staking and delegation vocabulary describes committing TAO to support validators inside subnet markets (Crowdloans, Staking and delegation overview).
A crowdloan can gather TAO for a burn-cost or transfer action without that action being a delegation stake. Readers should keep campaign funding separate from validator stake moves.