Skip to main content

TrustVerse

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

TrustVerse — an AI/Other project on Ethereum, token (symbol: TRV).

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 platform/protocol for managing digital assets and “digital estate planning”, where AI is used for portfolio optimization (per the project’s publications).
  • Who it’s for: users who need accounting/management of digital assets and scenarios for transferring assets/data.
  • Why onchain/token: the onchain layer is the TRV ERC‑20 token; the details of the necessity of the token for access/payment have a conflict across sources and are not unambiguously confirmed per Tier‑1 sources.

How it works (very briefly)

  1. The user does: connects to the product/service and keeps records of assets/data (per the project’s description).
  2. The system does: provides AI support for portfolio optimization and uses smart contracts for asset transfer/protection scenarios (per the project’s description).
  3. The user gets: management services and “estate planning” mechanics (within the project’s claims).
  4. Where the blockchain is: onchain — the TRV token and smart contracts (module addresses are not confirmed per Tier‑1 sources); offchain — AI computations.
  5. Token role (if any): the TRV token exists; the Tier‑1 description of the utility has a conflict (some materials speak of a “TVS token”), so the decisions on the TK flags are conservative.

Quick links: AI thesis fit

Project passport

Field Value
Project name TrustVerse
Also known as (aliases) TRV
Logo (logo) ../assets/425_trustverse_logo.svg
Token symbol (ticker) TRV
Category AI/Other | Consumer
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 0x72955ecff76e48f2c8abcce11d54e5734d6f3657
Token model (token_type) —
Max supply 1,000,000,000 TRV
Issuance fixed
Tokenomics (tokenomics, brief) total supply 1B (per the explorer); the distribution details conflict across sources
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI portfolio optimization
Use‑case (use_case) wealth management + digital estate planning
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 0 / 1
Last verified 2026-02-11

General project overview

Per the official publications (Medium), TrustVerse is positioned as a wealth management platform with a digital estate planning protocol, where AI deep‑neural technologies and smart contracts are used for scenarios of transferring/protecting assets and data.

Features/modules

  • An AI component for portfolio optimization/analytics (per the project’s description).
  • Smart contracts for “estate planning” scenarios and the transfer of assets to a designated party (per the project’s description).

Typical scenarios

  • Scenario 1: a user keeps records of digital assets → receives analytics/recommendations on the portfolio (within the project’s claims).
  • Scenario 2: a user sets up the transfer of assets/data upon an event → a smart contract executes the transfer (the implementation details are not confirmed by addresses per Tier‑1 sources).
  • Scenario 3: — (not found per Tier‑1 sources).

Getting started (wallet/network)

  • What you need: an EVM wallet for operations with the token; access to the project’s official materials.
  • Network/chain: Ethereum (the TRV token).
  • Fees: Ethereum fees for onchain operations.

Architecture/tech (non‑AI)

  • Components: the TRV token (ERC‑20) + an offchain AI/portfolio engine (per the publications) + smart‑contract mechanics (module addresses not established).
  • Participant roles: product users; the teams/operators of the service.
  • Where logic runs: the AI part — offchain; onchain — the token and possible smart contracts for transfer/accounting.
  • Dependencies: — (not found per Tier‑1 sources).

Token/economics (expanded, no forecasts)

  • Token utility: the publications contain a claim that the token grants access/is linked to the services, but there is a conflict (a “TVS token” is mentioned vs the current “TRV”).
  • Protocol necessity drivers: due to the conflict of sources, the necessity of the token is not considered confirmed.
  • Who pays fees: users of the Ethereum network for onchain operations with the token.
  • Where fees go: — (not found per Tier‑1 sources).
  • Issuance/burn: fixed supply (1B TRV per the explorer); a burn model was not found per Tier‑1 sources.
  • Security/incentive mechanisms: — (not found per Tier‑1 sources).
  • Distribution and token issuance schedule: the publication contains distribution figures, but they refer to “TVS” and are not unambiguously mapped to TRV; therefore, for TRV we consider it not established.
  • Treasury: — (not found per Tier‑1 sources).

Governance

  • Who makes decisions: — (not found per Tier‑1 sources).
  • How protocol parameters change: — (not found per Tier‑1 sources).
  • Where decisions are discussed/made: — (not found per Tier‑1 sources).
  • Keys/multisig: — (not found per Tier‑1 sources).

Security and incidents

  • Audits: — (not found per Tier‑1 sources).
  • Bug bounty: — (not found per Tier‑1 sources).
  • Incidents: — (not found per Tier‑1 sources).
  • Threat model: risks of a centralized offchain component; the risk of a mismatch between the claims about token utility and the actual implementation; standard risks of an EVM token.

Project status and timeline

  • Current status: mainnet (the TRV ERC‑20 token).
  • Key releases/milestones: — (not found per Tier‑1 sources).
  • Roadmap: a PDF is published (see links_*).

Ecosystem/integrations

  • Integrations: — (not found per Tier‑1 sources).
  • Partners: — (not found per Tier‑1 sources).
  • Where it’s actually used: the onchain artifact of the token is confirmed; product integrations/cases are not confirmed by Tier‑1 links.

AI component of the project

  • What is real AI here? The official publications claim an AI deep‑neural technology and portfolio optimization.
  • What is truly onchain? The confirmed onchain artifact is the TRV token contract on Ethereum; the addresses of the “estate planning” smart contracts are not established per Tier‑1 sources.
  • Why is a token needed? The publications contain “the token provides utility/access”, but some materials speak of TVS, not TRV; therefore, the TRV utility is not considered confirmed.
  • Red flags (based on the information found): a conflict of the ticker/terms across sources; the absence of addresses of the product modules; the risk of “token‑first” without verifiable utility.

DecAI Fit component summary

  • DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 1
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): There is AI intent, but an AI feature of the platform is also claimed (AI_1).
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/understanding-of-trustverse-3875bdcc3b19
  • Why sufficient / why not (one line): AI_0 applies when there is only intent without a feature; here the feature is described.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): An AI deep‑neural + multi‑data portfolio optimization engine for wealth management is claimed.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/understanding-of-trustverse-3875bdcc3b19
  • Why sufficient / why not (one line): The Tier‑1 publication explicitly describes the AI part and its purpose.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A public app/demo/guide for reproducible verification of the AI part was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/
  • Why sufficient / why not (one line): The publications describe the concept, but do not provide “what you can touch”.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/understanding-of-trustverse-3875bdcc3b19
  • Why sufficient / why not (one line): No quantitative metrics/benchmarks were found in the Tier‑1 publication.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): An AI tech description/architecture/versions at the level of independent verification were not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/understanding-of-trustverse-3875bdcc3b19
  • Why sufficient / why not (one line): There are general formulations, but without tech details.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the TRV token: 0x72955ecff76e48f2c8abcce11d54e5734d6f3657
  • Evidence: Tier‑1 — https://etherscan.io/token/0x72955ecff76e48f2c8abcce11d54e5734d6f3657
  • Why sufficient / why not (one line): The token contract is confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: Tier‑1 addresses of the “estate planning”/product module contracts were not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/understanding-of-trustverse-3875bdcc3b19
  • Why sufficient / why not (one line): The publications speak of smart contracts, but without addresses/specifications.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality per the SSOT test was found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/understanding-of-trustverse-3875bdcc3b19
  • Why sufficient / why not (one line): There is no formulation of “what breaks down” without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, TRV (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x72955ecff76e48f2c8abcce11d54e5734d6f3657
  • Why sufficient / why not (one line): The token contract is confirmed in the 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): The sources contain claims that “the token grants access”, but some materials speak of TVS, not TRV.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/trustverses-ai-wealth-management-digital-estate-planning-protocol-dbf05d0c7ec1
  • Why sufficient / why not (one line): Due to the conflict of the ticker/terms, the TRV utility is not considered confirmed.
  • Conflict note (if any): Conflict: the publication uses “TVS token”, while the current onchain token is TRV (0x7295…).

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

  • TK_2 (decision): 0
  • Claim (one line): A Tier‑1 description of incentives/collateral/penalties tied to TRV was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/
  • Why sufficient / why not (one line): No TK_2 mechanics were found per Tier‑1 sources.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): A Tier‑1 description of governance via TRV was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://trustverse-official.medium.com/
  • Why sufficient / why not (one line): The available sources have no governance mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): Tier‑1 proof of an irreplaceable function of TRV at the protocol level was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x72955ecff76e48f2c8abcce11d54e5734d6f3657
  • Why sufficient / why not (one line): There is a token onchain, but a “must‑have” protocol mechanic is not confirmed.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://trustverse-official.medium.com/understanding-of-trustverse-3875bdcc3b19 Tier‑1: an AI deep‑neural + portfolio optimization engine and the use of smart contracts for transferring assets/data are claimed.
Tier‑1 https://etherscan.io/token/0x72955ecff76e48f2c8abcce11d54e5734d6f3657 Tier‑1 onchain fact: the TRV token contract and total supply 1B.
Tier‑1 https://github.com/trustverse/TRV-token-contract Tier‑1: the token contract repository (a development artifact).
Tier‑1 — No Tier‑1 source for claim “there is a public App/Demo for verifying the AI part” was found per Tier‑1 sources.
Tier‑1 — No Tier‑1 source for claim “utility of the TRV token (payment/access/incentives/governance) without conflicts” was found per Tier‑1 sources.
Tier‑2 https://www.coingecko.com/en/coins/trustverse Tier‑2 token profile/metadata and links (context).
Tier‑2 https://coinmarketcap.com/currencies/trustverse/ Tier‑2 token profile/metadata and links (context).