Rift

Rift (RIFT) — 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).

Rift — a Trading / DeFi project: a mobile app/interface for trading and strategies (borrow against Bitcoin, perps, automated strategies — per the docs). The official documentation describes the $RIFT token (distribution/vesting and a list of Solana wallet addresses), and the token mint is listed in links_* via Solscan.

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 mobile trading app/interface (swap/perps/strategies) as described in the docs.
Who it’s for: traders/users who need a “data‑driven” interface and strategies.
Why onchain/token: the $RIFT token is described in the docs (distribution + wallets), but the specific protocol utility of the token is not disclosed in the extracted Tier‑1.

How it works (very briefly)

The user does: uses the Rift mobile app/interface for trading and strategies (docs).
The system does: provides analysis of indicators/signals and access to strategies (docs).
The user gets: trading tools “in a data‑driven way” (claim; docs).
Where the blockchain is: the interface “may facilitate interaction with third‑party blockchain protocols”, and the token docs publish the Solana addresses of the distribution wallets (Terms + Wallet Tracker).
Token role (if any): in the extracted Tier‑1, no description was found that $RIFT is mandatory for payment/access/staking within the app.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Rift
Also known as (aliases)	RIFT, $RIFT, Rift Protocol (term in the Terms)
Logo (logo)	—
Token symbol (ticker)	RIFT
Category	Trading \| DeFi
Primary chain (chain)	Solana
Type	non-EVM
Network status	mainnet
Consensus (consensus)	PoS (Solana)
Launch date (launch_date)	—
Project status (status)	early access
Token (standard)	SPL
Token contract	jUpa2aDCzvdR9EF4fqDXmuyMUkonPTohphABLmRkRFj
Token model (token_type)	unknown
Max supply	—
Issuance	—
Tokenomics (tokenomics, brief)	distribution in %: Community 54.8%, Treasury&Ecosystem 32.2%, Core Contributors 10%, Liquidity 13% (docs)
Governance	company (Faraway Inc. in the legal docs)
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	backed by a16z, Sequoia, Lightspeed (claim; docs overview)
AI component (ai_component)	—
Use‑case (use_case)	mobile trading app + strategies
DecAI Fit — AI thesis fit	0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary	0 / 1 / 0 / 3
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://rift.ai
Docs	https://faq.rift.ai/
GitHub	—
Releases / Changelog	—
Whitepaper	—
Roadmap	—
Security advisories	—
Explorer	https://solscan.io/token/jUpa2aDCzvdR9EF4fqDXmuyMUkonPTohphABLmRkRFj
X	https://twitter.com/riftai_
Discord	https://discord.gg/riftai
Telegram	—
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/rift-ai
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/rift-ai/

General project overview

Rift describes itself as a “mobile trading app” that helps users act in a more “data‑driven” way: analyze indicators before a swap, use perps based on claimed “market signals”, and use automated strategies (docs). In the legal documents, the interface is described as a product of Faraway Inc. that may facilitate interaction with third‑party blockchain protocols, including the “Rift Protocol” (Terms).

Features/modules

Mobile trading app (claim): trading from a phone (docs overview).
Indicator analytics (claim): “analyze market indicators” before a swap (docs overview).
Perps and signals (claim): “trade perps based on proven market signals” (docs overview).
Automated strategies: strategies that users can publish/use (Terms: Creator Program/Strategies).

Typical scenarios

Scenario 1: the user uses the interface → analyzes tokens/indicators → makes a swap/trade (claim; docs).
Scenario 2: the user uses automated strategies → receives the strategy result/returns (we do not assess; the Terms describe risks and liability).
Scenario 3: a creator publishes a Strategy → other users use it via the interface (Terms).

Getting started (wallet/network)

What you need: the Rift app/interface (docs/Terms); a compatible self‑custodial wallet (Terms).
Network/chain: the interface works with third‑party blockchain protocols (Terms). Per the token docs, the wallet addresses are in Solana format.
Fees: fees may be charged for a subscription to the interface (Terms, Subscriptions), and network fees depend on the blockchains used (Terms).

Architecture/tech (non‑AI)

Components: mobile app/interface (offchain) + interaction with third‑party protocols/networks (Terms) + token docs/wallets (docs token pages).
Participant roles: interface users; strategy creators; the operator Faraway Inc.
Where logic runs: interface/strategies/subscriptions — offchain; the onchain part depends on external protocols; the onchain artifacts of the $RIFT token are not confirmed in the extracted Tier‑1 via an explorer page.
Dependencies: third‑party blockchains/wallets; Faraway infrastructure.

Token/economics (expanded, no forecasts)

Token utility: — (in the extracted Tier‑1 token pages there is no description that $RIFT is needed for payment/access/incentives within the interface).
Protocol necessity drivers: —.
Who pays fees: the Terms describe subscription fees for the interface (USD); network fees depend on the selected networks.
Where fees go: — (apart from network fees).
Issuance/burn: — (not extracted).
Security/incentive mechanisms: —.
Distribution and token issuance schedule: the tokenomics describes the distribution by category and vesting/cliffs (Tokenomics).
Treasury: the wallet tracker publishes the treasury/allocation addresses (Wallet Tracker).

Governance

Who makes decisions: Faraway Inc. (legal docs).
How protocol parameters change: —.
Where decisions are discussed/made: —.
Keys/multisig: —.

Security and incidents

Audits: —.
Bug bounty: —.
Incidents: —.
Threat model: strategy risks (the Terms emphasize the absence of guarantees); third‑party protocol risks; absence of public onchain artifacts of the token/app contracts in the extracted Tier‑1.

Project status and timeline

Current status: the docs publish an overview and legal documents; the project is collecting a waitlist/early access (docs overview).
Key releases/milestones: —.
Roadmap: —.

Ecosystem/integrations

Integrations: self‑custodial wallets (Terms); third‑party blockchain protocols (Terms).
Partners: incubated by Faraway and backed by a16z/Sequoia/Lightspeed (claim; docs overview).
Where it’s actually used: — (there are no public cases/integrations in the extracted Tier‑1).

AI component of the project

What is real AI here? in the extracted Tier‑1 docs there is no description of AI models/LLM/ML; the project uses “intelligent/data‑driven” language, but without technical details.
What is truly onchain? the interface interacts with third‑party blockchains (Terms); the token docs publish the Solana addresses of the distribution wallets, and the token mint is listed in links_* via Solscan.
Why is a token needed? in the extracted Tier‑1 there is no description of a mandatory utility of the $RIFT token.
Red flags (based on the information found): AI‑washing (“AI” appears in the name/ticker, but the AI component is not described); token‑washing (the utility is not disclosed); dependence on third‑party protocols and the offchain interface.

DecAI Fit component summary

DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)

Component	Level	Score
AI reality	absent	0
Onchain necessity	low	1
Token necessity	low	0
Evidence	Tier‑1 present	3

Details

AI reality

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

AI_0 (decision): 0
Claim (one line): in the extracted Tier‑1 there is no roadmap item about an AI module; there is a general “intelligent” positioning.
Evidence: Tier‑1 — https://faq.rift.ai/
Why sufficient / why not (one line): insufficient for AI intent per the rules.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): AI functions/models are not described; it is about indicators/signals/strategies without ML details.
Evidence: Tier‑1 — https://faq.rift.ai/
Why sufficient / why not (one line): there is no description of an AI component as a model/agent.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): a demo of the AI component is absent, since the AI component is not described.
Evidence: Tier‑1 — https://faq.rift.ai/
Why sufficient / why not (one line): not applicable.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —.
Context (version/date/how measured): —.
Evidence: Tier‑1 — https://faq.rift.ai/
Why sufficient / why not (one line): AI quality metrics are absent.
Conflict note (if any): —

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

AI_4 (decision): 0
Claim (one line): a technical description of AI/ML is absent.
Evidence: Tier‑1 — https://faq.rift.ai/
Why sufficient / why not (one line): not applicable.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Solana
Addresses/identifiers: SPL mint — jUpa2aDCzvdR9EF4fqDXmuyMUkonPTohphABLmRkRFj
Evidence: Tier‑1 — https://solscan.io/token/jUpa2aDCzvdR9EF4fqDXmuyMUkonPTohphABLmRkRFj
Why sufficient / why not (one line): the onchain identifier of the token (mint) is verifiable via the explorer.
Conflict note (if any): —

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

OC_2 (decision): 0
What useful logic is onchain: in the extracted Tier‑1, no onchain contracts/addresses of the product logic are described.
Evidence: Tier‑1 — https://faq.rift.ai/legal/terms
Why sufficient / why not (one line): the Terms describe interaction with third‑party protocols, but without specific addresses/contracts.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: the interface/subscriptions/strategies can work without their own onchain contracts; criticality is not proven.
Evidence: Tier‑1 — https://faq.rift.ai/legal/terms
Why sufficient / why not (one line): onchain is used as third‑party infrastructure, not as a critical “own protocol”.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the project has a token, $RIFT (tokenomics/docs).
Evidence: Tier‑1 — https://faq.rift.ai/token/tokenomics
Why sufficient / why not (one line): the tokenomics page describes the distribution of $RIFT.
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): payment for the interface/services with the $RIFT token is not described in the extracted Tier‑1.
Evidence: Tier‑1 — https://faq.rift.ai/legal/terms ; https://faq.rift.ai/token/tokenomics
Why sufficient / why not (one line): the Terms describe a subscription fee in USD and do not tie payment to $RIFT.
Conflict note (if any): —

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

TK_2 (decision): 0
Claim (one line): incentive mechanics (staking/rewards) via $RIFT are not described in the extracted Tier‑1.
Evidence: Tier‑1 — https://faq.rift.ai/token/tokenomics
Why sufficient / why not (one line): the tokenomics describes distribution/vesting, but not utility.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): the governance role of $RIFT is not described in the extracted Tier‑1.
Evidence: Tier‑1 — https://faq.rift.ai/token/tokenomics
Why sufficient / why not (one line): there is no description of governance mechanics.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 1
Claim (one line): in the absence of a described utility, $RIFT looks replaceable (payment/access via a subscription).
Evidence: Tier‑1 — https://faq.rift.ai/legal/terms ; https://faq.rift.ai/token/tokenomics
Why sufficient / why not (one line): the Terms describe a subscription, and the tokenomics does not describe mandatory functions of the token.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://faq.rift.ai/	Product overview: mobile trading app, “market indicators”, strategies (without AI technical details).
Tier‑1	https://faq.rift.ai/legal/terms	Terms: the Faraway interface, subscriptions/fees, interaction with third‑party protocols.
Tier‑1	https://faq.rift.ai/token/tokenomics	Distribution/vesting of $RIFT (without a description of utility).
Tier‑1	https://faq.rift.ai/token/wallet-tracker	Solana addresses of the distribution wallets and token amounts.
Tier‑1	https://solscan.io/token/jUpa2aDCzvdR9EF4fqDXmuyMUkonPTohphABLmRkRFj	Explorer link to the SPL mint of the $RIFT token (Solana).