Byte
Byte (BYTE) — 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).
Byte — a Meme project on Ethereum, token (symbol: BYTE).
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 meme token promoted as an “AI dog / companion”.
- Who it’s for: the crypto community/meme token traders.
- Why onchain/token: the token exists onchain as an ERC‑20; no provable “product” necessity for the token, other than trading/the community meme, was found.
How it works (very briefly)
- The user does: performs operations with BYTE or uses it as a community asset.
- The system does: standard ERC‑20 operations on Ethereum.
- The user gets: participation in the community around the meme asset.
- Where the blockchain is: the entire “product” is the token itself and its transactions.
- Token role (if any): the token is the object itself.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Byte |
| Also known as (aliases) | ByteDog; BYTE |
| Logo (logo) | ../assets/174_byte_logo.jpg |
| Token symbol (ticker) | BYTE |
| Category | Meme |
| 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 | 0xDe342A3e269056FC3305f9E315F4c40d917bA521 |
| Token model (token_type) | — |
| Max supply | 964,467,033,476.831263951 BYTE (fixed), decimals: 9 |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | no public utility (payment/access/protocol staking) was found |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | positioning only ("AI dog/companion") |
| Use‑case (use_case) | meme token |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | 0 / 1 / 0 / 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.bytedog.ai/ |
| Docs | — |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0xde342a3e269056fc3305f9e315f4c40d917ba521 |
| X | https://twitter.com/ByteDogToken |
| Discord | — |
| Telegram | https://t.me/Byte_ERC20 |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/byte |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/byte/ |
General project overview
Byte is a meme token on Ethereum. In its public materials, the project uses the rhetoric of an “AI dog/companion”, but within this card no verifiable (Tier‑1) technical artifacts were found: code, a demo, a description of the AI system’s architecture or metrics.
Features/modules
- ERC‑20 token (the main object).
- Community channels (X/Telegram).
Typical scenarios
- Scenario 1: a user performs operations with BYTE → gets a standard ERC‑20 transaction.
- Scenario 2: a user interacts with BYTE → participates in the community.
Getting started (wallet/network)
- What you need: an EVM wallet (for example, MetaMask) and ETH for fees.
- Network/chain: Ethereum mainnet.
- Fees: Ethereum gas.
Architecture/tech (non‑AI)
- Components: an ERC‑20 contract + external interfaces (wallets/DEX).
- Participant roles: token holders.
- Where logic runs: in the token’s smart contract (transfers/balances).
- Dependencies: Ethereum.
Token/economics (expanded, no forecasts)
- Token utility: within this card, only trading/holding of the token is confirmed.
- Protocol necessity drivers: no separate protocol was identified; the token is not tied to a provable service.
- Issuance/burn: fixed supply (per Etherscan data).
Governance
- Who makes decisions: — (no DAO/procedures found).
Security and incidents
- Audits / bug bounty: not found.
Project status and timeline
- Current status: active as a token.
Ecosystem/integrations
- Integrations: standard EVM tools and exchanges/DEX (not recorded as an “AI technology”).
AI component of the project
- What is real AI here? Within the available Tier‑1 sources, no verifiable AI component was found (no description, demo or metrics).
- What is truly onchain? The ERC‑20 token and its transactions.
- Why is a token needed? The token is an object of trading/community; protocol necessity is not confirmed.
- Red flags (based on the information found): high risk of AI‑washing (AI terms without technical artifacts); token‑washing (a token without provable 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 roadmap/update with an intent to “build AI” was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a Tier‑1 source, an “intent” is not counted.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): a specific description of an AI function is absent in Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no verifiable description of AI functions.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): no demos/examples of the AI at work were found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no verifiable 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): metrics are absent.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a technical description of the AI architecture is absent.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no documentation/code related to an AI component.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: 0xDe342A3e269056FC3305f9E315F4c40d917bA521
- Evidence: Tier‑1 — https://etherscan.io/token/0xde342a3e269056fc3305f9e315f4c40d917ba521
- Why sufficient / why not (one line): the token address is verifiable onchain.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: no useful onchain logic other than the token was found.
- Evidence: Tier‑1 — https://etherscan.io/token/0xde342a3e269056fc3305f9e315f4c40d917ba521
- Why sufficient / why not (one line): nothing other than the token is confirmed.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the project has no confirmed protocol/service that “breaks down” without onchain.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there are no grounds for OC_3=1.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the BYTE token exists.
- Evidence: Tier‑1 — https://etherscan.io/token/0xde342a3e269056fc3305f9e315f4c40d917ba521
- Why sufficient / why not (one line): the token is verifiable onchain.
- 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 a service with the token is not confirmed.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no described service or payment mechanics.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): incentives/collateral/penalties based on BYTE are not confirmed.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no protocol economy other than the token.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): governance mechanics via the token are not confirmed.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no DAO/procedures in Tier‑1.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): since confirmed utility is absent, the token is easily replaceable (or not needed at all) for the “product”.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there are no protocol functions that require specifically BYTE.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://etherscan.io/token/0xde342a3e269056fc3305f9e315f4c40d917ba521 | the fact of the token’s existence, supply/decimals parameters |
| Tier‑1 | https://www.bytedog.ai/ | the project’s marketing positioning |
| Tier‑1 | — | No Tier‑1 source proving a real AI component (what exactly the AI does, a demo, metrics) was found in the reviewed sources |
| Tier‑2 | https://coinmarketcap.com/currencies/byte/ | reference links (not proof of technology) |
| Tier‑3 | — | — |
No comments to display
No comments to display