tensorprox (SN91): project purpose, mechanism and token context
This project evidence summary outlines the documented purpose, mechanism and token context for tensorprox. It separates confirmed source material from information that requires current independent verification, including market data, supply figures, contract state and operational availability.
tensorprox is described in the reviewed source record as follows: tensorprox identifies itself as Bittensor subnet netuid 91 and describes a decentralized DDoS protection marketplace. This establishes the documented project purpose, but it is not a statement about price, adoption, reserves or future performance.
The documented operating model adds this context: The repository describes miners deploying scrubber infrastructure, validators auditing performance and origins receiving cleaned traffic. Readers should separate that stated mechanism from any interface, contract or market condition visible today. Product rules and integrations can change.
The evidence set also records: The project describes eBPF/XDP traffic filtering, active and standby scrubbers, region-aware assignment and audit-based rewards as design elements. This helps explain the role of tensorprox within its network or product, while leaving any unsupported reward, liquidity or performance claim unresolved.
Identity is important because similar names, wrapped assets and historical deployments can coexist. The reviewed record states: Bittensor subnet participation uses network-specific roles, emissions and validator or miner behavior; current parameters must be checked in live chain data. Before interacting with tensorprox, verify the active chain, contract and official interface rather than relying on a ticker alone.
For token role and disclosed design, the source material says: CoinGecko identifies SN91 as tensorprox in the Bittensor ecosystem and supplies changing market fields; these are not permanent protocol claims. Where supply, allocation, emissions, vesting or burn details are absent, this profile leaves them unresolved and does not infer a current figure.
The available record further notes: DDoS protection, cloud infrastructure and subnet rewards carry operational, security, availability, performance and market risks; repository descriptions do not guarantee outcomes. This is useful technical background, but it does not replace operational due diligence. Permissions, counterparties, oracles, bridges and withdrawal conditions can affect real use.
One additional evidence-bound observation is: tensorprox identifies itself as Bittensor subnet netuid 91 and describes a decentralized DDoS protection marketplace. The editorial conclusion is limited to the cited record and deliberately avoids price targets, return projections and claims that a mechanism will deliver a particular outcome.
When assessing current status, the key question is what has been independently confirmed at the time of use. The dossier supports this point: The repository describes miners deploying scrubber infrastructure, validators auditing performance and origins receiving cleaned traffic. Later official records take precedence if contracts, terms or deployments change.
The project documentation provides a basis for describing intended scope, not for filling every data gap. The reviewed material says: The project describes eBPF/XDP traffic filtering, active and standby scrubbers, region-aware assignment and audit-based rewards as design elements. Current market metrics and operational availability require separate, dated verification.
Finally, the evidence record notes: Bittensor subnet participation uses network-specific roles, emissions and validator or miner behavior; current parameters must be checked in live chain data. The practical takeaway is to verify identity, chain, contract details and current risk disclosures before acting. This is especially important where custody, lending, bridges or external dependencies are involved.
YearBull Rank update
Newest YearBull Rank value for tensorprox: #3271.
Rank change (daily snapshots).
Reading rule: rank #120 sits higher than rank #200.
- 7d window (2026-10-20): #6718 → #3271 (up by 3447).
- 30d window (2026-09-27): #5943 → #3271 (up by 2672).
Stability posture: the same move can be stable in one market and fragile in another.
Flow read: liquidity often shows up as how easily the rank holds its gains.
Venue context: a tightened venue set can reduce variance or increase it.
Trend context: a single week rarely defines a phase on its own.
Practical note: rank is best used for relative context, not certainty.
YearBull Rank is an internal ordering on YearBull that positions a coin relative to the rest of the tracked universe. Treat it as a directional context tool rather than a standalone verdict.
