Skip to main content

Reddio

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

Reddio — an AI/Compute | Infra project with the RDO token (ERC‑20; Ethereum). The project describes itself as a Layer‑2 with a CUDA‑compatible Parallel EVM and a P2P GPU network.

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 infrastructure L2 project for accelerating the execution of EVM transactions (parallel execution, GPU acceleration) and supporting “high‑performance” dApp scenarios.
  • Who it’s for: developers and projects that need a high‑performance EVM‑compatible execution layer (DeFi/games/AI dApps).
  • Why onchain/token: the RDO token is described as gas/staking/validation/burn/governance; the onchain part — the L2 execution layer itself and its economic mechanics.

How it works (very briefly)

  1. The user does: sends transactions/interacts with applications on the Reddio network.
  2. The system does: executes transactions in the L2, claiming a parallel EVM and the use of GPU resources.
  3. The user gets: cheaper/faster interactions compared to L1 (as claimed).
  4. Where the blockchain is: logic and state — on the L2; settlement/anchoring — via integration with Ethereum (per the whitepaper).
  5. Token role: RDO is used as gas and for staking (earn/validate), the burn mechanism and governance (per the docs).

Quick links: AI thesis fit

Project passport

Field Value
Project name Reddio
Also known as (aliases) Reddio zkEVM; RDO
Logo (logo) ../assets/324_reddio_logo.png
Token symbol (ticker) RDO
Category AI/Compute | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoA (Proof of Authority)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x57240C3E140f98abe315CA8E0213c7a77F34A334
Token model (token_type) utility (governance)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Per the docs: gas on the network; “earn/validate” staking; burn of a share of fees; governance.
Governance governance (as claimed)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) L2 for AI dApps (Parallel EVM + GPU network)
Use‑case (use_case) high-performance execution layer
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 3 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

Reddio describes itself as a Layer‑2 solution for Ethereum that focuses on high performance through parallel execution of the EVM and the use of GPU acceleration (CUDA‑compatible Parallel EVM), as well as a P2P GPU network and a modular sequencer SDK. The whitepaper separately emphasizes applicability to high‑load scenarios, including DeFi, games and AI dApps.

Features/modules

  • Parallel execution + state optimizations: parallel processing of transactions and optimizations of state storage/access (whitepaper).
  • CUDA‑compatible Parallel EVM: GPU acceleration of EVM opcode/batch execution is claimed (whitepaper).
  • P2P GPU network: a network of nodes providing GPU resources is claimed (whitepaper).
  • Modular sequencer SDK: an SDK for customizing L2/L3 is claimed (whitepaper).

Typical scenarios

  • Scenario 1: a dApp moves its load to the L2 → gets higher throughput and lower latency (as claimed).
  • Scenario 2: a developer uses the SDK/execution layer for a custom rollup scenario (as claimed).

Getting started (wallet/network)

  • What you need: an EVM wallet and access to the Reddio network (onboarding details are in the project’s docs).
  • Network/chain: the project describes itself as an L2 on Ethereum.
  • Fees: per the docs, gas is paid in the RDO token.

Architecture/tech (non‑AI)

  • Components: L2 execution layer (parallel EVM) + sequencer/SDK + confirmation/anchoring via Ethereum (per the whitepaper).
  • Where logic runs: execution and state transitions — in the L2; publication/settlement — via the L1 integration (per the description).

Token/economics (expanded, no forecasts)

  • Gas: RDO is used for fees on the network.
  • Stake to earn / validate: staking for participation in revenue distribution and for validators of the PoA model.
  • Burn: the docs describe burning of a part of fees.
  • Governance: voting rights on parameters/upgrades are claimed.

Security and incidents

  • Security advisories: there is a GitHub Security Advisories section in the repository.
  • Audits/bug bounty: no Tier‑1 confirmations were found.

AI component of the project

  • What is real AI here? In Tier‑1 sources, AI mostly appears as a target use‑case (AI dApps, on‑chain AI), not as a specific built‑in “AI product” with metrics/a model.
  • What is truly onchain? The L2 execution layer itself and the network’s onchain economy; the RDO token and its mechanics (gas/stake/burn/governance).
  • Why is a token needed? Per the docs: gas, staking for earn/validate, burn of a part of fees, governance.
  • Red flags (what to double‑check):
    • Claims about on‑chain AI and the GPU network require verification against actual releases/launched components (via Tier‑1 artifacts: releases/code/launched components).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity high 3
Token necessity high 3
Evidence Tier‑1 present 3
Details

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the project positions the network as infrastructure for AI‑driven solutions and on‑chain AI use‑cases.
  • Evidence: Tier‑1 — https://docs.reddio.com/zkevm/tokeneconomy/introduction
  • Why sufficient / why not (one line): there is Tier‑1 intent/applicability to AI, but no proof of an “AI module” as a product.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): specific AI functionality (model/task) as part of the product is not described.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Tier‑1 describes AI as a use‑case, not as an implemented AI component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demo specifically of the AI component was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no recorded Tier‑1 “what you can touch” for the AI part.
  • 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 model metrics are not applicable: AI is described as a use‑case.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the Tier‑1 tech description relates to the L2 architecture, not to an AI model/version.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the AI_4 criterion about an AI component is not met.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (L1 token contract); the product — an L2 per the project’s description
  • Addresses/identifiers: RDO token contract 0x57240C3E140f98abe315CA8E0213c7a77F34A334
  • Evidence: Tier‑1 — https://etherscan.io/token/0x57240C3E140f98abe315CA8E0213c7a77F34A334
  • Why sufficient / why not (one line): the onchain fact of the contract is verifiable directly.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: the L2 execution layer (parallel EVM) as the product.
  • Evidence: Tier‑1 — https://static.reddio.com/REDDIO%20WHITEPAPER.pdf
  • Why sufficient / why not (one line): the whitepaper describes the L2 architecture and transaction execution as the key functionality.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain execution/settlement the L2 loses its meaning as an execution layer for dApps.
  • Evidence: Tier‑1 — https://static.reddio.com/REDDIO%20WHITEPAPER.pdf
  • Why sufficient / why not (one line): the product is a blockchain network/L2; the “trustless execution + settlement” property relies on onchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the RDO token exists.
  • Evidence: Tier‑1 — https://docs.reddio.com/zkevm/tokeneconomy/tokenutilities
  • Why sufficient / why not (one line): the docs describe the token’s utility on the network.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): RDO is used as gas for network operations.
  • Evidence: Tier‑1 — https://docs.reddio.com/zkevm/tokeneconomy/tokenutilities
  • Why sufficient / why not (one line): the “Transaction Fees” utility is described explicitly.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): RDO staking for earn/validate (validators/miners).
  • Evidence: Tier‑1 — https://docs.reddio.com/zkevm/tokeneconomy/tokenutilities
  • Why sufficient / why not (one line): the “Stake to Earn / Stake to Validate” utility is described explicitly.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): governance rights for RDO holders.
  • Evidence: Tier‑1 — https://docs.reddio.com/zkevm/tokeneconomy/tokenutilities
  • Why sufficient / why not (one line): the “Governance” utility is described explicitly.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token with another asset is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 statement about replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://static.reddio.com/REDDIO%20WHITEPAPER.pdf Description of the L2 architecture (Parallel EVM, GPU network, SDK) and the integration with Ethereum.
Tier‑1 https://docs.reddio.com/zkevm/tokeneconomy/introduction Positioning: an L2 for DeFi/games/AI use‑cases + the role of RDO in the ecosystem.
Tier‑1 https://docs.reddio.com/zkevm/tokeneconomy/tokenutilities Token utility: gas, stake, burn, governance.
Tier‑1 https://etherscan.io/token/0x57240C3E140f98abe315CA8E0213c7a77F34A334 The RDO token contract on Ethereum.

No comments to display

Back to top