TENEX
SN67
Evaluation Score
Overall rating on a scale of 0-10
Dimension Breakdown
AI Analysis
Comprehensive evaluation of the token
SN67 (TENEX) suffers from substantial data gaps across five of the six evaluation categories. Active Development, Community Support, Tokenomics, Team and Governance, and Security and Audit History all returned insufficient data (-1.0) because available sources either failed to track Bittensor Subnet 67 or produced name-collisions with unrelated entities. The only scorable dimension, Market and Use Case (3.5/10), reflects a micro-cap valuation of approximately $1.5M, very thin daily liquidity ($23K-$68K), and undocumented fundamentals. No qualifying red-flag events or fraudulent activity were affirmatively established, but the extreme lack of verifiable project data combined with weak market liquidity presents significant downside risk.
Development Activity
Code updates and developer engagement
Community Support
Social media presence and community engagement
Tokenomics
Supply, distribution, and utility
Market & Use Case
Value proposition and competitive landscape
Team & Governance
Team background and project governance
Security & Audits
Security history and audit status
About TENEX (SN67)
TENEX (SN67) is a cryptocurrency token associated with Subnet 67 on the Bittensor network. As a subnet-specific asset within the Bittensor ecosystem, it represents participation in that dedicated subnet, though specific documentation regarding its underlying functional mechanisms, architecture, and value proposition remains unverified.
From a market perspective, TENEX trades as a micro-cap asset with a market capitalization of approximately $1.5 million. The token exhibits relatively thin trading activity, with recorded daily liquidity ranging between $23,000 and $68,000 across tracking platforms. Detailed fundamental data regarding product-market fit, token utility, and competitive differentiation are undocumented in available records.
The project is characterized by substantial information gaps across technical and operational domains. There is no publicly verifiable data concerning active code development, changelogs, tokenomic distributions (such as supply metrics or vesting schedules), or the identities and governance structures of the operating team. Additionally, no independent security audits or historical incident records could be definitively verified for Bittensor Subnet 67, highlighting limited transparency and market liquidity risks for the token.