SophiaTX

SophiaTX — 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).

SophiaTX — a blockchain platform/network (per the Tier‑1 developer docs and the mainnet repository); token (symbol: —).

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 blockchain network/platform with public mainnet code and documentation for developers.
• Who it’s for: for developers and network participants (details are not established per Tier‑1).
• Why onchain/token: the blockchain is the basis of the product; the Tier‑1 developer docs describe the native network currency SPHTX (fees/transfers), but detailed tokenomics are not recorded in this card.

How it works (very briefly)

1. The developer does: uses the developer docs and repositories (Tier‑1).
2. The network does: executes the mainnet logic (per the SophiaTX-MainNet repository).
3. The user gets: access to the network’s functions (details are not established per Tier‑1).
4. Where the blockchain is: the explorer and the mainnet source code are confirmed by Tier‑1.
5. Token role (if any): Tier‑1: SPHTX — the network currency/fees and operations on the blockchain.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	SophiaTX
Also known as (aliases)	—
Logo (logo)	../assets/682_sophiatx_logo.svg
Token symbol (ticker)	SPHTX
Category	Infra
Primary chain (chain)	SophiaTX
Type	Appchain
Network status	mainnet
Consensus (consensus)	DPoS
Launch date (launch_date)	—
Project status (status)	—
Token (standard)	native
Token contract	—
Token model (token_type)	utility (payments + fees)
Max supply	—
Issuance	—
Tokenomics (tokenomics, brief)	Not established per Tier‑1.
Governance	—
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	—
Use‑case (use_case)	blockchain platform/network
DecAI Fit — AI thesis fit	0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary	0 / 2 / 1 / 1
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://www.sophiatx.com/
Docs	https://developers.sophiatx.com/
GitHub	https://github.com/SophiaTX
Releases / Changelog	https://github.com/SophiaTX/SophiaTX/releases
Whitepaper	https://www.sophiatx.com/storage/web/SophiaTX_Whitepaper_v1.9.pdf
Roadmap	https://github.com/SophiaTX/SophiaTX-MainNet/milestones
Security advisories	https://github.com/SophiaTX/SophiaTX-MainNet/security
Explorer	https://explorer.sophiatx.com/blocks
App / Demo	—
X	https://twitter.com/Sophia_TX_
Discord	—
Telegram	https://t.me/sophia_TX_com
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	—
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/sophiatx/

General project overview

Per Tier‑1 sources, there are developer docs and a “SophiaTX‑MainNet” repository, which confirms the existence of a blockchain network/platform. Details of application, tokenomics and governance are not established per Tier‑1.

Features/modules

• SophiaTX-MainNet — the mainnet source code (Tier‑1).
• Developer docs (Tier‑1).

Typical scenarios

• Scenario 1: a developer uses the documentation/repositories → deploys/uses the network’s functionality (details are not established per Tier‑1).

Getting started (wallet/network)

• What you need: developer docs (see links_*).
• Network/chain: SophiaTX (per the explorer).
• Fees: Tier‑1: fees are denominated in SPHTX (see the developer docs).

Architecture/tech (non‑AI)

• Components: mainnet code + tooling/docs (Tier‑1).
• Participant roles: not established per Tier‑1.
• Where logic runs: onchain on its own network; details are not established per Tier‑1.
• Dependencies: not established per Tier‑1.

Token/economics (expanded, no forecasts)

• Token utility: Tier‑1: SPHTX — the network currency/fees (payment for operations).
• Protocol necessity drivers: Tier‑1: fees/operations on the network are denominated in SPHTX.
• Who pays fees: network users (per the Tier‑1 example of operations).
• Where fees go: not established per Tier‑1.
• Issuance/burn: not established per Tier‑1.
• Security/incentive mechanisms: not established per Tier‑1.
• Distribution and token issuance schedule: not established per Tier‑1.
• Treasury: not established per Tier‑1.

Governance

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

Security and incidents

• Audits: not found per Tier‑1.
• Bug bounty: not found per Tier‑1.
• Incidents: not established per Tier‑1.
• Threat model: not established per Tier‑1.

Project status and timeline

• Current status: mainnet (per the explorer).
• Key releases/milestones: not established per Tier‑1.
• Roadmap: see links_* (GitHub milestones).

Ecosystem/integrations

• Integrations: not established per Tier‑1.
• Partners: not established per Tier‑1.
• Where it’s actually used: not established per Tier‑1.

AI component of the project

• What is real AI here? Per Tier‑1 sources, no confirmation of an AI component or an AI roadmap was found.
• What is truly onchain? Its own network/explorer and the mainnet code in a public repository.
• Why is a token needed? Tier‑1: SPHTX — the network currency/fees (payment for operations); other roles of the token are not established per Tier‑1.
• Red flags (based on the information found): the absence of a Tier‑1 description of tokenomics/governance; double‑check the role of the token and the network parameters.

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	medium	2
Token necessity	low	1
Evidence	Tier‑1 present	1

Details

AI reality

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

• AI_0 (decision): 0
• Claim (one line): No Tier‑1 AI intent was found.
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): the documentation/repositories contain no AI roadmap.
• Conflict note (if any): —

AI_1 — what the AI does (1/0)

• AI_1 (decision): 0
• Claim (one line): No Tier‑1 confirmation of an AI component was found.
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): AI functionality is not established.
• Conflict note (if any): —

AI_2 — demos/examples (1/0)

• AI_2 (decision): 0
• Claim (one line): No demo of an AI component was found (an AI component is not established).
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): there is no subject of AI verification.
• Conflict note (if any): —

AI_3 — metrics/quality (1/0)

• AI_3 (decision): 0
• Metrics: not found (an AI component is not established).
• Context (version/date/how measured): —
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): AI metrics are absent.
• Conflict note (if any): —

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

• AI_4 (decision): 0
• Claim (one line): No Tier‑1 tech description of an AI component was found (the AI component is not established).
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): AI architecture/model versions are absent.
• Conflict note (if any): —

Onchain necessity

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

• OC_1 (decision): 1
• Chain: SophiaTX
• Addresses/identifiers: the network explorer + the mainnet repository.
• Evidence: Tier‑1 — https://explorer.sophiatx.com/blocks ; Tier‑1 — https://github.com/SophiaTX/SophiaTX-MainNet
• Why sufficient / why not (one line): there is an explorer and the mainnet source code.
• Conflict note (if any): —

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

• OC_2 (decision): 1
• What useful logic is onchain: its own blockchain network/platform (per the mainnet/explorer artifacts).
• Evidence: Tier‑1 — https://github.com/SophiaTX/SophiaTX-MainNet ; Tier‑1 — https://explorer.sophiatx.com/blocks
• Why sufficient / why not (one line): the network’s onchain logic is confirmed by artifacts.
• Conflict note (if any): —

OC_3 — onchain is critical (1/0)

• OC_3 (decision): 0
• “Replace the blockchain” test: not established per Tier‑1.
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): there is no operational justification of OC_3.
• Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

• TK_0 (decision): 0
• Claim (one line): The Tier‑1 developer docs describe the native network currency SPHTX.
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): Tier‑1 explicitly states “SPHTX currency of the blockchain”.
• Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

• TK_1 (decision): 1
• Claim (one line): Tier‑1: operation fees are denominated in SPHTX (a custom_json example with a fee in SPHTX).
• Evidence: Tier‑1 — https://developers.sophiatx.com/tutorials/
• Why sufficient / why not (one line): There is a Tier‑1 example of a transaction with a fee in SPHTX.
• Conflict note (if any): —

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

• TK_2 (decision): 0
• Claim (one line): Mechanics of incentives/collateral/penalties are not established per Tier‑1.
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): insufficient data.
• Conflict note (if any): —

TK_3 — governance (1/0)

• TK_3 (decision): 0
• Claim (one line): A governance role of the token is not established per Tier‑1.
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): insufficient data.
• 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 per Tier‑1.
• Evidence: Tier‑1 — https://developers.sophiatx.com/
• Why sufficient / why not (one line): there is no argumentation.
• Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://developers.sophiatx.com/	Tier‑1 developer docs.
Tier‑1	https://github.com/SophiaTX/SophiaTX-MainNet	Tier‑1 artifact: the mainnet source code.
Tier‑1	https://explorer.sophiatx.com/blocks	Tier‑1 artifact: the network explorer.
Tier‑1	https://developers.sophiatx.com/tutorials/	Tier‑1: examples of operations/fees in SPHTX (token utility as currency/fees).
Tier‑1	—	No Tier‑1 source for claim “there is an AI component/AI intent” was found.
Tier‑1	—	No Tier‑1 source for claim “extended role of the token (staking/incentives/governance as TK_2/TK_3)” was found.