next-epoch-start-block

Block at which the subnet's next epoch is expected to fire, or None if tempo is 0.

Chain-computed: LastEpochBlock + tempo, pulled earlier by any pending owner-triggered epoch. This is the source of truth — the epoch schedule is stateful, so the legacy client-side modular formula is wrong on subnets whose tempo changed or whose owner triggered an epoch.

Category: Epochs & timing

Parameters

Parameter	Type	Description
`netuid`	integer	Subnet to query.

CLI

btcli query next-epoch-start-block --netuid <integer> --json

Python

Namespace method (autocomplete, signature help):

import bittensor as bt

sub = bt.Subtensor()
result = sub.epochs.next_epoch_start_block(netuid=1)

Or dispatch by name, as an agent would:

result = sub.read("next_epoch_start_block", netuid=1)

Async is the same surface awaited: async with bt.Subtensor() as client:.

On-chain implementation

Runtime API SubnetInfoRuntimeApi.get_next_epoch_start_block

Every file is browsable under /code exactly as built into the runtime.