Dtravel / TRVL
Dtravel / TRVL (TRVL) — 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).
Dtravel — a Travel / Web3 project: a peer‑to‑peer direct booking ecosystem for housing rentals. Per the official documents, the ecosystem’s infrastructure is built around Nite Protocol (an open standard + an onchain data/transaction layer), while the TRVL token is used for incentives, payments/discounts and governance (Tier‑1 docs/website). AI component is not described in Tier‑1, so per the DecAIHub methodology DecAI Fit = 0/6 (ai_score = 0).
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 for direct booking of housing without OTA marketplaces (per the Dtravel documents).
- Who it’s for: operators/hosts (who create direct booking websites and listings) and travelers (who search and book directly).
- Why onchain/token: the TRVL token exists onchain (ERC‑20) and is used for rewards/incentives and governance; the AI thesis is not confirmed.
How it works (very briefly)
- The user does: a traveler searches for housing and books directly; an operator connects listings/creates a website.
- The system does: provides the direct booking infrastructure and, per the docs, links the infrastructure components with Nite Protocol (an onchain data/standard layer).
- The user gets: a booking directly with the operator and rewards/discounts via TRVL (claim).
- Where the blockchain is: the TRVL token on Ethereum is confirmed; the documents describe the Nite Protocol onchain layer, but the protocol’s contract addresses are not provided in the extracted Tier‑1.
- Token role (if any): TRVL is used as a utility token for rewards/network growth and for governance (Snapshot).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Dtravel / TRVL |
| Also known as (aliases) | TRVL, Dtravel DAO, Nite Protocol |
| Logo (logo) | ../assets/286_trvl_logo.svg |
| Token symbol (ticker) | TRVL |
| Category | Travel | Web3 | 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 | 0xd47bdf574b4f76210ed503e0efe81b58aa061f3d |
| Token model (token_type) | utility (governance) |
| Max supply | 1,000,000,000 TRVL (Etherscan Max Total Supply) |
| Issuance | fixed max supply (per the explorer data) |
| Tokenomics (tokenomics, brief) | TRVL is used for reward distributions for the sake of network growth; governance votes via Snapshot (docs). |
| Governance | DAO (claim; governance docs) |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | direct booking + rewards token |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | 0 / 1 / 2 / 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | http://www.dtravel.com/ |
| Docs | https://docs.dtravel.com/ |
| GitHub | https://github.com/NiteProtocol |
| Releases / Changelog | — |
| Whitepaper | https://docs.dtravel.com/papers/dtravel-litepaper |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0xd47bdf574b4f76210ed503e0efe81b58aa061f3d |
| X | https://twitter.com/DtravelDAO |
| Discord | https://discord.gg/dtravel |
| Telegram | https://t.me/dtravelcommunity |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/trvl |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/trvl/ |
General project overview
Dtravel describes itself as a peer‑to‑peer ecosystem for vacation rentals that “facilitates peer‑to‑peer bookings” and gives operators tools for direct booking websites/listings (docs). In the documents, Dtravel also highlights Nite Protocol as an open standard + an approach to “bringing vacation rental data on‑chain” (docs). The ecosystem is “powered by TRVL” — a utility token that is used for network growth incentives and governance (docs).
Features/modules
- Direct booking infrastructure: tools for operators (listings/websites) and for travelers (search/booking) (docs).
- Nite Protocol (claim): an open standard + an onchain data/smart contract layer (Nite Protocol litepaper).
- TRVL rewards layer: incentives for contributing to the network; pay‑utility in the form of payment in TRVL/discounts (website + token economics).
- Governance: voting via Snapshot (governance docs).
Typical scenarios
- Scenario 1 (traveler): searches for housing → books directly with the operator → (claim) can pay in TRVL and receive a 10% giveback/discount (website).
- Scenario 2 (operator): connects listings/creates a direct booking website → participates in the network and (claim) in growth campaigns incentivized with TRVL (docs token economics).
- Scenario 3 (TRVL holder): participates in governance votes on Snapshot (docs).
Getting started (wallet/network)
- What you need: web access to the Dtravel products; an EVM wallet for TRVL.
- Network/chain: Ethereum mainnet (TRVL).
- Fees: Ethereum gas for onchain operations with the token; booking/product operations are largely offchain.
Architecture/tech (non‑AI)
- Components: offchain Dtravel applications/services + the onchain TRVL token + (claim) the Nite Protocol onchain layer (docs).
- Participant roles: travelers; operators/hosts; token holders; DAO members.
- Where logic runs: onchain — the TRVL token; the protocol’s onchain logic is described conceptually, but without contract addresses in the extracted Tier‑1; the application/billing/UX — offchain.
- Dependencies: Ethereum; the Dtravel infrastructure; external payment rails (fiat/crypto) — per the docs.
Token/economics (expanded, no forecasts)
- Token utility: rewards/incentives for network growth (token economics/why critical); pay‑utility (payment in TRVL and a 10% giveback/discount) (website); governance utility via Snapshot (governance docs).
- Protocol necessity drivers: the token is described as a “vehicle” for bootstrapping adoption and ownership/votes (why critical).
- Who pays fees: users pay Ethereum gas on TRVL transfers; network fees go to Ethereum validators.
- Where fees go: — (apart from network fees).
- Issuance/burn: max total supply 1,000,000,000 (Etherscan).
- Security/incentive mechanisms: incentives via reward distributions and campaigns (token economics).
- Distribution and token issuance schedule: per Tier‑1, no specific allocations/vesting in numbers are provided.
- Treasury: — (addresses/control not extracted).
Governance
- Who makes decisions: TRVL holders participate in votes on Snapshot (docs).
- How protocol parameters change: via governance proposals/votes (in general terms; without specific contracts in the extracted Tier‑1).
- Where decisions are discussed/made: Snapshot (docs).
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: a substantial share of the system (search/booking/payment UX) is probably offchain; the protocol’s onchain part is described without addresses; risks of centralized dependence on the operator/infrastructure.
Project status and timeline
- Current status: the website and docs are available; the TRVL token exists on Ethereum; the governance guide has been updated (dated).
- Key releases/milestones: the litepaper states “Updated October 14, 2024” (the document evolves).
- Roadmap: — (not extracted).
Ecosystem/integrations
- Integrations: Ethereum (TRVL); Snapshot for voting; (claim) Nite Protocol as an open standard.
- Partners: —.
- Where it’s actually used: the utility is described in the docs; the onchain token is confirmed by the explorer.
AI component of the project
- What is real AI here? in the extracted Tier‑1 there is no description of an AI component/ML models/agents.
- What is truly onchain? the TRVL token on Ethereum; the documents describe the Nite Protocol onchain approach without contract addresses.
- Why is a token needed? rewards/network growth and governance utility (Snapshot).
- Red flags (based on the information found): the AI thesis is not confirmed (ai_score=0); most of the product may be offchain; in the extracted Tier‑1 there are no contract addresses for Nite Protocol/the infrastructure (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 | absent | 0 |
| Onchain necessity | low | 1 |
| Token necessity | medium | 2 |
| Evidence | Tier‑1 present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): in the extracted Tier‑1 there is no roadmap/declaration of intent regarding an AI component.
- Evidence: Tier‑1 — https://docs.dtravel.com/ ; http://www.dtravel.com/
- Why sufficient / why not (one line): AI intent requires an explicit Tier‑1 item/update about AI.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): AI features are not described.
- Evidence: Tier‑1 — https://docs.dtravel.com/
- Why sufficient / why not (one line): there is no AI description in the documentation.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): there is no demo of an AI component (the AI component is not described).
- Evidence: Tier‑1 — https://docs.dtravel.com/
- Why sufficient / why not (one line): not applicable.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —.
- Context (version/date/how measured): —.
- Evidence: Tier‑1 — https://docs.dtravel.com/
- Why sufficient / why not (one line): there are no AI quality metrics.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a technical description of AI/ML is absent.
- Evidence: Tier‑1 — https://docs.dtravel.com/
- Why sufficient / why not (one line): not applicable.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: TRVL token: 0xd47bdf574b4f76210ed503e0efe81b58aa061f3d
- Evidence: Tier‑1 — https://etherscan.io/token/0xd47bdf574b4f76210ed503e0efe81b58aa061f3d
- Why sufficient / why not (one line): the explorer confirms the contract and max total supply.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: Nite Protocol describes blockchain/smart contracts conceptually, but contract/deployment addresses are not provided in the extracted Tier‑1.
- Evidence: Tier‑1 — https://docs.dtravel.com/papers/nite-protocol-litepaper
- Why sufficient / why not (one line): without addresses/contracts we do not count OC_2.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: a direct booking platform can be implemented in a centralized way; onchain criticality is not proven in the extracted Tier‑1.
- Evidence: Tier‑1 — https://docs.dtravel.com/
- Why sufficient / why not (one line): onchain is claimed as part of the vision/infrastructure, without proof that “without the blockchain it breaks down”.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a utility token, TRVL.
- Evidence: Tier‑1 — https://docs.dtravel.com/ ; https://etherscan.io/token/0xd47bdf574b4f76210ed503e0efe81b58aa061f3d
- Why sufficient / why not (one line): the token is confirmed onchain and described in the docs.
- 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): TRVL is used to pay for stays/bookings with an additional benefit (a 10% giveback/discount) on the Dtravel network.
- Evidence: Tier‑1 — http://www.dtravel.com/
- Why sufficient / why not (one line): the website directly describes “Pay for stays with TRVL… save 10%”.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): TRVL is described as a tool for bootstrapping adoption: rewards for bookings/referrals/participant contributions.
- Evidence: Tier‑1 — https://docs.dtravel.com/papers/trvl-token-economics/why-is-trvl-critical-to-the-success-of-dtravel ; https://docs.dtravel.com/papers/trvl-token-economics
- Why sufficient / why not (one line): the documents describe the role of rewards as a key mechanism of network growth.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): governance votes take place on Snapshot using TRVL held in wallets (including staked).
- Evidence: Tier‑1 — https://docs.dtravel.com/papers/dtravel-dao-governance/how-community-members-can-vote
- Why sufficient / why not (one line): the governance mechanism and platform are specified explicitly.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): rewards/discounts and governance can be implemented via offchain loyalty/stablecoins/accounting without its own token; the protocol‑level necessity of the token is not proven by Nite Protocol contract addresses.
- Evidence: Tier‑1 — http://www.dtravel.com/ ; https://docs.dtravel.com/papers/nite-protocol-litepaper
- Why sufficient / why not (one line): the onchain criticality and the uniqueness of the token are not confirmed by protocol artifacts in the extraction.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.dtravel.com/ | Definition of the Dtravel ecosystem, its link with Nite Protocol and the role of TRVL. |
| Tier‑1 | https://docs.dtravel.com/papers/dtravel-litepaper | Litepaper: context, goals, description of the ecosystem. |
| Tier‑1 | https://docs.dtravel.com/papers/nite-protocol-litepaper | Nite Protocol: blockchain/smart contracts as part of the design (without addresses). |
| Tier‑1 | https://docs.dtravel.com/papers/trvl-token-economics | TRVL token economics: the purpose of the token and the reward logic. |
| Tier‑1 | https://docs.dtravel.com/papers/trvl-token-economics/why-is-trvl-critical-to-the-success-of-dtravel | Why TRVL is critical: rewards and bootstrapping adoption. |
| Tier‑1 | https://docs.dtravel.com/papers/dtravel-dao-governance/how-community-members-can-vote | Governance: Snapshot and voting with token balances. |
| Tier‑1 | http://www.dtravel.com/ | Website: TRVL utility (“pay with TRVL”, 10% giveback/discount). |
| Tier‑1 | https://etherscan.io/token/0xd47bdf574b4f76210ed503e0efe81b58aa061f3d | The onchain TRVL token (Ethereum), max supply and contract. |
No comments to display
No comments to display