With the amount of new subnets being added it can be hard to get up to date information across all subnets, so data may be slightly out of date from time to time

Subnet 77

Liquidity

Emissions
Value
Recycled
Value
Recycled (24h)
Value
Registration Cost
Value
Active Validators
Value
Active Miners
Value
Active Dual Miners/Validators
Value

ABOUT

What exactly does it do?

Subnet 77 (Liquidity) is designed to bridge Bittensor with decentralized finance. Its goal is to incentivize liquidity provisioning for Bittensor tokens in external markets. In practice, SN-77 lets TAO holders deploy funds into liquidity pools (e.g. on Uniswap V3) and rewards them based on that liquidity.

As the official Bittensor docs summarize: SN-77 “rewards miners based off of the amount of liquidity they deploy”. The subnet creator (CreativeBuilds) describes it as “a complete on-chain liquidity mining system for the Bittensor ecosystem”. In short, SN-77’s role is to extend Bittensor’s token economy into DeFi, letting the community guide where liquidity is allocated and capture trading value back into the network.

Subnet 77 (Liquidity) is designed to bridge Bittensor with decentralized finance. Its goal is to incentivize liquidity provisioning for Bittensor tokens in external markets. In practice, SN-77 lets TAO holders deploy funds into liquidity pools (e.g. on Uniswap V3) and rewards them based on that liquidity.

As the official Bittensor docs summarize: SN-77 “rewards miners based off of the amount of liquidity they deploy”. The subnet creator (CreativeBuilds) describes it as “a complete on-chain liquidity mining system for the Bittensor ecosystem”. In short, SN-77’s role is to extend Bittensor’s token economy into DeFi, letting the community guide where liquidity is allocated and capture trading value back into the network.

PURPOSE

What exactly is the 'product/build'?

SN-77 implements a custom incentive mechanism that combines on-chain contracts (on Ethereum) with off-chain coordination and the Bittensor consensus. Key points:

Liquidity auction & voting (on Ethereum): An on-chain Subnet77LiquidityAuction.sol contract holds the reward pool, and a helper contract SeventySevenV1 enables TAO holders to vote on which liquidity pools (identified by their token addresses) should receive reward weight. Token holders submit votes (e.g. via a script) allocating weights to different pools (for example, “0xPoolA:70%, 0xPoolB:30%” summing to 100%). These votes control how the subnet’s incentives are directed.

Off-chain data aggregation: Specialized validators observe the on-chain votes and fetch real liquidity data (e.g. Uniswap V3 pool reserves) from Ethereum. They use a local The Graph node (IPFS + PostgreSQL) to index relevant events and combine vote weights with actual pool liquidity. The result is a normalized weight for each liquidity provider (“miner”) in SN-77.

Pushing weights to Bittensor: Periodically, each validator submits the computed miner weights into the Bittensor network. In Bittensor terms, validators “push final miner weights to subnet 77”, which the Yuma consensus uses to distribute TAO emissions. In other words, miners who provided more weighted liquidity receive higher TAO rewards.

Dynamic TAO and alpha token: SN-77, like any subnet, has its own token (the SN-77 α token) and reserves. Miners stake TAO into the subnet to acquire α tokens, and the TAO/α reserve ratio determines the α price. In this case, miners also earn TAO rewards based on their α holdings and weight. (The alpha price evolves as miners add or remove stake.)

Summary flow: TAO holders register a hotkey and link it to an Ethereum address. They stake TAO for α tokens (raising liquidity reserves) and vote on pools on Ethereum. Meanwhile, validators aggregate on-chain votes and off-chain pool liquidity, calculate miner scores, and submit those scores back to Bittensor. The subnet’s emission (currently ~1.02% of TAO) is then allocated to miners and validators according to those scores.

 

Components & Tools

The SN-77 ecosystem comprises on-chain contracts and off-chain tooling (all open-source on GitHub). Major components include:

Smart Contracts (Ethereum):

  • Subnet77LiquidityAuction.sol: Holds the TAO reward pool and implements the logic to distribute rewards to chosen pools.
  • SeventySevenV1: Allows token holders to submit weighted votes for different liquidity pools.

 

Off-chain Scripts (TypeScript/Python): The repo provides scripts for key tasks:

  • Generating or importing EVM keypairs and linking them to Bittensor public keys (create-key.ts).
  • Registering a Bittensor hotkey to an Ethereum address (register.ts).
  • Submitting weighted votes for pools (vote.ts).
  • Analytics scripts that combine on-chain votes, taostats balances, and Uniswap liquidity to rank pools (pools.ts).
  • Checking on-chain balances for all registered keys (balance.ts). These tools run on Bun/Node.js and use Docker for a local The Graph instance.

 

Indexing & Data:

  • A local Graph Node (with IPFS and Postgres) indexes Ethereum events for ultra-fast queries of vote and liquidity data. This lets validators quickly compute weights from aggregated data.
  • User Interaction: While SN-77 does not have its own GUI, users interact via Bittensor CLI (btcli) and standard Ethereum wallets. TAO.app and dTAO Terminal (community tools) can be used to trade or track the SN-77 alpha token, and taostats.io can display SN-77 stats.

 

 

Technical Architecture

SN-77 is a hybrid system linking the Bittensor blockchain and Ethereum:

  • Infrastructure: On the Ethereum side, the subnet deploys smart contracts (on mainnet or a testnet). On the Bittensor side, SN-77 is an active subnet (Netuid 77) on the metagraph. Its emissions (∼1.02% of TAO) are managed by Bittensor’s Yuma consensus. Validators run standard Subtensor nodes plus custom software (scripts above) to feed data into the subnet.
  • Codebase: The entire codebase is open-source on GitHub (CreativeBuilds/sn77, MIT license). It includes contracts (Hardhat/ethers), TypeScript/Python tools, a Justfile/Docker for local deployment, and subgraph definitions. Dependencies include Bun/Node, Docker, and the Bittensor CLI. The architecture relies on Bittensor’s Dynamic TAO system (so the subnet uses on-chain TAO staking and alpha minting) and on Ethereum’s liquidity ecosystem (Uniswap V3 or equivalent) for market data.
  • Interaction with Bittensor: After validators compute weights off-chain, they use btcli to finalize weights on-chain in the SN-77 subnet. This means miners’ stakes on SN-77 are scored based on the previously aggregated votes and liquidity. TAO emissions are then automatically distributed to miners and validators according to those scores, following Bittensor’s standard incentive mechanism.

 

 

SN-77 implements a custom incentive mechanism that combines on-chain contracts (on Ethereum) with off-chain coordination and the Bittensor consensus. Key points:

Liquidity auction & voting (on Ethereum): An on-chain Subnet77LiquidityAuction.sol contract holds the reward pool, and a helper contract SeventySevenV1 enables TAO holders to vote on which liquidity pools (identified by their token addresses) should receive reward weight. Token holders submit votes (e.g. via a script) allocating weights to different pools (for example, “0xPoolA:70%, 0xPoolB:30%” summing to 100%). These votes control how the subnet’s incentives are directed.

Off-chain data aggregation: Specialized validators observe the on-chain votes and fetch real liquidity data (e.g. Uniswap V3 pool reserves) from Ethereum. They use a local The Graph node (IPFS + PostgreSQL) to index relevant events and combine vote weights with actual pool liquidity. The result is a normalized weight for each liquidity provider (“miner”) in SN-77.

Pushing weights to Bittensor: Periodically, each validator submits the computed miner weights into the Bittensor network. In Bittensor terms, validators “push final miner weights to subnet 77”, which the Yuma consensus uses to distribute TAO emissions. In other words, miners who provided more weighted liquidity receive higher TAO rewards.

Dynamic TAO and alpha token: SN-77, like any subnet, has its own token (the SN-77 α token) and reserves. Miners stake TAO into the subnet to acquire α tokens, and the TAO/α reserve ratio determines the α price. In this case, miners also earn TAO rewards based on their α holdings and weight. (The alpha price evolves as miners add or remove stake.)

Summary flow: TAO holders register a hotkey and link it to an Ethereum address. They stake TAO for α tokens (raising liquidity reserves) and vote on pools on Ethereum. Meanwhile, validators aggregate on-chain votes and off-chain pool liquidity, calculate miner scores, and submit those scores back to Bittensor. The subnet’s emission (currently ~1.02% of TAO) is then allocated to miners and validators according to those scores.

 

Components & Tools

The SN-77 ecosystem comprises on-chain contracts and off-chain tooling (all open-source on GitHub). Major components include:

Smart Contracts (Ethereum):

  • Subnet77LiquidityAuction.sol: Holds the TAO reward pool and implements the logic to distribute rewards to chosen pools.
  • SeventySevenV1: Allows token holders to submit weighted votes for different liquidity pools.

 

Off-chain Scripts (TypeScript/Python): The repo provides scripts for key tasks:

  • Generating or importing EVM keypairs and linking them to Bittensor public keys (create-key.ts).
  • Registering a Bittensor hotkey to an Ethereum address (register.ts).
  • Submitting weighted votes for pools (vote.ts).
  • Analytics scripts that combine on-chain votes, taostats balances, and Uniswap liquidity to rank pools (pools.ts).
  • Checking on-chain balances for all registered keys (balance.ts). These tools run on Bun/Node.js and use Docker for a local The Graph instance.

 

Indexing & Data:

  • A local Graph Node (with IPFS and Postgres) indexes Ethereum events for ultra-fast queries of vote and liquidity data. This lets validators quickly compute weights from aggregated data.
  • User Interaction: While SN-77 does not have its own GUI, users interact via Bittensor CLI (btcli) and standard Ethereum wallets. TAO.app and dTAO Terminal (community tools) can be used to trade or track the SN-77 alpha token, and taostats.io can display SN-77 stats.

 

 

Technical Architecture

SN-77 is a hybrid system linking the Bittensor blockchain and Ethereum:

  • Infrastructure: On the Ethereum side, the subnet deploys smart contracts (on mainnet or a testnet). On the Bittensor side, SN-77 is an active subnet (Netuid 77) on the metagraph. Its emissions (∼1.02% of TAO) are managed by Bittensor’s Yuma consensus. Validators run standard Subtensor nodes plus custom software (scripts above) to feed data into the subnet.
  • Codebase: The entire codebase is open-source on GitHub (CreativeBuilds/sn77, MIT license). It includes contracts (Hardhat/ethers), TypeScript/Python tools, a Justfile/Docker for local deployment, and subgraph definitions. Dependencies include Bun/Node, Docker, and the Bittensor CLI. The architecture relies on Bittensor’s Dynamic TAO system (so the subnet uses on-chain TAO staking and alpha minting) and on Ethereum’s liquidity ecosystem (Uniswap V3 or equivalent) for market data.
  • Interaction with Bittensor: After validators compute weights off-chain, they use btcli to finalize weights on-chain in the SN-77 subnet. This means miners’ stakes on SN-77 are scored based on the previously aggregated votes and liquidity. TAO emissions are then automatically distributed to miners and validators according to those scores, following Bittensor’s standard incentive mechanism.

 

 

WHO

Team Info

The publicly known developer behind SN-77 is CreativeBuilds, a Bittensor community member and GitHub user. The subnet’s GitHub repository and commits are authored by “creativebuilds” (as shown in the repo metadata and LICENSE)

The publicly known developer behind SN-77 is CreativeBuilds, a Bittensor community member and GitHub user. The subnet’s GitHub repository and commits are authored by “creativebuilds” (as shown in the repo metadata and LICENSE)

FUTURE

Roadmap

SN-77 was registered on March 14, 2025, and by late May 2025 the developer announced it was entering an initial launch phase. The code was made public and validators have been configured. As of mid-2025, SN-77 is active on mainnet: its TAO/α reserve mechanism is live and the subnet is receiving its scheduled emissions (~1.02% of TAO). Initial on-chain activity (validator votes and weight updates) has begun, and the SN-77 token is trading in the dTAO ecosystem (e.g. ~0.0146 τ per SN-77 at the time of writing).

Future development plans have not been formally published, but likely milestones include: expanding liquidity pool coverage, refining the voting/auction mechanisms, and integrating new tooling. The subnet is designed to evolve under community governance – for example, token holders can adjust pool weights each epoch – so its roadmap will depend on community participation and performance of the liquidity strategy. In summary, Subnet 77 has moved from idea to implementation and is now operational, with ongoing updates managed via its open GitHub repository.

SN-77 was registered on March 14, 2025, and by late May 2025 the developer announced it was entering an initial launch phase. The code was made public and validators have been configured. As of mid-2025, SN-77 is active on mainnet: its TAO/α reserve mechanism is live and the subnet is receiving its scheduled emissions (~1.02% of TAO). Initial on-chain activity (validator votes and weight updates) has begun, and the SN-77 token is trading in the dTAO ecosystem (e.g. ~0.0146 τ per SN-77 at the time of writing).

Future development plans have not been formally published, but likely milestones include: expanding liquidity pool coverage, refining the voting/auction mechanisms, and integrating new tooling. The subnet is designed to evolve under community governance – for example, token holders can adjust pool weights each epoch – so its roadmap will depend on community participation and performance of the liquidity strategy. In summary, Subnet 77 has moved from idea to implementation and is now operational, with ongoing updates managed via its open GitHub repository.

NEWS

Announcements

Load More