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 73

Metahash

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?

MetaHash (Bittensor Subnet 73) is essentially a decentralized OTC (over-the-counter) marketplace for Bittensor miners. In practice, it lets network participants swap their earned subnet tokens (“ALPHA” rewards) directly for the SN73 native token (“META”) without going through on-chain liquidity pools. This means miners can exit their subnet positions without slippage or price impact on the original subnet. MetaHash is explicitly described as “the first meta-mining subnet on Bittensor — a decentralized OTC marketplace for Bittensor miners”. All ALPHA submitted in an epoch is routed into a treasury, which is then used for purposes like providing cross-subnet liquidity (e.g. Uniswap V3 pools), executing other OTC trades, earning yield, etc.. The system operates in discrete epochs: each epoch has a three-phase cycle – (1) finalize rewards for the previous auction, (2) a short preparation window, then (3) a Dutch auction where miners bid by sending ALPHA in exchange for META. Early bids get larger discounts (higher META per ALPHA) as determined by a bonding curve.

No-slippage swaps: Miners can transfer ALPHA to acquire META at a predictable rate, avoiding on-pool price impact.

Epoch auctions: Each epoch distributes a fixed budget of META (≈148 META per epoch) to miners via a Dutch auction. The auction starts at a high “discount” (cheap META) that gradually decreases as more ALPHA enters the treasury. This incentivizes early participation and smooths demand.

Treasury-backed liquidity: All ALPHA received is locked in a subnet treasury. The dev team indicates this treasury funds various ecosystem supports (liquidity pools, yield strategies, OTC trades, consumption of digital goods, etc.) to “serve as a liquidity layer for derivative platforms”. Unused META (if the auction is undersubscribed) is burned to protect token value.

 

MetaHash (Bittensor Subnet 73) is essentially a decentralized OTC (over-the-counter) marketplace for Bittensor miners. In practice, it lets network participants swap their earned subnet tokens (“ALPHA” rewards) directly for the SN73 native token (“META”) without going through on-chain liquidity pools. This means miners can exit their subnet positions without slippage or price impact on the original subnet. MetaHash is explicitly described as “the first meta-mining subnet on Bittensor — a decentralized OTC marketplace for Bittensor miners”. All ALPHA submitted in an epoch is routed into a treasury, which is then used for purposes like providing cross-subnet liquidity (e.g. Uniswap V3 pools), executing other OTC trades, earning yield, etc.. The system operates in discrete epochs: each epoch has a three-phase cycle – (1) finalize rewards for the previous auction, (2) a short preparation window, then (3) a Dutch auction where miners bid by sending ALPHA in exchange for META. Early bids get larger discounts (higher META per ALPHA) as determined by a bonding curve.

No-slippage swaps: Miners can transfer ALPHA to acquire META at a predictable rate, avoiding on-pool price impact.

Epoch auctions: Each epoch distributes a fixed budget of META (≈148 META per epoch) to miners via a Dutch auction. The auction starts at a high “discount” (cheap META) that gradually decreases as more ALPHA enters the treasury. This incentivizes early participation and smooths demand.

Treasury-backed liquidity: All ALPHA received is locked in a subnet treasury. The dev team indicates this treasury funds various ecosystem supports (liquidity pools, yield strategies, OTC trades, consumption of digital goods, etc.) to “serve as a liquidity layer for derivative platforms”. Unused META (if the auction is undersubscribed) is burned to protect token value.

 

PURPOSE

What exactly is the 'product/build'?

There is no front-end product – MetaHash is a software protocol/subnet built on the Bittensor platform. The entire implementation is open-source (in the fx-integral/metahash GitHub repo) and written in Python, following standard Bittensor subnet patterns. Nodes run as Python processes (“miners” and “validators”) that interact with the Bittensor network.

Validators run a similar run_validator script. Internally, each epoch’s logic (auction mechanics, reward calculations, bonding curve) is encoded in on-chain consensus code and off-chain Python scripts. The code defines how ALPHA inputs are tracked and how weights are computed using the Dutch auction/bonding-curve formula. In short, the “product” is the subnet code itself – a specialized Bittensor consensus module – rather than a user application. Key architectural points:

Epoch-based auction logic: Custom on-chain routines handle a 3-phase auction per epoch. Validators calculate each miner’s share of META based on incoming ALPHA using a decaying bonding curve.

Python node scripts: Miners/validators join the network via Python scripts (run_miner / run_validator) that submit on-chain transactions and fetch state. This is the standard Bittensor subnet setup.

Bonding curve pricing: The protocol uses a mathematical formula (rate = max(r_min, C₀/(1+β·m))) to price ALPHA contributions. This ensures early ALPHA buys more META, and caps excess payouts.

Treasury and smart contracts: While not detailed in open docs, the mention of a “treasury” implies on-chain accounts or contracts that accumulate ALPHA and manage META issuance. In other words, incoming ALPHA is locked on-chain and only released as META via the epoch logic.

 

There is no front-end product – MetaHash is a software protocol/subnet built on the Bittensor platform. The entire implementation is open-source (in the fx-integral/metahash GitHub repo) and written in Python, following standard Bittensor subnet patterns. Nodes run as Python processes (“miners” and “validators”) that interact with the Bittensor network.

Validators run a similar run_validator script. Internally, each epoch’s logic (auction mechanics, reward calculations, bonding curve) is encoded in on-chain consensus code and off-chain Python scripts. The code defines how ALPHA inputs are tracked and how weights are computed using the Dutch auction/bonding-curve formula. In short, the “product” is the subnet code itself – a specialized Bittensor consensus module – rather than a user application. Key architectural points:

Epoch-based auction logic: Custom on-chain routines handle a 3-phase auction per epoch. Validators calculate each miner’s share of META based on incoming ALPHA using a decaying bonding curve.

Python node scripts: Miners/validators join the network via Python scripts (run_miner / run_validator) that submit on-chain transactions and fetch state. This is the standard Bittensor subnet setup.

Bonding curve pricing: The protocol uses a mathematical formula (rate = max(r_min, C₀/(1+β·m))) to price ALPHA contributions. This ensures early ALPHA buys more META, and caps excess payouts.

Treasury and smart contracts: While not detailed in open docs, the mention of a “treasury” implies on-chain accounts or contracts that accumulate ALPHA and manage META issuance. In other words, incoming ALPHA is locked on-chain and only released as META via the epoch logic.

 

WHO

Team Info

The known lead developer and creator goes by the handle “Fxintegral” and corresponds to a GitHub account (fx-integral) which hosts the project’s code, as well as a Twitter/X profile (@fxintegral_T). The Twitter profile tagline for Fxintegral confirms their role by describing Metahash’s mission, and early announcements explicitly credit “Metahash by @fxintegral_T” as the subnet’s introduction to the community. In the repository’s commit history, the author name “tegridy” appears, suggesting that the primary developer’s pseudonym might be Tegridy (potentially the same person behind Fxintegral). At this stage, the team appears to be small – likely one primary developer (Fxintegral/Tegridy) with possible support from a few community testers.

The project is open source, so community members can contribute via the GitHub repository. So far, no additional core contributors have been publicly named. Community presence: The Metahash team and community interact through public channels.

 

The known lead developer and creator goes by the handle “Fxintegral” and corresponds to a GitHub account (fx-integral) which hosts the project’s code, as well as a Twitter/X profile (@fxintegral_T). The Twitter profile tagline for Fxintegral confirms their role by describing Metahash’s mission, and early announcements explicitly credit “Metahash by @fxintegral_T” as the subnet’s introduction to the community. In the repository’s commit history, the author name “tegridy” appears, suggesting that the primary developer’s pseudonym might be Tegridy (potentially the same person behind Fxintegral). At this stage, the team appears to be small – likely one primary developer (Fxintegral/Tegridy) with possible support from a few community testers.

The project is open source, so community members can contribute via the GitHub repository. So far, no additional core contributors have been publicly named. Community presence: The Metahash team and community interact through public channels.

 

FUTURE

Roadmap

Metahash was launched in April 2025 (known then as Merit). Given its recent launch, it is in an early phase of deployment, sometimes referred to as an “alpha” stage. At launch, the code and whitepaper were made available and the basic functionality (cross-subnet scoring with ping checks) was up and running.

Key launch milestones achieved:

  • Concept and Design Completion: By the time of launch, the Metahash whitepaper and incentive model were defined (the GitHub repo contains a detailed README/whitepaper outlining the design). This indicates the concept went through a design phase to ensure it aligns with Bittensor’s goals.
  • Deployment on Mainnet: In mid-April 2025, Metahash (SN 73) was activated on the Bittensor main network. The first miners and validators (likely including the founder and some community members) registered and began producing blocks. The announcement on X on April 16, 2025 signaled the official launch of Metahash to the public.
  • Open Sourcing: Initially, the code repository was private during development, but it was opened up upon or shortly after launch. This allows anyone to inspect the code or run their own node, crucial for transparency in a decentralized project.

 

Current status (Mid-2025): Metahash is operational with a small but growing set of miners and validators. Being new, it likely hasn’t reached its maximum capacity (Bittensor subnets can have up to 256 miners, but Metahash currently has far fewer). The emission rate for Merit is still low relative to larger subnets – the root subnet’s allocation for SN-73 might be minimal until Metahash proves its utility. This period is essentially a trial by fire: the community can observe how Metahash’s incentive model performs. Key things being monitored now include:

  • Are miners responding to the incentives by actually joining more subnets?
  • Is the BMPS calculation fair to miners of different subnets (e.g., balancing those who contribute to small subnets vs big ones)?
  • Are there any exploits or unintended behaviors (such as miners trying to game the score)?
  • How well do the TOTP pings work in practice (any sync issues or false negatives)?

 

The short-term roadmap for Metahash is likely about refinement and stabilization. Ee can infer some near-term plans:

  • Fill Validator and Miner Slots: Encourage more validators to join and secure the subnet, and encourage more high-participation miners to register on Metahash. This will increase the decentralization and reliability of the subnet. For example, if only a couple of validators are running initially, a goal would be to have many validators so that the scoring is robust and not dependent on one machine’s view.
  • Parameter Tuning: Based on real-world data, the team might fine-tune parameters like the ping frequency, the weight of the ping bonus/penalty, or the 100,000 scaling factor for BMPS. If any miners find edge cases (for instance, if participating in an extremely large number of subnets yields an outsize score, or if the averaging formula needs adjustment), the algorithm could be updated.
  • Documentation and Ease of Use: Improve guides for running Metahash nodes and understanding the scoring. Being a new concept, miners might need clarity on how to maximize their Metahash score (the team will likely emphasize “participate in many subnets and stay online”). Clear documentation and maybe a FAQ could be part of the immediate plans.

 

Looking further ahead, the medium to long-term strategic goals for Metahash tie back to its mission of fostering cross-network collaboration:

  • Wider Adoption: The ultimate success for Metahash would be if most Bittensor miners choose to join subnet 73 in addition to their primary subnets. This would mean Metahash becomes a standard part of the mining strategy – a miner who is serious about maximizing their earnings and contributing broadly will naturally register on Metahash. The team will aim for this ubiquity, making Metahash an integral piece of the ecosystem.
    Ecosystem Impact: Metahash’s presence could subtly influence how new subnets attract miners. A miner might normally ignore a small, niche subnet, but with Metahash rewarding any additional subnet involvement, miners have incentive to at least try out or contribute to more subnets. Over time, this could lead to a more balanced distribution of mining power across subnets. The Metahash team will watch these trends and possibly advocate for adjustments in the broader system (for example, if Metahash reveals that certain subnets are consistently under-participated, that might flag an issue to address).
  • Enhanced Metrics: In the future, Metahash might evolve its scoring beyond the simple average of incentives. Possible enhancements could include weighting subnets differently (maybe in proportion to their emission or importance), or incorporating qualitative metrics if available (though currently all metrics are quantitative). The team could also provide analytics tools – e.g., a dashboard of BMPS for all miners, or historical charts – effectively making Metahash not just a reward subnet but a network analytics subnet. This would align with its ethos of shining light on contributions across the network.
  • Collaboration and Governance: As Metahash matures, the team might collaborate with Bittensor’s core developers and other subnet creators. One long-term possibility is integrating Metahash’s concept into governance – for instance, high-participation miners (as per Metahash) could have more say in network decisions, or Metahash’s score could feed into the Root subnet’s view of subnet value. While speculative, such ideas underscore that Metahash’s long-term goal is to become a pillar of the Bittensor ecosystem’s incentive alignment.

 

In terms of concrete upcoming milestones, the community can watch for:

  • Scaling to Full Capacity: When Metahash approaches its max miners.
  • First Major Update: The first time the Metahash team updates the subnet code (e.g., Metahash v2) after launch, incorporating lessons learned.
  • Ecosystem Recognition: Perhaps inclusion in official Bittensor documentation or dashboards as a key component once it’s proven. Right now, it’s new; a year out, it may be highlighted in “How to mine Bittensor” guides as a recommended subnet to join.

 

It’s important to note that Metahash’s formal roadmap is not yet public, and the above are logical projections. The founder has stated that at its core Metahash aims to “foster a collaborative space” for the community of miners. This suggests the philosophy guiding future plans is one of openness and collaboration. As the project grows, we can expect the Metahash team to remain communicative via Discord/Twitter about upcoming features or adjustments. The long-term vision is to ensure Metahash continues to fairly and effectively reward cross-network contributors, thereby strengthening Bittensor’s decentralized AI marketplace as a whole.

In conclusion, Bittensor Subnet 73 – Meethash – is in its infancy but has a well-defined purpose and mechanism. Going forward, its success will be measured by how well it incentivizes positive behavior network-wide and how it adapts to Bittensor’s evolution. The community-driven roadmap will evolve with input from miners and validators, steering Metahash toward its goal of making “meritocracy” a reality in decentralized AI.

 

Metahash was launched in April 2025 (known then as Merit). Given its recent launch, it is in an early phase of deployment, sometimes referred to as an “alpha” stage. At launch, the code and whitepaper were made available and the basic functionality (cross-subnet scoring with ping checks) was up and running.

Key launch milestones achieved:

  • Concept and Design Completion: By the time of launch, the Metahash whitepaper and incentive model were defined (the GitHub repo contains a detailed README/whitepaper outlining the design). This indicates the concept went through a design phase to ensure it aligns with Bittensor’s goals.
  • Deployment on Mainnet: In mid-April 2025, Metahash (SN 73) was activated on the Bittensor main network. The first miners and validators (likely including the founder and some community members) registered and began producing blocks. The announcement on X on April 16, 2025 signaled the official launch of Metahash to the public.
  • Open Sourcing: Initially, the code repository was private during development, but it was opened up upon or shortly after launch. This allows anyone to inspect the code or run their own node, crucial for transparency in a decentralized project.

 

Current status (Mid-2025): Metahash is operational with a small but growing set of miners and validators. Being new, it likely hasn’t reached its maximum capacity (Bittensor subnets can have up to 256 miners, but Metahash currently has far fewer). The emission rate for Merit is still low relative to larger subnets – the root subnet’s allocation for SN-73 might be minimal until Metahash proves its utility. This period is essentially a trial by fire: the community can observe how Metahash’s incentive model performs. Key things being monitored now include:

  • Are miners responding to the incentives by actually joining more subnets?
  • Is the BMPS calculation fair to miners of different subnets (e.g., balancing those who contribute to small subnets vs big ones)?
  • Are there any exploits or unintended behaviors (such as miners trying to game the score)?
  • How well do the TOTP pings work in practice (any sync issues or false negatives)?

 

The short-term roadmap for Metahash is likely about refinement and stabilization. Ee can infer some near-term plans:

  • Fill Validator and Miner Slots: Encourage more validators to join and secure the subnet, and encourage more high-participation miners to register on Metahash. This will increase the decentralization and reliability of the subnet. For example, if only a couple of validators are running initially, a goal would be to have many validators so that the scoring is robust and not dependent on one machine’s view.
  • Parameter Tuning: Based on real-world data, the team might fine-tune parameters like the ping frequency, the weight of the ping bonus/penalty, or the 100,000 scaling factor for BMPS. If any miners find edge cases (for instance, if participating in an extremely large number of subnets yields an outsize score, or if the averaging formula needs adjustment), the algorithm could be updated.
  • Documentation and Ease of Use: Improve guides for running Metahash nodes and understanding the scoring. Being a new concept, miners might need clarity on how to maximize their Metahash score (the team will likely emphasize “participate in many subnets and stay online”). Clear documentation and maybe a FAQ could be part of the immediate plans.

 

Looking further ahead, the medium to long-term strategic goals for Metahash tie back to its mission of fostering cross-network collaboration:

  • Wider Adoption: The ultimate success for Metahash would be if most Bittensor miners choose to join subnet 73 in addition to their primary subnets. This would mean Metahash becomes a standard part of the mining strategy – a miner who is serious about maximizing their earnings and contributing broadly will naturally register on Metahash. The team will aim for this ubiquity, making Metahash an integral piece of the ecosystem.
    Ecosystem Impact: Metahash’s presence could subtly influence how new subnets attract miners. A miner might normally ignore a small, niche subnet, but with Metahash rewarding any additional subnet involvement, miners have incentive to at least try out or contribute to more subnets. Over time, this could lead to a more balanced distribution of mining power across subnets. The Metahash team will watch these trends and possibly advocate for adjustments in the broader system (for example, if Metahash reveals that certain subnets are consistently under-participated, that might flag an issue to address).
  • Enhanced Metrics: In the future, Metahash might evolve its scoring beyond the simple average of incentives. Possible enhancements could include weighting subnets differently (maybe in proportion to their emission or importance), or incorporating qualitative metrics if available (though currently all metrics are quantitative). The team could also provide analytics tools – e.g., a dashboard of BMPS for all miners, or historical charts – effectively making Metahash not just a reward subnet but a network analytics subnet. This would align with its ethos of shining light on contributions across the network.
  • Collaboration and Governance: As Metahash matures, the team might collaborate with Bittensor’s core developers and other subnet creators. One long-term possibility is integrating Metahash’s concept into governance – for instance, high-participation miners (as per Metahash) could have more say in network decisions, or Metahash’s score could feed into the Root subnet’s view of subnet value. While speculative, such ideas underscore that Metahash’s long-term goal is to become a pillar of the Bittensor ecosystem’s incentive alignment.

 

In terms of concrete upcoming milestones, the community can watch for:

  • Scaling to Full Capacity: When Metahash approaches its max miners.
  • First Major Update: The first time the Metahash team updates the subnet code (e.g., Metahash v2) after launch, incorporating lessons learned.
  • Ecosystem Recognition: Perhaps inclusion in official Bittensor documentation or dashboards as a key component once it’s proven. Right now, it’s new; a year out, it may be highlighted in “How to mine Bittensor” guides as a recommended subnet to join.

 

It’s important to note that Metahash’s formal roadmap is not yet public, and the above are logical projections. The founder has stated that at its core Metahash aims to “foster a collaborative space” for the community of miners. This suggests the philosophy guiding future plans is one of openness and collaboration. As the project grows, we can expect the Metahash team to remain communicative via Discord/Twitter about upcoming features or adjustments. The long-term vision is to ensure Metahash continues to fairly and effectively reward cross-network contributors, thereby strengthening Bittensor’s decentralized AI marketplace as a whole.

In conclusion, Bittensor Subnet 73 – Meethash – is in its infancy but has a well-defined purpose and mechanism. Going forward, its success will be measured by how well it incentivizes positive behavior network-wide and how it adapts to Bittensor’s evolution. The community-driven roadmap will evolve with input from miners and validators, steering Metahash toward its goal of making “meritocracy” a reality in decentralized AI.

 

NEWS

Announcements

Load More