Edge Network
Edge Network (EDGE) — 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).
Edge Network — an AI/Compute | Infra project: a decentralized “cloud/supercloud” and an L1 (XE/Edge Protocol) for coordinating resources and rewards; token (symbol: EDGE).
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 network/platform of distributed resources (compute/CDN/DNS/storage, etc.) with its own L1 for accounting/rewards.
- Who it’s for: resource providers (hosts/nodes) and users/clients of cloud services.
- Why onchain/token: the token is used for purchasing services, staking/node contributions, rewards and governance; a 1:1 linkage $EDGE (ERC‑20) ↔ $XE (L1 coin) is claimed.
How it works (very briefly)
- The user does: purchases/uses Edge services (compute/CDN/DNS, etc.).
- The network does: allocates resources and serves requests via distributed nodes.
- The resource provider does: connects a node/host, provides resources and receives rewards.
- Where the blockchain is: the L1 is used for coordination, staking, governance and economic accounting (including burn).
- Token role: $EDGE/$XE are described as the network’s units of settlement and incentives for providers.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Edge Network |
| Also known as (aliases) | EDGE, XE Blockchain |
| Logo (logo) | ../assets/504_edge_logo.webp |
| Token symbol (ticker) | EDGE |
| Category | AI/Compute | Infra |
| 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 | 0x4ec1b60b96193a64acae44778e51f7bff2007831 |
| Token model (token_type) | utility (payments + staking + governance) |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | The wiki describes a 1:1 linkage $EDGE (ERC‑20) ↔ $XE (L1 coin); $XE is used for services/staking/governance/rewards. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | cloud infrastructure for AI workloads |
| Use‑case (use_case) | decentralized cloud compute/CDN |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 2 / token_score 3 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://edge.network |
| Docs | https://wiki.edge.network |
| GitHub | https://github.com/edge |
| Releases / Changelog | https://wiki.edge.network/getting-started/project-updates |
| Whitepaper | https://edge-blockchain.gitbook.io/edge-whitepaper |
| Roadmap | https://github.com/edge/wiki/blob/master/getting-started/project-roadmaps.md |
| Security advisories | https://github.com/orgs/edge/security |
| Explorer | https://etherscan.io/token/0x4ec1b60b96193a64acae44778e51f7bff2007831 |
| X | https://twitter.com/edgenetwork |
| Discord | https://discord.com/invite/3sEvuYJ |
| Telegram | https://t.me/edgenetwork |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/edge |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/edge/ |
General project overview
Edge describes a “decentralized cloud / supercloud” with a set of services (compute/CDN/DNS/storage/GPU, etc.) and a separate L1 (XE/Edge Protocol) for coordination and economic incentives. The wiki/whitepaper describe the elements of the L1, and the tokenomics — the role of $EDGE/$XE, node staking and governance processes.
Features/modules
- Network services: compute/CDN/DNS/storage/GPU (as product directions).
- XE blockchain / Edge Protocol: an L1 for coordination and economic accounting.
- Edge CLI: installation/connection of nodes via the CLI (described in the wiki).
Typical scenarios
- Scenario 1: a resource provider installs the Edge CLI and brings up a host → starts providing resources.
- Scenario 2: a user purchases services in the network → the network allocates resources → performs delivery/computation.
Getting started (wallet/network)
- What you need: an account/wallet for operations with $EDGE (ERC‑20) or for participation in the network via $XE (per the project’s description).
- Network/chain: Ethereum (the token) + XE Blockchain (per the description in the wiki/website).
- Fees: Ethereum fees for operations with the ERC‑20; within Edge Network, free transactions are claimed (the wiki has a caveat about the possible introduction of a fee via governance).
Architecture/tech (non‑AI)
- Components (per the whitepaper/wiki): the L1 (Edge Protocol), nodes/hosts (resource providers), staking and governance mechanisms.
- Participant roles: service users, resource providers (hosts), L1 validators/nodes.
- Where logic runs: service execution — distributed nodes; coordination/accounting/staking/governance — the onchain L1 layer and the associated token.
- Dependencies: the $EDGE ↔ $XE bridge is described in the wiki tokenomics.
Token/economics (expanded, no forecasts)
- Token utility (per the wiki): purchasing services, node staking, participation in governance, rewards.
- $EDGE/$XE linkage: $XE is the coin of the XE Blockchain, bridged 1:1 to Ethereum as $EDGE (ERC‑20).
- Burn: the tokenomics describes the burning of a share of network revenue (example: 75% revenue burned) and a link to the zero‑address in the XE explorer.
- Issuance/burn: the issuance/max supply parameters are not established per Tier‑1 (there are API endpoints, but we do not put them in the passport without explicit confirmation).
Governance
- Who makes decisions: the governance mechanism is described in the wiki; participation requires a stake in the network (per the tokenomics).
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: typical risks of a PoS network and risks of economic attacks; the wiki mentions a governance discussion of measures against flood attacks.
Project status and timeline
- Current status: mainnet (the token on Ethereum; the wiki has “mainnet releases” and CLI instructions for mainnet).
- Key releases/milestones: there is an archive of project updates (partially outdated) and weekly updates (see links_*).
- Roadmap: project roadmaps (see links_* Roadmap).
Ecosystem/integrations
- Integrations: —.
- Partners: listed on the website (see links_* Website) as “Integrations and partnerships”.
AI component of the project
- What is real AI here? AI/“autonomous AI agents” are mentioned in the positioning; no Tier‑1 evidence of a specific AI module (architecture/versions/metrics) was found.
- What is truly onchain? there is an ERC‑20 token contract on Ethereum and a described L1 (Edge Protocol / XE Blockchain) with staking/governance and economic rules.
- Why is a token needed? described as the means of purchasing services, staking, governance and rewards.
- Red flags (based on the information found): AI‑washing (AI is mentioned as part of the cloud’s marketing without metrics/architecture of an AI module); it is important to separate “a cloud for AI workloads” from “there is an own AI component”.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | medium | 2 |
| 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 Tier‑1 positioning mentions “autonomous AI agents” and an AI direction as part of the cloud’s use cases.
- Evidence: Tier‑1 — https://edge.network
- Why sufficient / why not (one line): This records intent/applicability, but does not prove the existence of the protocol’s own AI component.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): It is not established that the project has its own AI module/model with a described function.
- Evidence: Tier‑1 — https://edge.network
- Why sufficient / why not (one line): The mention of “AI” refers to workloads/the market and the product line, but not to a specific AI implementation.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No Tier‑1 demo/app demonstrating an AI component was found.
- Evidence: Tier‑1 — https://edge.network
- Why sufficient / why not (one line): Without an explicit demo for the AI part we do not raise the flag.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://edge.network
- Why sufficient / why not (one line): No reproducible set of metrics of an AI component was found in Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A tech description of AI models/versions/architecture is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): The whitepaper describes the L1 protocol, but gives no technical details of an AI component.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: EDGE ERC‑20 contract: 0x4ec1b60b96193a64acae44778e51f7bff2007831
- Evidence: Tier‑1 — https://etherscan.io/token/0x4ec1b60b96193a64acae44778e51f7bff2007831
- Why sufficient / why not (one line): The explorer confirms the onchain artifact (the token contract).
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: node staking, governance and economic rules (burn/revenue) on the XE Blockchain (per the wiki) + the L1 protocol (whitepaper).
- Evidence: Tier‑1 — https://wiki.edge.network/getting-started/edge-tokenomics ; https://edge-blockchain.gitbook.io/edge-whitepaper
- Why sufficient / why not (one line): Tier‑1 sources describe onchain mechanics beyond “just a token”.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established per Tier‑1 that the product breaks down without the blockchain (rather than operating as a centralized cloud service).
- Evidence: Tier‑1 — https://edge.network
- Why sufficient / why not (one line): OC_3=1 requires an explicit argument “impossible without onchain”; not found per Tier‑1.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, EDGE (ERC‑20), and a coin, $XE (L1), with a 1:1 linkage.
- Evidence: Tier‑1 — https://wiki.edge.network/getting-started/edge-tokenomics ; https://etherscan.io/token/0x4ec1b60b96193a64acae44778e51f7bff2007831
- Why sufficient / why not (one line): The wiki describes $XE/$EDGE, and the explorer confirms the $EDGE contract.
- 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): $XE/$EDGE are used to purchase Edge Network services.
- Evidence: Tier‑1 — https://wiki.edge.network/getting-started/edge-tokenomics ; https://edge.network
- Why sufficient / why not (one line): The tokenomics and the website describe payment for services with the token.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): A node contribution requires a stake; rewards and penalties for bad actors are described in the tokenomics.
- Evidence: Tier‑1 — https://wiki.edge.network/getting-started/edge-tokenomics
- Why sufficient / why not (one line): The tokenomics describes staking and penalization/burn for bad actors.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): Participation in governance requires a stake in the network (per the tokenomics).
- Evidence: Tier‑1 — https://wiki.edge.network/getting-started/edge-tokenomics
- Why sufficient / why not (one line): The tokenomics directly states that governance requires a stake and that changes to the tokenomics go through governance.
- 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): TK_4=1 requires an explicit argument that the token is replaceable without changing the network model; not found.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://edge.network | Positioning: decentralized cloud; the token is used for payments/staking/governance; mention of AI/agents as a use case. |
| Tier‑1 | https://edge-blockchain.gitbook.io/edge-whitepaper | Whitepaper: Edge Protocol as an L1, a PoS network (the protocol’s tech context). |
| Tier‑1 | https://wiki.edge.network/getting-started/edge-tokenomics | Tokenomics: $XE L1 coin ↔ $EDGE (ERC‑20) 1:1; services/staking/governance/burn. |
| Tier‑1 | https://etherscan.io/token/0x4ec1b60b96193a64acae44778e51f7bff2007831 | The EDGE token contract on Ethereum. |
| Tier‑2 | https://www.coingecko.com/en/coins/edge | Token profile/metadata (for reference). |
| Tier‑2 | https://coinmarketcap.com/currencies/edge/ | Token profile/metadata (for reference). |
No comments to display
No comments to display