Resistor AI

Resistor AI — 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).

Resistor AI — an Infra project (based on the name/positioning; a Tier‑1 description of the AI component is not established: website/docs could not be loaded), token (symbol: TOR) on the Ethereum network.

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 with the TOR token (ERC‑20) on the Ethereum network; it was not possible to confirm per Tier‑1 sources what exactly constitutes the AI product/component (the website/docs content could not be loaded).
Who it’s for: — (not established per Tier‑1 sources).
Why onchain/token: the TOR ERC‑20 token contract on Etherscan is confirmed; the purpose of the token in the product is not established per Tier‑1 sources.

How it works (very briefly)

The user does: interacts with the TOR token (transfers/DEX) or with the project’s product (if it exists).
The system does: — (not established per Tier‑1 sources).
The user gets: — (not established per Tier‑1 sources).
Where the blockchain is: the TOR token is deployed on Ethereum (Etherscan).
Token role (if any): it is not established per Tier‑1 sources that the token is needed for access to/operation of the service.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Resistor AI
Also known as (aliases)	$TOR
Logo (logo)	—
Token symbol (ticker)	TOR
Category	Infra
Primary chain (chain)	Ethereum
Type	EVM
Network status	mainnet
Consensus (consensus)	PoS (Ethereum)
Launch date (launch_date)	—
Project status (status)	active
Token (standard)	ERC-20
Token contract	0x6b448aeb3bfd1dcbe337d59f6dee159daab52768
Token model (token_type)	—
Max supply	1,000,000,000 TOR
Issuance	fixed (max total supply)
Tokenomics (tokenomics, brief)	—
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

Links (links_*)

Type	Link
Website	https://resistorai.org
Docs	https://docs.resistorai.org
GitHub	—
Releases / Changelog	—
Whitepaper	https://docs.resistorai.org/
Roadmap	—
Security advisories	—
Explorer	https://etherscan.io/token/0x6b448aeb3bfd1dcbe337d59f6dee159daab52768
X	https://twitter.com/resistorai
Discord	—
Telegram	https://t.me/ResistorAI
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	—
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/resistor-ai/

General project overview

An onchain fact could be confirmed per Tier‑1 sources: the TOR token (ERC‑20) on the Ethereum network.

The official Website/Docs pages are listed in links_*, but their content could not be loaded (unavailable per the available sources when retrieved), so the purpose of the product and AI component is not established here and is recorded conservatively.

Features/modules

TOR token (Tier‑1): ERC‑20 contract on Ethereum.
AI features: not established per Tier‑1 sources (accessible Tier‑1 text/artifacts are needed).

Typical scenarios

Scenario 1: a user interacts with the TOR token (transfer/DEX) → an onchain operation on Ethereum.

Getting started (wallet/network)

What you need: an EVM wallet.
Network/chain: Ethereum.
Fees: Ethereum network fees.

Architecture/tech (non‑AI)

Components: TOR ERC‑20 token contract (onchain); other project components are not established per Tier‑1 sources.
Where logic runs: token transfers — onchain (Ethereum).

Token/economics (expanded, no forecasts)

Token utility: not established per Tier‑1 sources (accessible Tier‑1 is needed).
Issuance/supply: max total supply 1,000,000,000 TOR (Etherscan).

Governance

Who makes decisions: —.

Security and incidents

Audits: —.
Bug bounty: —.
Incidents: —.
Threat model: typical ERC‑20 token and admin control risks (a separate contract check is needed).

Project status and timeline

Current status: —.
Roadmap: —.

Ecosystem/integrations

Integrations: — (not established per Tier‑1 sources).

AI component of the project

What is real AI here? not established per Tier‑1 sources (website/docs are unavailable per the available sources when retrieved).
What is truly onchain? TOR ERC‑20 token on Ethereum.
Why is a token needed? not established per Tier‑1 sources.
Red flags (based on the information found): absence of verifiable Tier‑1 data on the AI component and the necessity of the token in the product.

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 partial	1

Details

AI reality

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

AI_0 (decision): 0
Claim (one line): A Tier‑1 declaration of AI intent is not established (the website/docs content could not be loaded).
Evidence: Tier‑1 — —
Why sufficient / why not (one line): Without accessible Tier‑1 text/artifacts, 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 per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): A Tier‑1 description of AI features is unavailable (unavailable per the available sources when retrieved).
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): Not established per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 confirmed demo surface of the AI component.
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): Not found/not established per Tier‑1 sources.
Conflict note (if any): —

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

AI_4 (decision): 0
Claim (one line): Not found/not established per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): Without a Tier‑1 tech description, we set 0.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Ethereum
Addresses/identifiers: TOR token: 0x6b448aeb3bfd1dcbe337d59f6dee159daab52768
Evidence: Tier‑1 — https://etherscan.io/token/0x6b448aeb3bfd1dcbe337d59f6dee159daab52768
Why sufficient / why not (one line): The token contract is confirmed by the onchain explorer.
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 sources.
Evidence: Tier‑1 — https://etherscan.io/token/0x6b448aeb3bfd1dcbe337d59f6dee159daab52768
Why sufficient / why not (one line): Tier‑1 addresses/a description of protocol logic other than the ERC‑20 token are needed.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: not established per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): The project has a TOR ERC‑20 token.
Evidence: Tier‑1 — https://etherscan.io/token/0x6b448aeb3bfd1dcbe337d59f6dee159daab52768
Why sufficient / why not (one line): The token contract is confirmed by the onchain explorer.
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 per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 description that the token is used as payment for the service.
Conflict note (if any): —

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

TK_2 (decision): 0
Claim (one line): Not established per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 description of protocol incentives/collateral/penalties.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): Not established per Tier‑1 sources.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 description of governance.
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): Without a Tier‑1 role of the token, we do not draw a conclusion.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://etherscan.io/token/0x6b448aeb3bfd1dcbe337d59f6dee159daab52768	TOR ERC‑20 token contract (onchain fact).
Tier‑1	https://resistorai.org	Official website (the content could not be loaded: unavailable per the available sources when retrieved).
Tier‑1	https://docs.resistorai.org/	Official docs/whitepaper (the content could not be loaded: unavailable per the available sources when retrieved).
Tier‑1	—	No Tier‑1 source for claim “what exactly the AI component does” was found (the docs are unavailable due to a timeout).
Tier‑1	—	No Tier‑1 source for claim “why a token is needed in the product” was found (the docs are unavailable due to a timeout).