Skip to main content

Seele

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

Seele — an infrastructure blockchain project; documentation/a repository and an ERC‑20 token contract on Ethereum are recorded per links_*.

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: an L1 blockchain project with documentation on the node/accounts/transactions and working with contracts (JSON‑RPC); an ERC‑20 token, SEELE, is also recorded on Ethereum.
  • Who it’s for: developers and network users (accounts/transfers/calls/contract deployment are described in Tier‑1 docs).
  • Why onchain/token: the network enables the execution of transactions and contracts; the ERC‑20 contract of the SEELE token on Ethereum is confirmed, but the role of the token in the economy/incentives is not established per Tier‑1 as of the verification date.

How it works (very briefly)

  1. The user does: creates an account, sends transactions/transfers, deploys and calls contracts (per Tier‑1 docs).
  2. The system does: validates transactions and maintains the network state; interaction is possible via JSON‑RPC.
  3. The user gets: transaction execution and the result of a contract call.
  4. Where the blockchain is: the project has its own network/node/tools (see Docs/GitHub); the ERC‑20 contract of the SEELE token on Ethereum is confirmed separately.
  5. Token role: the existence of the ERC‑20 token SEELE is confirmed; the token utility in the protocol is not established per Tier‑1 as of the verification date.

Quick links: AI thesis fit

Project passport

Field Value
Project name Seele
Also known as (aliases) SEELE
Logo (logo) ../assets/694_seele_logo.jpg
Token symbol (ticker) SEELE
Category Infra
Primary chain (chain) Seele
Type Appchain
Network status mainnet
Consensus (consensus) MPoW (PoW)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xb1e93236ab6073fdac58ada5564897177d4bcc43
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Not established per Tier‑1 as of the verification date.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) blockchain infrastructure
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 2 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

Seele is positioned as a blockchain project: there is Tier‑1 documentation on working with the network/node/JSON‑RPC and a client repository. The ERC‑20 contract of the SEELE token on the Ethereum network is also recorded.

Features/modules

  • Transactions/accounts and working with contracts (deploy/call) are described in the Tier‑1 documentation.

Typical scenarios

  • Scenario 1: a user creates an account → makes a transfer → (optional) deploy/call contract via CLI/JSON‑RPC (see Docs).

Getting started (wallet/network)

  • What you need: the Seele network client/node/tools (see Docs); a wallet for the Ethereum network is needed only for operations with the ERC‑20 token.
  • Network/chain: Seele (the project’s network); Ethereum — for the ERC‑20 token.
  • Fees: on the Seele network, the fee is calculated as fee = price * gas (gas depends on the tx type); Ethereum fees — for operations with the ERC‑20 token.

Architecture/tech (non‑AI)

  • Components: the node/client and network documentation (see links_* Docs/GitHub); a separate onchain artifact — the ERC‑20 token contract on Ethereum.
  • Participant roles: —.
  • Where logic runs: transactions/contracts — on the Seele network (see Docs/JSON‑RPC); ERC‑20 operations — onchain (Ethereum).
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 as of the verification date.
  • Protocol necessity drivers: not established per Tier‑1 as of the verification date.
  • Who pays fees: token users for ERC‑20 operations.
  • Where fees go: to Ethereum validators (network fees).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: not established per Tier‑1 as of the verification date.
  • How protocol parameters change: not established per Tier‑1 as of the verification date.

Security and incidents

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

Project status and timeline

  • Current status: active (based on the presence of public materials and the token).
  • Key releases/milestones: not established per Tier‑1 as of the verification date.
  • Roadmap: not found per Tier‑1 as of the verification date.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1 as of the verification date.

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of an AI component was found.
  • What is truly onchain? The Seele network (accounts/transactions/contracts are described in Tier‑1 docs); the ERC‑20 token contract on Ethereum is confirmed separately.
  • Why is a token needed? The role of the token in the economy/incentives is not established per Tier‑1 as of the verification date.
  • Red flags (based on the information found): the absence of a Tier‑1 description of the role of the token and verifiable artifacts of onchain logic other than the token.

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 medium 2
Token necessity low 0
Evidence Tier‑1 present (partially) 3
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 as intent/applicability was found.
  • Evidence: Tier‑1 — https://seelen.pro/research.html
  • Why sufficient / why not (one line): Per Tier‑1 sources, an AI component is not confirmed.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): An AI component is not established per Tier‑1.
  • Evidence: Tier‑1 — https://seelen.pro/research.html
  • Why sufficient / why not (one line): There is no Tier‑1 description of AI tasks/models.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): An AI demo is not applicable: an AI component is not established.
  • Evidence: Tier‑1 — https://seelen.pro/research.html
  • Why sufficient / why not (one line): —.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://seelen.pro/research.html
  • Why sufficient / why not (one line): No Tier‑1 quality metrics for the AI component were found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of an AI component is not applicable: an AI component is not established.
  • Evidence: Tier‑1 — https://seelen.pro/research.html
  • Why sufficient / why not (one line): —.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Seele
  • Addresses/identifiers: — (network module addresses were not recorded within this card)
  • Evidence: Tier‑1 — https://seeleteam.github.io/seele-doc/docs/Getting-Started-With-Seele.html
  • Why sufficient / why not (one line): The Tier‑1 documentation describes running a node/mainnet interaction and working via the client/JSON‑RPC.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: support for transactions and smart contracts (deploy/call) on the Seele network (including EVM contracts).
  • Evidence: Tier‑1 — https://seeleteam.github.io/seele-doc/docs/Getting-Started-With-Seele.html
  • Why sufficient / why not (one line): The Tier‑1 docs contain instructions and examples of transfer + deploy/call contract.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://seele.pro/research.html
  • Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): An ERC‑20 contract is recorded in links_*, so the token exists.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xb1e93236ab6073fdac58ada5564897177d4bcc43
  • Why sufficient / why not (one line): The onchain contract page confirms the existence of the token.
  • 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 service with the token is not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://seele.pro/research.html
  • Why sufficient / why not (one line): No explicit mechanics for paying with the token were found.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Mechanics of token‑based incentives/collateral/penalties are not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://seele.pro/research.html
  • Why sufficient / why not (one line): No incentive parameters/rules were found.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://seele.pro/research.html
  • Why sufficient / why not (one line): There is no Tier‑1 description of a governance process via the token.
  • 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 as of the verification date.
  • Evidence: Tier‑1 — https://seele.pro/research.html
  • Why sufficient / why not (one line): Without a confirmed role of the token, no conclusion can be drawn.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://seelen.pro/#/ Project website (navigation).
Tier‑1 https://seeleteam.github.io/seele-doc/index.html Project documentation.
Tier‑1 https://seeleteam.github.io/seele-doc/docs/Getting-Started-With-Seele.html Running a node and basic network operations (transfer; deploy/call contract; JSON‑RPC/client).
Tier‑1 https://seeleteam.github.io/seele-doc/docs/Seele-transaction-fee.html The fee formula fee = price * gas and basic gas values for tx/contract tx.
Tier‑1 https://github.com/seeleteam Official organization/repositories (codebase).
Tier‑1 https://arxiv.org/pdf/1905.04565.pdf Description of MPoW (Matrix‑Proof‑of‑Work) as the PoW algorithm used in Seele main-net (SeeleTech).
Tier‑1 https://etherscan.io/token/0xb1e93236ab6073fdac58ada5564897177d4bcc43 Existence of the ERC‑20 token/contract SEELE on Ethereum.
Tier‑1 https://seelescan.net Public explorer (“Seele Scan”) mentioned in the Tier‑1 documentation.

No comments to display

Back to top