Skip to main content

inheritance Art

inheritance Art — 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).

inheritance Art — a Consumer project related to NFT/digital art; there is a token on the Ethereum network (symbol: iAI).

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 that issued NFTs and described the iAI token as an access/utility component for its own NFT/metaverse platform (per Tier‑1 Medium posts).
  • Who it’s for: users/collectors who interact with the project’s NFTs/token.
  • Why onchain/token: onchain is needed for issuance/circulation of the iAI token (ERC‑20); the token utility is described as “tier‑based access” and staking for access to the platform (claimed in Tier‑1 sources).

How it works (very briefly)

  1. The user does: holds/transfers the iAI token in a wallet and/or interacts with the project’s NFTs (per the project description on Medium).
  2. The system does: records token operations onchain (ERC‑20).
  3. The user gets: token ownership; the claimed utility of access to the platform requires separate verification against current Tier‑1 artifacts.
  4. Where the blockchain is: the iAI token — ERC‑20 on the Ethereum network.
  5. Token role (if any): in Tier‑1 Medium posts, the token is described as a component of tier‑access and staking for access to the platform; the technical implementation/status of these features are not confirmed per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name inheritance Art
Also known as (aliases) iAI, IAI
Logo (logo) ../assets/741_inheritance-art_logo.png
Token symbol (ticker) iAI
Category Consumer
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 0x6dDe4fFD6dB302Bc9a46850f61399e082f6c2122
Token model (token_type) —
Max supply 50,000,000 iAI
Issuance fixed (max total supply)
Tokenomics (tokenomics, brief) The token is described as providing tier‑based access to the platform and as an asset for staking (claimed in Medium).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) NFT + digital art + token utility
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 2
Last verified 2026-02-11

General project overview

The available Tier‑1 artifacts confirm the existence of the inheritance Art (iAI) token on the Ethereum network (ERC‑20) and the presence of official publications (Medium), where the token is described as a component of access to an NFT/metaverse platform (tier‑based access) and staking mechanics.

However, no Tier‑1 proof of the existence of an AI component (what exactly “the AI does” at the product level) was found, so ai_score = 0 and DecAI Fit = 0/6 per the SSOT rule.

Features/modules

  • Onchain artifact: the iAI token (ERC‑20) on Ethereum.
  • Communications/guide: Medium posts with instructions on the token and the BNB→Ethereum migration (1:1 swap).

Typical scenarios

  • Scenario 1: a user holds/transfers iAI → ownership is recorded onchain (Ethereum).
  • Scenario 2: a user reads the project guides → performs token/migration actions (as described in the Medium posts).

Getting started (wallet/network)

  • What you need: an EVM wallet (for example, Metamask/Trust Wallet) — as mentioned in the project instructions.
  • Network/chain: Ethereum (for ERC‑20 iAI).
  • Fees: Ethereum network fees for operations with the token.

Architecture/tech (non‑AI)

  • Components: the iAI ERC‑20 token contract; the rest of the product part (NFT platform/metaverse) is not confirmed per Tier‑1.
  • Participant roles: token holders.
  • Where logic runs: token operations — onchain; other logic — not established per Tier‑1.
  • Dependencies: Ethereum infrastructure for ERC‑20 operations.

Token/economics (expanded, no forecasts)

  • Token utility: the Medium post claims that iAI provides tier‑based access to the platform and can be used in staking mechanics.
  • Issuance/supply: Max Total Supply on Etherscan: 50,000,000 iAI.

Governance

  • Who makes decisions: not established per Tier‑1.

Security and incidents

  • Audits: not found per Tier‑1.
  • Bug bounty: not found per Tier‑1.
  • Incidents: —.
  • Threat model: typical risks of ERC‑20 tokens (phishing/approvals) and risks of trusting claimed offchain features without Tier‑1 artifacts.

Project status and timeline

  • Current status: not established per Tier‑1.

Ecosystem/integrations

  • Integrations: —.

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of an AI component of the product (what exactly the AI does) was found.
  • What is truly onchain? the iAI token as an ERC‑20 on the Ethereum network.
  • Why is a token needed? in Tier‑1 publications, the token is described as a component of access to the platform and staking mechanics; implementation/current relevance requires separate verification.
  • Red flags (based on the information found): AI‑washing: use of “AI” in positioning without a Tier‑1 tech description/demo/metrics; token‑washing: token utility is claimed, but verifiable implementation artifacts were not found per Tier‑1.

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 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 declaration of AI intentions (roadmap/docs) was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without an explicit Tier‑1 claim about AI plans, we set 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): It is not established per Tier‑1 what exactly the AI component of the product does.
  • Evidence: Tier‑1 — https://inheritanceart.medium.com/getting-started-with-crypto-and-the-inheritance-art-token-b7c3c5d3b8ef
  • Why sufficient / why not (one line): the publications describe the token/NFTs but do not provide a verifiable description of an AI feature.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): Demos/examples of AI features were not found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a demo surface of AI features, 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 were not found per Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The tech description/architecture of the AI component were not found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a 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: iAI token: 0x6dDe4fFD6dB302Bc9a46850f61399e082f6c2122
  • Evidence: Tier‑1 — https://etherscan.io/token/0x6dDe4fFD6dB302Bc9a46850f61399e082f6c2122
  • Why sufficient / why not (one line): the onchain fact of the token 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: it is not established per Tier‑1 that there is useful onchain logic other than the token.
  • Evidence: Tier‑1 — https://inheritanceart.medium.com/inheritance-art-iai-token-swap-procedure-5fcf00c583fe
  • Why sufficient / why not (one line): the publications focus on the token/migration; there are no contract addresses for “product” logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: No Tier‑1 justification was found that without the blockchain the product breaks down.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a formulation of the test, we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, iAI (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x6dDe4fFD6dB302Bc9a46850f61399e082f6c2122
  • Why sufficient / why not (one line): the onchain fact of the token is confirmed by 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 use of iAI as a mandatory payment for the service is not established per Tier‑1.
  • Evidence: Tier‑1 — https://inheritanceart.medium.com/getting-started-with-crypto-and-the-inheritance-art-token-b7c3c5d3b8ef
  • Why sufficient / why not (one line): the publication describes buying/holding the token but does not record a “pay‑per‑service” scheme.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties via the token in a verifiable form are not established per Tier‑1.
  • Evidence: Tier‑1 — https://inheritanceart.medium.com/getting-started-with-crypto-and-the-inheritance-art-token-b7c3c5d3b8ef
  • Why sufficient / why not (one line): staking is mentioned as an idea/utility, but without verifiable parameters of the mechanics, we set 0.
  • 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 — —
  • Why sufficient / why not (one line): without a description of the governance mechanics, we set 0.
  • 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): without an explicit comparison “the same is possible without the token”, we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0x6dDe4fFD6dB302Bc9a46850f61399e082f6c2122 Onchain fact of the inheritance Art (iAI) token (ERC‑20) and Max Total Supply 50,000,000 iAI.
Tier‑1 https://inheritanceart.medium.com/getting-started-with-crypto-and-the-inheritance-art-token-b7c3c5d3b8ef Official description of the iAI token and claims about access to the platform/NFT utility (as positioned in the guide).
Tier‑1 https://inheritanceart.medium.com/inheritance-art-iai-token-swap-procedure-5fcf00c583fe Migration of the iAI token from BNB Chain to Ethereum and confirmation of the current ERC‑20 contract.

No comments to display

Back to top