Skip to main content

Uberstate Inc

Uberstate Inc — 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).

Uberstate Inc — a project with an onchain token artifact on the Ethereum network, 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: insufficient data about the product was found per Tier‑1 (other than the onchain token artifact).
  • Who it’s for: not established.
  • Why onchain/token: a token contract on Ethereum is recorded; the role of onchain/the token in the product is not established per Tier‑1.

How it works (very briefly)

  1. The user does: — (no usage scenario was found per Tier‑1).
  2. The system does: —.
  3. The user gets: —.
  4. Where the blockchain is: the token contract on Ethereum.
  5. Token role (if any): the existence of the token is established by the contract; utility is not established.

Quick links: AI thesis fit

Project passport

Field Value
Project name Uberstate Inc
Also known as (aliases) —
Logo (logo) —
Token symbol (ticker) —
Category —
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0x2f115f7ae9a4c6ed075924752045bfe3f281335b
Token model (token_type) —
Max supply —
Issuance —
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
Type Link
Website —
Docs —
GitHub —
Releases / Changelog —
Whitepaper —
Roadmap —
Security advisories —
Explorer https://etherscan.io/token/0x2f115f7ae9a4c6ed075924752045bfe3f281335b
X https://twitter.com/JessDav64746034
Discord —
Telegram https://t.me/uberstaterit
Medium https://medium.com/@uberstateinc
Audit report(s) —
Bug bounty —
CoinGecko (profile, reference) —
CoinMarketCap (profile, reference) https://coinmarketcap.com/currencies/uberstate-inc/

General project overview

In the current set of links in links_*, Tier‑1 sources (Website/Docs/GitHub) are not listed, so the product description is limited to what can be formally verified: a token contract exists on the Ethereum network, and the project also has social media/channels. Any conclusions about AI/onchain/token are drawn conservatively: where there is no data, it is marked as “not established”.

Features/modules

  • Onchain artifact: the token contract on Ethereum.
  • Communication channels: X/Telegram/Medium (not proof of technology).

Typical scenarios

  • Scenario 1: a user checks the token contract → uses the explorer to view the address and basic parameters.

Getting started (wallet/network)

  • What you need: a wallet for the Ethereum network (for operations with the token).
  • Network/chain: Ethereum.
  • Fees: Ethereum network fees apply to transactions with the token.

Architecture/tech (non‑AI)

  • Components: —.
  • Participant roles: —.
  • Where logic runs: —.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1.
  • Protocol necessity drivers: not established.
  • Who pays fees: token users (transactions on Ethereum).
  • Where fees go: to Ethereum validators (network fees).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: —.

Project status and timeline

  • Current status: —.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? Per current data (without Tier‑1 Website/Docs), AI intent/an AI component are not established.
  • What is truly onchain? The token contract on the Ethereum network.
  • Why is a token needed? The existence of the token is established by the contract; necessity/utility is not established per Tier‑1.
  • Red flags (based on the information found): absence of Tier‑1 links (Website/Docs/GitHub) in links_*; risk of AI‑washing (if AI is claimed only in social media/marketing); what to double‑check: official documents/repos and the description of token utility.

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): No Tier‑1 AI intent was found (Website/Docs are absent from links_*).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 source for AI intent, we set 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): What exactly “the AI does” is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 tech description/description of an AI feature.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): Tier‑1 demos/examples of the AI component are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 demo, we set 0.
  • 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 quality metrics are not established per Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A Tier‑1 tech description of the AI component/versions is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There are no Tier‑1 documents/repos in links_* confirming AI architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: token contract 0x2f115f7ae9a4c6ed075924752045bfe3f281335b
  • Evidence: Tier‑1 — https://etherscan.io/token/0x2f115f7ae9a4c6ed075924752045bfe3f281335b
  • Why sufficient / why not (one line): The contract address and onchain history are observable 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: not established (other than the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No confirmation of onchain logic beyond the token was found per Tier‑1.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): OC_3=1 requires an explicit justification of onchain criticality; not found per Tier‑1.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token (contract on Ethereum).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x2f115f7ae9a4c6ed075924752045bfe3f281335b
  • Why sufficient / why not (one line): The existence of the token contract is a sufficient onchain fact for TK_0=0.
  • 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): Utility as “payment for the service” is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 description of payments with the token, we set 0.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties with the token are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without Tier‑1 incentive mechanics, we set 0.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): TK_3=1 requires explicit Tier‑1 governance mechanics; not found per Tier‑1.
  • 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 — —
  • Why sufficient / why not (one line): There is no Tier‑1 justification of replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0x2f115f7ae9a4c6ed075924752045bfe3f281335b Onchain fact: the token contract on the Ethereum network.
Tier‑1 — No Tier‑1 source for claim “what exactly the product does” was found (Website/Docs are absent from links_*).
Tier‑1 — No Tier‑1 source for claim “the project has an AI component or AI intent” was found.
Tier‑1 — No Tier‑1 source for claim “the token is necessary for the service/incentives/governance” was found.
Tier‑3 https://twitter.com/JessDav64746034 Project social media (claims require Tier‑1 confirmation).
Tier‑3 https://t.me/uberstaterit Project channel/chat (claims require Tier‑1 confirmation).
Tier‑3 https://medium.com/@uberstateinc Project publications (claims require Tier‑1 confirmation).
Tier‑2 https://coinmarketcap.com/currencies/uberstate-inc/ Reference token profile.

No comments to display

Back to top