Skip to main content

DeXe Protocol

DeXe Protocol (DEXE) — 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).

DeXe Protocol — a set of smart contracts (a “DAO constructor”) for creating and managing DAOs (governance, voting models, treasury, delegation, etc.). The DEXE token is described as a utility+governance token for the DeXe Protocol DAO and for treasury management.

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 open‑source library of smart contracts for assembling DAOs (gov pools, voting, treasury, delegation, proposal templates).
  • Who it’s for: teams/communities that need to quickly deploy DAO structures and onchain governance; DAO participants (voters/delegates/validators).
  • Why onchain/token: onchain is needed for trustless governance/treasury; the DEXE token is for governing the DeXe Protocol DAO and its treasury (governance/rewards/fees as described in the whitepaper).

How it works (very briefly)

  1. The user does: deploys a DAO/pool via factories and configures the governance rules.
  2. The system does: creates a set of DAO governance contracts (GovPool and related contracts), stores and executes decisions onchain.
  3. The user gets: a manageable DAO “core” (voting, proposal execution, treasury structures) and a transparent history of decisions.
  4. Where the blockchain is: the governance logic and the custody of funds/voting rights — onchain (smart contracts).
  5. Token role: DEXE is used as the governance token for the DeXe Protocol DAO (treasury management, rewards and other utility as described in the whitepaper/token page).

Quick links: AI thesis fit

Project passport

Field Value
Project name DeXe Protocol
Also known as (aliases) DeXe, DEXE
Logo (logo) ../assets/dexe_logo.svg
Token symbol (ticker) DEXE
Category DeFi | 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 0xde4EE8057785A7e8e800Db58F9784845A5C2Cbd6
Token model (token_type) utility (rewards + governance)
Max supply 96504599.336094511795478536 (DEXE)
Issuance fixed (Max Total Supply)
Tokenomics (tokenomics, brief) governance token for the DAO: voting/treasury/rewards; multichain (ERC‑20 + BEP‑20)
Governance DAO (DeXe Protocol DAO)
Admins/keys —
Audit yes
Bug bounty yes
Team (team) DeXe Protocol Association / contributors
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) DAO constructor + on-chain governance
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 3 / 1 / 2
Last verified 2026-02-10

General project overview

DeXe Protocol is described as an open‑source “DAO constructor” — a library of smart contracts and modules for building DAOs: different voting models, delegation, treasury structures, proposal templates and execution contracts. The technical documentation describes the architecture as a set of contract groups (core, factory, gov) and lists the roles of the contracts in creating and operating a governance pool.

Features/modules

  • Core contracts: the registry/settings and the basic constants of the system.
  • Factory contracts: creation of DAOs/pools and their registration/upgrades.
  • Gov contracts: GovPool (proposals/voting/execution), custody of funds for voting, the validators layer (two-stage voting), governance settings.
  • Treasury/governance token: DEXE is used for governing the DeXe Protocol DAO and the treasury (whitepaper/token page).

Typical scenarios

  • Scenario 1: a team/community deploys a DAO → configures the proposal/voting rules → gets an onchain governance process.
  • Scenario 2: a DAO participant delegates voting assets/participates in voting → influences decisions and may receive rewards (as described in the whitepaper).
  • Scenario 3: the DAO adopts and executes an onchain decision → changes parameters/distributes rewards/performs execution.

Getting started (wallet/network)

  • What you need: an EVM wallet and interaction with the DAO/contracts (via UI/scripts).
  • Network/chain: DeXe is deployed as a set of EVM contracts (including Ethereum; multichain is mentioned in the token docs).
  • Fees: gas fees of the respective EVM network (e.g., Ethereum).

Architecture/tech (non‑AI)

  • Components: core (registry/constants), factory (creation/upgrades), gov (DAO governance contracts) + auxiliary components (e.g., subgraphs per the docs).
  • Participant roles: DAO creators (deploy/config), governance participants (proposals/voting), delegates/experts, validators (if 2‑stage voting is enabled).
  • Where logic runs: onchain — DAO creation and governance logic/execution; offchain — UI/indexing (e.g., subgraph), discussions.
  • Dependencies: EVM networks, open‑source code and tooling (GitHub).

Token/economics (expanded, no forecasts)

  • Token utility: $DEXE is described as a utility+governance token for the DeXe Protocol DAO: voting and treasury management, rewards to active participants, “token fees” in certain functions (whitepaper).
  • Protocol necessity drivers: DEXE is needed for the governance of the DeXe Protocol DAO itself and for decision-making on utility/treasury.
  • Who pays fees: gas in the EVM network used (e.g., Ethereum).
  • Where fees go: network fees — to the network validators; protocol token fees (if applicable) — to the DeXe DAO Treasury (whitepaper).
  • Issuance/burn: the max total supply on Ethereum is recorded in the explorer as Max Total Supply; no separate inflation mechanism is recorded in Tier‑1.
  • Incentive mechanisms: rewards for governance participants (whitepaper).
  • Distribution: the token page states that earmarked allocations are deposited in the treasury (a general wording); a detailed schedule/vesting as a passport fact is not established.
  • Treasury: managed by the DeXe Protocol DAO (whitepaper “Token & Treasury”).

Governance

  • Who makes decisions: the DeXe Protocol DAO (governance proposals and voting by DEXE holders/delegates).
  • How protocol parameters change: via proposals, voting and onchain execution (conceptually — as described for the DAO/governance modules).
  • Where decisions are discussed/made: whitepaper + GitHub/Docs.
  • Keys/multisig: —.

Security and incidents

  • Audits: yes (see links_* → audit report(s)).
  • Bug bounty: yes (Immunefi; see links_*).
  • Incidents: —.
  • Threat model: risks of bugs in the governance/treasury smart contracts; upgradeability risks via ContractsRegistry/Beacon Proxy; risks of centralized UI/indexing.

Project status and timeline

  • Current status: mainnet.
  • Key releases/milestones: —.
  • Roadmap: see links_* (GitHub Projects).

Ecosystem/integrations

  • Integrations: EVM wallets; subgraphs (per the docs); EVM ecosystem infrastructure.
  • Partners: —.
  • Where it’s actually used: DAO structures and governance modules assembled from DeXe Protocol contracts.

AI component of the project

  • What is real AI here? According to Tier‑1 sources, DeXe is described as a DAO/governance protocol; an AI component at the protocol/product level is not confirmed in Tier‑1.
  • What is truly onchain? The core logic — DAO/governance smart contracts (GovPool and related contracts), the treasury and the execution of decisions onchain.
  • Why is a token needed? DEXE is described as a utility+governance token for governing the DeXe Protocol DAO and the treasury, as well as for rewards/fees in certain functions.
  • Red flags (based on the information found): AI‑washing — high risk if the project is marketed as AI without Tier‑1; onchain‑washing — low risk (the product = onchain contracts); token‑washing — medium risk (the utility is described, but the completeness of the token’s necessity for using the protocol by “third-party DAOs” is limited).

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 high 3
Token necessity low 1
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): no Tier‑1 declaration “about an AI intent” for DeXe Protocol was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the Tier‑1 focus is on DAO/governance and smart contracts.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): no Tier‑1 confirmation of AI functions/models in DeXe Protocol was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): a DAO constructor and governance are described, not AI.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demo of an “AI component” was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no AI artifact to demonstrate.
  • 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): There are no Tier‑1 AI quality metrics.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is no technical description of an AI model/versions, because the project is not about AI.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Tier‑1 describes the DAO contract architecture, without AI models.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum mainnet (the DeXe contracts/token are also mentioned as multichain ERC‑20 + BEP‑20).
  • Addresses/identifiers: DEXE ERC‑20 contract: 0xde4EE8057785A7e8e800Db58F9784845A5C2Cbd6
  • Evidence: Tier‑1 — https://etherscan.io/token/0xde4EE8057785A7e8e800Db58F9784845A5C2Cbd6 ; https://whitepaper.dexe.network/dexe-protocol-dao/token-and-treasury
  • Why sufficient / why not (one line): token&treasury describes the ERC‑20 address of the token; Etherscan confirms the onchain fact.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: DAO creation and governance logic (GovPool: proposals/voting/execution; custody of voting assets; the validators layer; governance settings).
  • Evidence: Tier‑1 — https://docs.dexe.network/ ; https://whitepaper.dexe.network/dexe-protocol-overview
  • Why sufficient / why not (one line): the Tier‑1 docs describe the contract groups and the roles of the governance contracts.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, trustless governance/execution and treasury transparency disappear; it turns into a centralized service.
  • Evidence: Tier‑1 — https://whitepaper.dexe.network/dexe-protocol-overview ; https://docs.dexe.network/
  • Why sufficient / why not (one line): the protocol is described as a library of DAO smart contracts; its point is onchain execution.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has the DEXE token (ERC‑20; also BEP‑20).
  • Evidence: Tier‑1 — https://whitepaper.dexe.network/dexe-protocol-dao/token-and-treasury
  • Why sufficient / why not (one line): the whitepaper lists DEXE as the governance token and gives the ERC‑20/BEP‑20 addresses.
  • 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 use of the protocol by “other DAOs” is described as free; the details of mandatory DEXE payments as a core requirement are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the Tier‑1 emphasis is on governance/treasury; the payment necessity of the token is not proven.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): DEXE staking/slashing as the base security of the protocol is not described in Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): governance/rewards are described, but not a slashing model.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): DEXE is used for voting and governance of the DeXe Protocol DAO (including treasury management).
  • Evidence: Tier‑1 — https://whitepaper.dexe.network/dexe-protocol-dao/token-and-treasury ; https://dexe.network/token
  • Why sufficient / why not (one line): Tier‑1 describes DEXE as the governance token for the DAO and the treasury.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of DEXE with an alternative governance mechanism is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): a Tier‑1 argument about full replaceability without loss of the governance model is required.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://whitepaper.dexe.network/dexe-protocol-overview DeXe Protocol as an open‑source DAO constructor (a library of contracts, governance mechanics, execution, etc.).
Tier‑1 https://docs.dexe.network/ the contract architecture (core, factory, gov) and the roles of GovPool/keeper/validator/settings; the existence of deployments/subgraphs.
Tier‑1 https://whitepaper.dexe.network/dexe-protocol-dao/token-and-treasury DEXE as a utility+governance token for the DeXe Protocol DAO; its purpose (vote/treasury/rewards/fees); the ERC‑20/BEP‑20 addresses.
Tier‑1 https://dexe.network/token a description of the DEXE token and its utility for the DAO; confirmation of multichain ERC‑20/BEP‑20.
Tier‑1 https://etherscan.io/token/0xde4EE8057785A7e8e800Db58F9784845A5C2Cbd6 the onchain parameters of the DEXE token (including Max Total Supply) and the contract address.
Tier‑1 https://github.com/dexe-network/DeXe-Protocol/ the source code of DeXe Protocol (contracts).
Tier‑2 https://immunefi.com/bug-bounty/dexeprotocol/information/ the bug bounty program (context).

No comments to display

Back to top