Subnet 76: Byzantium
Subnet 76 is a Bittensor subnet slot whose current on-chain identity is registered as Byzantium. The live identity now presents a public repository, subnet website, Discord channel, and description.
Readers should still treat the live Finney identity as the source for current metadata, because subnet identity fields can change over time. This article records the current public identity fields rather than making independent claims about the subnet’s miner and validator mechanism.
Current Status
For active subnet articles, Taopedia normally describes what the subnet provides, what miners do, and how validators score them. Subnet 76’s live identity currently describes the project as “Leverage marketing with AI Swarm,” but it does not provide a detailed public mechanism description in the identity fields.
The useful published fact is the registered identity state: netuid 76 is named Byzantium and points to the Byzantium website, GitHub repository, Discord channel, and description listed in the live identity record.
On-Chain Identity
Live SN76 data is available on TaoStats. Readers can reproduce the
subnet’s registered identity fields with the Bittensor CLI command documented in the
btcli reference:
btcli subnets get-identity --netuid 76 --network finney.
That Finney identity reports the subnet name as Byzantium. It lists the GitHub repository as byzantiumaitao-arch/byzantium, the subnet URL as byzantiumai.net, the Discord channel as discord.com/channels/799672011265015819/1474042162877300776, and the description as “Leverage marketing with AI Swarm.” The contact and additional fields are blank.
Relationship to Yuma Consensus
Subnet 76 is registered on Bittensor and would use Yuma Consensus to convert validator weight vectors into the emission shares distributed to miners and validators within the subnet each tempo. The Yuma Consensus documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
Byzantium’s live identity describes the project as “Leverage marketing with AI Swarm,” but the current public repository does not provide a detailed mechanism description for how validators score miners. The Emission documentation describes how consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo, and those mechanics apply to Subnet 76 once a source-backed incentive mechanism is documented.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Byzantium (SN76), that sequence applies to the standard Bittensor lifecycle: localnet for isolated development, testnet for shared non-production testing, and mainnet for live operation with real emissions.
On mainnet, Byzantium (SN76) is registered as the live production subnet at netuid 76. The Bittensor Networks reference separates mainnet, testnet, and localnet. Participation examples or emission outcomes from one environment should not be read as representing production subnet performance in another environment.
Miner and Validator Roles
Subnet 76 operates under the standard Bittensor two-role structure. Miners supply the subnet’s capability and validators evaluate those contributions and set weights. Reward distribution follows Yuma Consensus.
Reader Boundary
Subnet 76 Byzantium should not be read as generic Bittensor subnet documentation, a complete mechanism specification, or a promise that the current public repository fully documents how miners and validators behave. This page is scoped to chain-registered identity fields and explicitly avoids implementation claims when they are not source-backed in the identity or linked docs.
Readers should verify the live identity fields (name, repo, URL, Discord, description) before relying on any metadata, because subnet identity can change over time (btcli reference).
Validator weights still flow through Yuma Consensus to determine emissions each tempo, but the subnet-specific scoring logic should be treated as unknown until it is documented by a stable public source (Yuma Consensus, Emission).
For readers, this means “AI Swarm” is an identity description, not an evidence-backed explanation of the reward function. Prefer registered sources over third-party summaries until a mechanism document is published and kept current.