Skip to main content

sciVive

sciVive (sciViVe) — 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).

sciVive — a Meme project on PulseChain, token (symbol: sciViVe).

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: the ERC‑20 token sciVive on the PulseChain network (per the explorer API data).
  • Who it’s for: users/the token community (the purpose requires Tier‑1 sources).
  • Why onchain/token: onchain records the token and transactions; the token’s utility is not established per Tier‑1.

How it works (very briefly)

  1. The user does: performs operations with the sciViVe token or interacts with the product (not established per Tier‑1).
  2. The system does: executes ERC‑20 transfers on the PulseChain network.
  3. The user gets: confirmed transactions onchain.
  4. Where the blockchain is: the token and transactions — onchain; the product logic — outside the current sample.
  5. Token role (if any): not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name sciVive
Also known as (aliases) sciViVe | SCIVIVE
Logo (logo) —
Token symbol (ticker) sciViVe
Category Meme
Primary chain (chain) PulseChain
Type EVM
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x72a96Ea9DA0C909500eEF1Ef81B433C3A26EB649
Token model (token_type) —
Max supply 65 300 000 000 000 sciViVe
Issuance fixed (total supply)
Tokenomics (tokenomics, brief) Total supply and decimals were obtained from the explorer API (BlockScout).
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

General project overview

During the check, the Tier‑1 onchain fact of the sciVive token (symbol sciViVe) on the PulseChain network and its parameters (decimals/totalSupply) were confirmed via the explorer API. The content of the project’s website at the given link is unavailable per the available sources, so we do not record the purpose of the product/token as a fact.

Features/modules

  • sciVive ERC‑20 token: an onchain asset on PulseChain.

Typical scenarios

  • Scenario 1: a user interacts with the token → receives onchain transactions.

Getting started (wallet/network)

  • What you need: an EVM wallet with PulseChain support.
  • Network/chain: PulseChain.
  • Fees: PulseChain fees for operations with the token.

Architecture/tech (non‑AI)

  • Components: the sciVive token (ERC‑20), the explorer API (BlockScout) for reading the token parameters.
  • Participant roles: token holders; ecosystem users (not established per Tier‑1).
  • Where logic runs: onchain — the token and transactions; the product logic — outside the current sample.
  • Dependencies: PulseChain RPC; the API/explorer.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1.
  • Who pays fees: users pay PulseChain fees for operations with the token.
  • Issuance: fixed (total supply 65 300 000 000 000 sciViVe; decimals 18; per the explorer API).
  • Security/incentive mechanisms: not established per Tier‑1.

Governance

  • Who makes decisions: not established per Tier‑1.
  • How protocol parameters change: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of the token smart contract; risks of the web infrastructure (website/sources).

Project status and timeline

  • Current status: mainnet (the token on PulseChain).
  • Key releases/milestones: —.
  • Roadmap: — (not established).

Ecosystem/integrations

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

AI component of the project

  • What is real AI here? No mentions/proof of an AI component were found per Tier‑1.
  • What is truly onchain? The sciVive token (ERC‑20 on PulseChain).
  • Why is a token needed? Not established per Tier‑1.
  • Red flags (based on the information found): insufficient availability of Tier‑1 materials (website) in the current check.

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 mention of AI intentions was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 source about AI.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI features are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of an AI component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo surface for AI was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 demo.
  • 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 identified.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of the AI module was not found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There are no Tier‑1 technical artifacts about AI.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: PulseChain
  • Addresses/identifiers: sciVive contract: 0x72a96Ea9DA0C909500eEF1Ef81B433C3A26EB649
  • Evidence: Tier‑1 — https://api.scan.pulsechain.com/api?module=token&action=getToken&contractaddress=0x72a96Ea9DA0C909500eEF1Ef81B433C3A26EB649
  • Why sufficient / why not (one line): The explorer API returns name/symbol/decimals/totalSupply for the contract address.
  • 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 (other than the token).
  • Evidence: Tier‑1 — https://api.scan.pulsechain.com/api?module=token&action=getToken&contractaddress=0x72a96Ea9DA0C909500eEF1Ef81B433C3A26EB649
  • Why sufficient / why not (one line): The source confirms the token, but not protocol‑level onchain logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

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

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, sciViVe (ERC‑20).
  • Evidence: Tier‑1 — https://api.scan.pulsechain.com/api?module=token&action=getToken&contractaddress=0x72a96Ea9DA0C909500eEF1Ef81B433C3A26EB649
  • Why sufficient / why not (one line): The explorer API confirms the token at the contract address.
  • 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 utility of the token as payment for the service is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no available Tier‑1 source with a description of the utility.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Token incentives/collateral/penalties are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no available Tier‑1 source.
  • 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): There is no available Tier‑1 source.
  • 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 available Tier‑1 source.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://api.scan.pulsechain.com/api?module=token&action=getToken&contractaddress=0x72a96Ea9DA0C909500eEF1Ef81B433C3A26EB649 Onchain fact: token name/symbol/decimals/totalSupply from the explorer API.
Tier‑1 — No Tier‑1 source for claim “why the sciVive token is needed (utility)” was found or it is unavailable.

No comments to display

Back to top