SN73 : Merit
| Subnet | Description | Category | Company |
|---|---|---|---|
| SN73 : Metahash | Incentivize miner participation | Infrastructure | Metahash |
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.
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.
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.