Skip to main content

Alpha Trader Exchange

Alpha Trader Exchange — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Alpha Trader Exchange — a project associated with Bittensor Subnet 63 (per links_*), token (symbol: ATX).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a project/service claimed to be associated with Bittensor Subnet 63; links_* contains the website and the subnet dashboard.
  • Who it’s for: users/participants of the subnet (miners/validators) and integrators; the specific user scenario is not established per Tier‑1.
  • Why onchain/token: the onchain context is recorded via the subnet; the necessity of the ATX token is not confirmed by Tier‑1 (see <details>).

How it works (very briefly)

  1. The user does: interacts with the Alpha Trader Exchange product/service (details not extracted).
  2. The system does: executes the subnet/service logic (not detailed per Tier‑1).
  3. The user gets: a result in terms of the product (not detailed per Tier‑1).
  4. Where the blockchain is: the project is associated with the Bittensor network via Subnet 63 (see Explorer in links_*).
  5. Token role (if any): the existence/necessity of the ATX token is not confirmed by Tier‑1; the TK decisions are set conservatively.

Quick links: AI thesis fit

Project passport

Field Value
Project name Alpha Trader Exchange
Also known as (aliases) ATX
Logo (logo) —
Token symbol (ticker) ATX
Category AI/Other | Infra
Primary chain (chain) Bittensor
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) —
Token contract —
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Per Tier‑1, issuance/model parameters were not extracted; the necessity of the ATX token per the TK flags is not confirmed by Tier‑1.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) —
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 1
Last verified 2026-02-11

General project overview

Alpha Trader Exchange is a project that, per links_*, is associated with Bittensor Subnet 63 (via the subnet dashboard/explorer). Within this card, the available public links and a conservative assessment of the verifiability of the AI/onchain/token claims are recorded: no Tier‑1 confirmation of a specific AI component and of the necessity of the ATX token was found.

Features/modules

  • Website: the public page of the project (context; requires extraction of specific Tier‑1 facts).
  • Subnet 63 (context): the subnet dashboard (aggregator; see links_*).

Typical scenarios

  • Scenario 1: a user reads the website → understands the positioning of the project and what needs to be double‑checked with Tier‑1.
  • Scenario 2: a subnet participant looks at Subnet 63 on taostats → tracks the state/dynamics (as context).

Getting started (wallet/network)

  • What you need: you can start with the project website; participation in the subnet usually requires Bittensor tools/environment (not detailed in this card).
  • Network/chain: Bittensor (Subnet 63).
  • Fees: not established per Tier‑1 (in this card).

Architecture/tech (non‑AI)

  • Components: not established per Tier‑1 (in this card; links_* contains GitHub).
  • Participant roles: users/operators/subnet participants (miners/validators) — without details.
  • Where logic runs: presumably offchain at the participants and within the Bittensor network; not established per Tier‑1 (in this card).
  • Dependencies: Bittensor infrastructure and the project’s infrastructure (not established per Tier‑1).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 (in this card).
  • Protocol necessity drivers: No Tier‑1 source for “the token is mandatory for pay‑for‑service / collateral / governance” was found.
  • Who pays fees: not established per Tier‑1 (in this card).
  • Where fees go: not established per Tier‑1 (in this card).
  • Issuance/burn: not established per Tier‑1 (in this card).
  • Security/incentive mechanisms: not established per Tier‑1 (in this card).
  • Distribution and token issuance schedule: not established per Tier‑1 (in this card).
  • Treasury: not established per Tier‑1 (in this card).

Governance

  • Who makes decisions: not established per Tier‑1 (in this card).
  • How protocol parameters change: not established per Tier‑1 (in this card).
  • Where decisions are discussed/made: not established per Tier‑1 (in this card).
  • Keys/multisig: not established per Tier‑1 (in this card).

Security and incidents

  • Audits: not established per Tier‑1 (in this card).
  • Bug bounty: not established per Tier‑1 (in this card).
  • Incidents: not established per Tier‑1 (in this card).
  • Threat model: typical risks include dependence on external data/infrastructure and the risks of “unverifiable claims”; separate verification is required.

Project status and timeline

  • Current status: active (there is a website/links to the repository and the subnet dashboard).
  • Key releases/milestones: not established per Tier‑1 (in this card).
  • Roadmap: a link to the milestones is in links_* (the content is not analyzed in this card).

Ecosystem/integrations

  • Integrations: not established per Tier‑1 (in this card).
  • Partners: not established per Tier‑1 (in this card).
  • Where it’s actually used: not established per Tier‑1 (in this card).

AI component of the project

  • What is real AI here? per Tier‑1 sources, no confirmation of a specific AI component was found.
  • What is truly onchain? the association with Bittensor Subnet 63 is observable via the subnet dashboard/explorer (as context).
  • Why is a token needed? the necessity of the ATX token is not confirmed by Tier‑1.
  • Red flags (based on the information found): AI‑washing and token‑washing; what to double‑check: the documentation/repository for specific AI functionality and token mechanics.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 absent 1
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 claim about AI intent/applicability was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without an explicit Tier‑1 mention of AI as intent we set 0 (conservatively).
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): Not established: an AI feature as part of the product/protocol.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of an AI component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 App/Demo URL as “what you can touch” was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires an explicit demo surface + synchronization (links_*/Evidence/TL;DR).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): AI metrics/benchmarks were not found per Tier‑1.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the AI part was not found per Tier‑1 (in this card).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires a specific tech context of the AI component.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Bittensor (Subnet 63)
  • Addresses/identifiers: Subnet 63
  • Evidence: Tier‑2 — https://taostats.io/subnets/63/chart
  • Why sufficient / why not (one line): There is a public dashboard/identifier of the subnet (as context).
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 (in this card).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires a specific Tier‑1 artifact/description of the onchain logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1 (in this card).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires an explicit argument and a source.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): Per Tier‑1, the fact “the project has no token” was not found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): We set TK_0=1 only with explicit proof of the absence of a token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): Not established: mandatory payment for the service with the ATX token.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no extracted Tier‑1 pay‑for‑service mechanism.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): Not established: incentives/collateral/penalty as a mandatory mechanism tied to the ATX token.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no extracted Tier‑1 description of the mechanism.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Not established: a governance mechanism where the ATX token is mandatory.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no extracted Tier‑1 governance description.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established (no Tier‑1 role of the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires a specific conclusion and a source.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.alphatraderexchange.com/ The public page of the project (context; without extraction of specific facts on AI/onchain/token in this card).
Tier‑1 — No Tier‑1 source for claim “what is real AI here” was found.
Tier‑1 — No Tier‑1 source for claim “why is the ATX token needed (pay‑for‑service / collateral / governance)” was found.
Tier‑2 https://taostats.io/subnets/63/chart Context: Subnet 63 on the Bittensor network (dashboard aggregator).
Tier‑2 https://coinmarketcap.com/currencies/alpha-trader-exchange-atx/ Reference profile of the token/project (context).

No comments to display

Back to top