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

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. Until settlement v2 starts, at most 1,500 miners are paid each epoch. Settlement v2 is targeting epoch 4, from about October 30, 18:25 UTC, pending final production checks and the on-chain pool registration before that epoch starts. Epoch 3 is still paid by version 1.

Once settlement v2 is 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. After epoch 4: from Nov 6, settled by settlement v2
  • Version 1
  • Settlement v2
  • Settlement v2 pool registration, pending, 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. PlannedTarget: settlement v2 active, epoch 4 begins
  6. PlannedFirst settlement v2 claims, earliest
  7. ScheduledModern provider gate turns on
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
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 Planned

    Settlement v2 pool registration, pending

    The governance Safe registers the v2 pool for epoch 4, after the final production checks. This is the activation, and it must finalize before block 9,398,428. At finalized block 9,354,702, on October 24 at 16:40 UTC, the pool was not yet registered.

  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 Target: the first settlement v2 epoch · Blocks 9,398,428 → 9,448,828 · 50,400 blocks, 7 days

  1. UTC Planned

    Target: settlement v2 active, epoch 4 begins

    From block 9,398,428, if the v2 pool registration has finalized by then. If it has not, epoch 4 also stays on version 1, and a new date will be set. Epoch 3 still closes on version 1, with its payout root due by around 22:25 UTC.

  2. UTC Scheduled

    Last version 1 claims (epoch 3), if v2 starts with epoch 4

    The epoch 3 payout root can finalize from block 9,412,828 at the earliest. The same version 1 limit applies.

After epoch 4

The first settlement v2 cycle

  1. – UTC Planned

    First settlement v2 close and commit

    If settlement v2 starts with epoch 4: epoch 4 ends at block 9,448,828, and the first v2 ledger root is due by block 9,450,028.

  2. – UTC Planned

    First settlement v2 claims, earliest

    The first v2 root can finalize 14,400 blocks after its commit, from block 9,463,228 to 9,464,428 at the earliest, and claims follow once it has. Open challenges, a late or invalid root, or delayed finalization can push claims later.

  3. 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.

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 .