UR is an open source protocol powering network infrastructure, maintained by its community.For URnetwork products (eg. VPN), go to ur.io

Notice · October 31, 2026

Epoch 3 payout delayed. Funds are safe.

Epoch 3's payout root was not committed within its window on October 30, because a server step timed out at mainnet scale. That step is now fixed. Epoch 1 had no eligible work to pay out, so its funding carried forward under the protocol's missed-commit rule.

Both epochs' funding is safe in the v1 settlement vault: 3,482.26 α for epoch 1 and 4,132.72 α for epoch 3. Carried funding does not expire.

At the end of epoch 4 (around November 6, 18:25 UTC), a recovery root moves these funds to the v2 vault. They are paid out with epoch 5, with epoch 3's funds going to the providers who did epoch 3's work. Claims are expected from around November 15. Epoch 4 is unaffected, and there is nothing you need to do.

Update, November 6: the recovery root was committed at block 9,449,041, and the funds reach the v2 vault after its 48-hour challenge period, around November 8. Changes to the v2 settlement contract now wait 72 hours behind a public timelock, so adding the funds to epoch 5 is scheduled by November 10. The schedule above is unchanged.

Read the full notice

Mainnet is live!

What miners need to do

  1. Install the new miner before November 11, 2026. From 00:00 UTC on November 11, the old miner will be deprioritized.

    Miner guide: Install
  2. Register your Bittensor wallet in the new miner. Your rewards are associated with the wallet you register.

    Miner guide: Run setup
  3. Settlement v2 pays every epoch from epoch 4. Settlement v2 started with epoch 4, from about October 30, 18:25 UTC, so version 1's limit of 1,500 paid miners an epoch no longer applies. Its first claims open from about November 8, 19:10 UTC. Epoch 3's funding is recovered and paid with epoch 5, as the notice above explains.

With settlement v2 active, the subnet is set up to run itself and scale to millions of miners. New miners can participate in Bittensor from the apps with zero Bittensor experience.

SN25 · Bittensor mainnet

Mainnet launch timeline

UR's subnet, SN25, went live on Bittensor mainnet on October 8, 2026. This timeline follows the launch by payout epoch, from the version 1 contracts to the first settlement v2 claim.

Milestones marked Scheduled or Planned are still ahead, and their dates may change. All times are UTC, and a time marked ≈ is approximate: most are projected from block numbers.

At a glance

  1. Epoch 0: Oct 8, settled by version 1
  2. Epoch 1: Oct 9–16, settled by version 1
  3. Epoch 2: Oct 16–23, settled by version 1
  4. Epoch 3: Oct 23–30, settled by version 1
  5. Epoch 4: Oct 30 – Nov 6, settled by settlement v2
  6. Epoch 5: Nov 6–13, settled by settlement v2
  7. Epoch 6: Nov 13–20, settled by settlement v2
  8. Epoch 7: Nov 20–27, settled by settlement v2
  • Version 1
  • Settlement v2
  • Settlement v2 pool registered, Oct 24–30
  • Now
  • Done
  • Scheduled or planned
  1. DoneVersion 1 contracts deployed
  2. DoneEpoch 1 begins: the first payout epoch
  3. DoneLast USDC payout batch
  4. DoneSettlement v2 contracts deployed
  5. DoneSettlement v2 active: epoch 4 begins
  6. PlannedFirst settlement v2 claims, earliest
  7. ScheduledModern provider gate turns on
  8. ScheduledSigned price goes live: demand deposits from epoch 7
Settlement

Version 1, then settlement v2

SN25 pays providers by payout epoch. These are UR's settlement epochs, not the chain's 72-minute tempo: epoch 0 lasted one day, and each later epoch lasts 7 days (50,400 blocks).

Version 1 launched on October 8 and settles epochs 1 to 3. It pays only the providers the validator has measured, and that measurement is capped at about 1,500 providers an epoch, so most miners receive no version 1 share.

Settlement v2 pays by usage and removes that cap. It was planned to take over from epoch 3, but its pool was not registered before epoch 3 began on October 23, so version 1 settles epoch 3 too. Settlement v2 is now targeting epoch 4, starting around October 30 at 18:25 UTC, pending final production checks and the on-chain pool registration before that epoch starts. The first v2 epoch would finish around November 6, with the first v2 claims no earlier than November 8, after the root is submitted and its challenge period ends. These dates are estimates from block production, and activation is confirmed only once the registration has finalized.

  1. Epoch 0 – Version 1
  2. Epoch 1 – Version 1
  3. Epoch 2 – Version 1
  4. Epoch 3 – Version 1
  5. Epoch 4 – Settlement v2
  6. Epoch 5 – Settlement v2
  7. Epoch 6 – Settlement v2
  8. Epoch 7 – Settlement v2
Timeline

Milestones

Before launch

  1. UTC Done

    Provider earnings move to SN25

    Earnings from contracts settled after this cutoff are paid through SN25. Legacy USDC payouts cover only earlier earnings.

Epoch 0

→ UTC

Version 1 Bootstrap, no payout root · Blocks 9,240,028 → 9,247,228 · 7,200 blocks, 1 day

  1. – UTC Done

    Version 1 contracts deployed

    Eight deployment steps on Bittensor's EVM, in blocks 9,239,983 to 9,240,067. The coordinator, created at 18:08 UTC, starts epoch 0.

    8 transactions
  2. UTC Done

    Network operator 1 registered

    The governance Safe registers the UR operator, network operator 1, and its pool, SN25 UID 169.

  3. UTC Done

    Version 1 validator activated

    SN25's sole validator, UID 1, publishes its activation for epoch 1 on chain.

  4. UTC Done

    Weekly epochs scheduled

    The governance Safe sets 7-day epochs of 50,400 blocks from epoch 1.

  5. UTC Done

    Network operator settlement switched on

    The network operator's servers switch on SN25 mainnet settlement.

  6. UTC Done

    Signed client-key registration live

    The first providers register their client keys with a signature for SN25.

Epoch 1

→ UTC

Version 1 The first payout epoch · Blocks 9,247,228 → 9,297,628 · 50,400 blocks, 7 days

  1. UTC Done

    Epoch 1 begins: the first payout epoch

    The first weekly payout epoch, and the one the version 1 validator activated for, starts at block 9,247,228.

  2. Done

    Last USDC payout batch

    The last batch of legacy USDC provider payouts.

  3. UTC Done

    Bittensor runtime 478 on mainnet

    The chain upgrades again, after runtime 477 on October 12. The settlement v2 contracts passed their rehearsal on runtime 478.

  4. UTC Done

    Settlement v2 start moved to epoch 3

    The subnet owner moves the start of settlement v2 from epoch 2 to epoch 3.

  5. UTC Done

    Gas policy for settlement v2 in place

    The network operator's servers load the gas policy for settlement v2's epoch closes.

  6. Planned

    Settlement v2 release checks

    The rollout dates that follow hold if the settlement v2 release passes its final checks by the morning of October 16.

  7. Planned

    Network operator services updated, v2 off

    During the day, the network operator's services move to the settlement v2 release, with v2 still switched off.

Epoch 2

→ UTC

Version 1 Version 1 · Blocks 9,297,628 → 9,348,028 · 50,400 blocks, 7 days

  1. – UTC Scheduled

    Epoch 1 closes on version 1

    The close window is 120 blocks, from block 9,297,628 to 9,297,748. The epoch 1 payout root is due by block 9,298,828, around 22:09 UTC.

  2. UTC Planned

    Connect service updated, v2 off

    The network operator's connect service follows its other services, ahead of the validator.

  3. – UTC Planned

    Settlement v2 validator starts, v2 off

    The validator runs its new release on unchanged settings, after the connect service.

  4. ≈ Done

    Settlement v2 contracts deployed

    vault2, which holds the funds, and STSettlement2 are on chain beside the unchanged version 1 contracts. Deploying them does not activate settlement v2: the v2 pool must also be registered.

  5. UTC Scheduled

    First version 1 claims (epoch 1)

    The epoch 1 payout root can finalize from block 9,312,028 at the earliest, and claims open then. As explained above, version 1 does not pay every miner.

  6. – Planned

    Validator adopts its settlement v2 settings

    Kept clear of the epoch 1 finalization on the evening of October 18.

  7. – Planned

    Network operator switches to the v2 contracts

    The network operator's servers switch to the settlement v2 contracts on October 19, and checks run on October 20. Apps pin vault2 from October 18 to 20.

  8. → UTC Done

    Settlement v2 not registered for epoch 3

    No v2 pool was registered in the window, blocks 9,333,628 to 9,340,828, so epoch 3 stays on version 1. Registration cannot activate an epoch that has already begun.

Epoch 3

→ UTC

Version 1 Version 1: the v2 pool was not registered in time · Blocks 9,348,028 → 9,398,428 · 50,400 blocks, 7 days

  1. UTC Done

    Epoch 3 begins on version 1

    Epoch 3 starts at block 9,348,028 without a v2 pool registered, so version 1 settles it. Epoch 2 closes on version 1, with its payout root due by around 22:09 UTC.

  2. → UTC Done

    Settlement v2 pool registered

    The governance Safe registered network operator 1's pool in the v2 vault before epoch 4 began, with epoch 4 as its first v2 epoch. This was the activation of settlement v2.

  3. UTC Scheduled

    Version 1 claims (epoch 2)

    The epoch 2 payout root can finalize from block 9,362,428 at the earliest. The same version 1 limit applies.

Epoch 4

→ UTC

Settlement v2 The first settlement v2 epoch · Blocks 9,398,428 → 9,448,828 · 50,400 blocks, 7 days

  1. UTC Done

    Settlement v2 active: epoch 4 begins

    From block 9,398,428, settlement v2 pays epoch 4 and every epoch after it. Epoch 3 closed on version 1 without a payout root; its funding is recovered and paid with epoch 5 (see the notice at the top).

  2. UTC Done

    Epoch 3 finalized without a payout root

    Epoch 3's payout root was not committed in its window, so it had no version 1 claims. Its 4,132.72 α carried forward with epoch 1's 3,482.26 α, and both are recovered and paid with epoch 5 (see the notice at the top).

  3. UTC Done

    Settlement v2 changes now wait 72 hours

    The settlement v2 contract that runs payouts is now owned by a timelock. Any change to it, such as an upgrade, a new auditor set or adding recovered funds to an epoch, is announced on chain and waits 72 hours, and can be cancelled during that time. Payout roots, approvals and claims are unaffected.

Epoch 5

→ UTC

Settlement v2 The first settlement v2 close and claims · Blocks 9,448,828 → 9,499,228 · 50,400 blocks, 7 days

  1. UTC Done

    First settlement v2 close and commit

    Epoch 4 ended at block 9,448,828. Its v2 ledger root was committed at block 9,449,034 and approved by the validator at block 9,449,041.

  2. UTC Done

    Recovery root sends the epoch 1 and 3 funding to the v2 vault

    A single version 1 root pays the whole carry, 3,482.26 α from epoch 1 and 4,132.72 α from epoch 3, to the v2 vault. It can be claimed into the vault after its 48-hour challenge period, from about November 8, 18:25 UTC.

  3. – UTC Planned

    First settlement v2 claims, earliest

    The first v2 root can finalize at block 9,463,434, 14,400 blocks after its commit, and claims follow once it has. An open challenge or delayed finalization can push claims later.

  4. → UTC Planned

    Recovered funds scheduled into epoch 5

    Once the recovery reaches the v2 vault, the governance Safe schedules adding it to epoch 5's payout through the 72-hour timelock. It must be scheduled by about November 10, 18:25 UTC to take effect before epoch 5 closes; otherwise the recovered payout moves to epoch 6. The recovery's record on the v2 settlement contract was scheduled on November 6 and can take effect from November 9, 21:19 UTC.

  5. UTC Scheduled

    Modern provider gate turns on

    Quality and Speed admit only providers verified as modern. The gate turns on automatically at 00:00 UTC, three weeks later than the October 21 first planned.

Epoch 6

→ UTC

Settlement v2 Its usage prices the first demand deposit · Blocks 9,499,228 → 9,549,628 · 50,400 blocks, 7 days

  1. – UTC Planned

    Epoch 5 claims, with the recovered epoch 1 and 3 funding

    Epoch 5 ends at block 9,499,228. Its root pays epoch 3's recovered funding to the providers who did epoch 3's work, in proportion to their usage, and adds epoch 1's to the regular payout. Claims follow its 14,400-block challenge period.

Epoch 7

→ UTC

Settlement v2 The first epoch with priced demand deposits · Blocks 9,549,628 → 9,600,028 · 50,400 blocks, 7 days

  1. UTC Scheduled

    Signed price goes live: demand deposits from epoch 7

    From block 9,549,628, the network operator deposits 0.010437 α per GiB and 0.005218 α per active user of epoch 6, capped at 3,000 α per epoch, as signed by the subnet owner in price.yml (published November 3). Validators check each epoch's deposit against it at every steering pass, with the validator release that ships before epoch 7. Until the deposit matches what the previous epoch's usage owes, the operator's pool gets no weight.

The time of a scheduled or planned milestone is a projection, from its block number at 12 seconds a block or from the plan, and is marked ≈ unless it was set for an exact time. A projected time moves a little if blocks run faster or slower. From epoch 1, each epoch closes within 120 blocks of its end, its payout root is due within 1,200 blocks of its end, and its claims open from 14,400 blocks (about two days) after it. Scheduled and planned milestones may change. Updated .