Subnet Lease
A subnet lease is the split-profit-ownership arrangement that the Crowdloans documentation ties to a leased subnet. The same source names “Leasing is split profit ownership of a subnet” as the defining concept and notes that a lease is tightly coupled to a crowdloan: the crowdloan contributors become the lease shareholders and the crowdloan creator becomes the lease beneficiary.
Why Subnet Leasing Exists
A participant who wants to launch a new subnet needs to fund its registration. A participant who wants exposure to a new subnet may want to support its registration in exchange for a place in the resulting profit-sharing arrangement. The Crowdloans documentation places leasing as the arrangement that lets a group of contributors collectively fund subnet registration and then share in the resulting emissions, instead of a single sponsor paying the registration cost alone.
The same source describes the design choice this enables: the lease uses the crowdloan contributors as the lease shareholders and the crowdloan creator as the lease beneficiary, so a leased subnet starts with its ownership side already distributed.
What a Subnet Lease Names
A subnet lease names two roles. The beneficiary is the participant identified by the lease as the principal owner-side party; the lease fills this role with the crowdloan creator. The shareholders are the participants identified by the lease as contributors to the funding that produced the leased subnet. The two roles are recorded against the coldkeys that funded and created the underlying crowdloan.
Together these two roles are what the source calls “split profit ownership of a subnet.” The lease itself is the arrangement that ties a leased subnet to those two named parties; it is not the subnet, and it is not the funding campaign that produced the subnet.
Relationship to Crowdloans
A subnet lease and a crowdloan are related but different. A crowdloan is the funding mechanism — a campaign with contributors, a cap, and an end block. A subnet lease is the profit-sharing arrangement that a successful crowdloan produces. The Crowdloans documentation explicitly distinguishes the two: crowdloans enable the funding, and leasing describes the split-profit ownership that the funding produces. The two concepts are tightly coupled because a lease is created only when a crowdloan finalizes successfully, but they name different things — the mechanism that funds the subnet and the arrangement that splits its owner-side emissions.
Beneficiary Control Without Contributor Custody
The crowdloan documentation describes a separation that matters for reading a subnet lease correctly. When a crowdloan finalizes into a leased subnet, finalization creates a dedicated proxy for the lease beneficiary. That beneficiary can operate the subnet — for example, configuring parameters — without holding custody of contributor funds or controlling how emission shares are split among shareholders.
This is why a subnet lease is not the same thing as ordinary wallet ownership of a subnet registration cost. The beneficiary gets operational authority through the lease arrangement, while shareholders retain the pro-rata emission side defined by their crowdloan contributions. Taopedia readers should not assume the beneficiary owns the subnet in a simple single-wallet sense; the lease records a split arrangement with distinct beneficiary and shareholder roles.
References: Crowdloans, Working with Proxies
How Emissions Reach Lease Shareholders
A subnet lease ties funding participation to later upside. The Crowdloans documentation states that when a lease is created, emissions flow to contributors pro-rata based on each person’s contributed share. That pro-rata rule is what makes the lease a profit-sharing arrangement rather than a one-time refund of registration costs.
For readers, the crowdloan funds the action that produces the leased subnet, and the lease defines who receives the ongoing emission split afterward. Shareholders are the contributors named by that split; the beneficiary is the operator-side party identified at lease creation. Neither role should be read as a guarantee about subnet performance, market value, or future emission levels — only as the ownership-side structure the documentation attaches to a successfully finalized leased subnet.
Reference: Crowdloans
From Successful Crowdloan to Active Leased Subnet
A subnet lease exists only after a crowdloan path succeeds. The crowdloan documentation explains that on success the pallet finalizes the crowdloan by executing an on-chain call that registers a leased network, standing up the subnet and activating emissions for the group. The lease is the profit-sharing record that accompanies that outcome.
If the funding cap is not met by the end block, the documentation describes refund and dissolution paths instead of lease creation. That failure boundary is important: a crowdloan campaign is not automatically a subnet lease. Contributors may participate in funding without producing a lease unless the campaign finalizes successfully under the documented rules.
Readers comparing subnet vocabulary should keep the sequence clear. Subnet registration names bringing a subnet onto the network. A crowdloan names one collective funding mechanism that can pay for that registration. A subnet lease names the split-profit ownership arrangement produced when that funding path succeeds.
References: Crowdloans, Create a Subnet
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from local testing to testchain and then mainchain. For a subnet lease, that sequence changes how readers should interpret examples of funding and ownership structure.
In local testing, a lease example can show how beneficiary and shareholder roles are represented in an isolated environment. That is useful for checking the concept, but it does not show public funding participation or production emission rights.
On testchain, lease behavior can be observed in a shared testing network. This gives stronger evidence about how successful crowdloan funding, lease roles, and emissions context interact than a private local run, while still keeping the result separate from production mainchain activity.
On mainchain, a subnet lease belongs to live subnet ownership and emission-sharing context. The Crowdloans documentation describes the lease as split-profit ownership, so production readings should keep the selected subnet, beneficiary, shareholder set, and current emission context attached.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A subnet-lease example in one environment should not be read as identical evidence about ownership or profit-sharing rights in another environment.
This distinction matters because a subnet lease names an ownership-side arrangement, not just a successful registration label. The network environment explains what kind of evidence the example provides, while the lease record explains which beneficiary and shareholders are in scope.
For readers, this keeps subnet-lease examples from sounding stronger than their environment supports. Local, testchain, and mainchain contexts can all contain subnet lease language, but they do not carry the same interpretive weight.
Relationship to Subnet Deregistration
A subnet lease and subnet deregistration address different parts of the leased subnet lifecycle. A subnet lease is the split-profit ownership arrangement created when a crowdloan successfully funds a subnet’s registration, giving the creator a beneficiary proxy and contributors a pro-rata share of the subnet’s emissions. Subnet deregistration is the network mechanism that removes an entire non-immune subnet when the subnet limit is reached and a new registration attempt enters, selecting the existing subnet with the lowest EMA of alpha price for removal. The Crowdloans documentation describes a subnet lease as the profit-sharing structure attached to a crowdloan-funded subnet, and the Subnet Deregistration documentation describes the network-level removal process.
A leased subnet participates in the Bittensor network on the same terms as any other subnet and is subject to subnet deregistration once its immunity period ends. If a leased subnet’s EMA of alpha price falls to the lowest in the network and a new subnet registration triggers the deregistration mechanism, the leased subnet would be removed — ending both the subnet and the lease arrangement, including the beneficiary proxy role and contributor emission shares. Subnet lease names the profit-sharing structure that a crowdloan creates; subnet deregistration names the network-level removal that can end it.
References: Crowdloans documentation, Subnet Deregistration, Glossary: Immunity Period
Relationship to Yuma Consensus
Subnet Lease and Yuma Consensus describe related parts of Bittensor’s incentive system. Yuma Consensus is the on-chain process that aggregates validator weight signals within a subnet into miner incentives and validator dividends, applying consensus clipping, bonding, and emission calculation (Yuma Consensus).
For readers, subnet lease names a specific part of that incentive picture, while Yuma Consensus names the consensus process that turns validator weights into the resulting incentives and dividends.
Reader Boundary
This article defines a subnet lease as a concept. It does not describe how to start a crowdloan, quote current emission shares, or describe the state of any specific leased subnet. Readers should use the official crowdloans documentation and the live chain state for operational detail.
Relationship to Coinbase
A subnet lease and coinbase are related but different parts of how a leased subnet’s profits arise and are shared. A subnet lease is the split-profit-ownership arrangement that names a beneficiary and pro-rata shareholders for a crowdloan-funded subnet. Coinbase is the per-block protocol mechanism that drives TAO emission, injects TAO into emitting subnets’ pool reserves, accumulates pending emissions, and checks epoch boundaries to trigger Yuma Consensus rounds. The Crowdloans documentation describes the lease as the profit-sharing structure attached to a subnet, and the Coinbase Implementation documentation describes the per-block emission operation.
The lease determines how a subnet’s owner-side emissions are split, while coinbase is the mechanism that produces those emissions in the first place. A lease’s pro-rata profit-sharing only carries value because coinbase generates and distributes the subnet’s emissions each epoch; without that emission flow there would be no profit for the lease to divide. Coinbase answers what emissions a subnet earns and when they are paid out; the subnet lease answers who among the beneficiary and shareholders is entitled to the owner-side portion of that result.
Pro-Rata Shares Define Shareholder Emission Rights
Under the Crowdloans lease rule, each shareholder’s emission right equals their fraction of the total TAO contributed, so a larger contribution earns a proportionally larger share of the leased subnet’s emissions. Subnet lease vocabulary therefore ties shareholder rights to funding participation rather than to a flat post-registration label.
Readers should not treat shareholder status as a performance guarantee. The lease names the documented split structure; live emission levels belong to current subnet and coinbase context (Coinbase Implementation).
Beneficiary Proxy Operates the Leased Subnet
Crowdloan documentation explains that successful finalization creates a dedicated proxy for the lease beneficiary so that party can operate the subnet without holding custody of contributor funds. Subnet lease reading should therefore separate beneficiary operational authority from shareholder emission shares (Working with Proxies).
The beneficiary can configure subnet-side actions through that proxy arrangement, while shareholders retain the pro-rata owner-side emission split described at lease creation.