Skip to main content

LNDRY

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

LNDRY — a project on the Ethereum network (ERC‑20), token (symbol: LNDRY).

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 dApp and Telegram bot for mixing/hiding the direct link between transactions and a wallet address (per the project’s claim).
  • Who it’s for: users who need mixing/privacy for transfers.
  • Why onchain/token: the token is used for staking/reward mechanics (per the project’s claim); onchain records the state of the ERC‑20 token.

How it works (very briefly)

  1. The user does: uses the dApp or Telegram bot to initiate mixing/a transfer.
  2. The system does: per the project’s claim, mixes transactions with others to make tracing more difficult.
  3. The user gets: a transfer with reduced “from → to” linkability (per the project’s claim).
  4. Where the blockchain is: onchain — the ERC‑20 token and related public contract data.
  5. Token role: the token is used in staking/reward mechanics (per the project’s claim).

Quick links: AI thesis fit

Project passport

Field Value
Project name LNDRY
Also known as (aliases) LNDRY
Logo (logo) —
Token symbol (ticker) LNDRY
Category 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 0x338be6a72db57a239f0d71d0ec4e5b1e38762e9f
Token model (token_type) —
Max supply 10 000 000
Issuance fixed
Tokenomics (tokenomics, brief) Buy/Sell tax: 5% (per the project’s claim).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI Mix + Bridge bot
Use‑case (use_case) transaction mixing/privacy
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

LNDRY is positioned as an ecosystem for crypto transaction privacy with a dApp and Telegram bot for mixing. The project’s Tier‑1 sources also claim future components (for example, a privacy DEX and staking), but implementation details require separate verification.

Features/modules

  • A dApp for mixing (per the project’s claim).
  • A Telegram bot for mixing (per the project’s claim).
  • Planned components: a privacy DEX and staking (marked as coming soon).

Typical scenarios

  • Scenario 1: a user uses the dApp for mixing and receives a transfer with lower traceability (per the project’s claim).
  • Scenario 2: a user uses the Telegram bot for mixing (per the project’s claim).

Getting started (wallet/network)

  • What you need: a wallet and access to the dApp or Telegram.
  • Network/chain: Ethereum (ERC‑20).
  • Fees: not found (check in the project’s Tier‑1 docs).

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token contract; dApp; Telegram bot (per the project’s claim).
  • Participant roles: users.
  • Where logic runs: onchain — the token; the rest of the mixing/bot logic — not established (no Tier‑1 confirmation found).
  • Dependencies: Ethereum RPC, web interface; the rest — not established.

Token/economics (expanded, no forecasts)

  • Token utility: token staking with returns from mixing operation fees is claimed (coming soon).
  • Protocol necessity drivers: not established (only general claims were found in Tier‑1).
  • Who pays fees: not established (no Tier‑1 confirmation found).
  • Where fees go: it is claimed that staking returns are linked to mixing operation fees.
  • Issuance/burn: fixed supply (10 000 000).
  • Security/incentive mechanisms: staking is claimed (coming soon).
  • Distribution and token issuance schedule: not found (no Tier‑1 confirmation identified).
  • Treasury: not found (no Tier‑1 confirmation identified).

Governance

  • Who makes decisions: not found (no Tier‑1 confirmation identified).
  • How protocol parameters change: not found (no Tier‑1 confirmation identified).
  • Where decisions are discussed/made: not found (no Tier‑1 confirmation identified).
  • Keys/multisig: not found (no Tier‑1 confirmation identified).

Security and incidents

  • Audits: not found (no Tier‑1 confirmation identified).
  • Bug bounty: not found (no Tier‑1 confirmation identified).
  • Incidents: not found (no Tier‑1 confirmation identified).
  • Threat model: not established; for mixing services, it is important to double‑check the risk of blocking/censorship/centralization and actual privacy guarantees.

Project status and timeline

  • Current status: mainnet (the ERC‑20 token on Ethereum; working links to the dApp/bot are claimed by the project).
  • Key releases/milestones: not found (no Tier‑1 confirmation identified).
  • Roadmap: stages (Stage 1–3) are claimed on the project website; exact task statuses require re‑checking.

Ecosystem/integrations

  • Integrations: dApp, Telegram bot (Tier‑1 links in links_*).
  • Partners: not found (no Tier‑1 confirmation identified).
  • Where it’s actually used: not established; actual volumes and terms of use require separate verification.

AI component of the project

  • What is real AI here? Only a mention of an AI bot in the roadmap (intent) was found in Tier‑1 sources. A working AI component and its quality are not confirmed per Tier‑1.
  • What is truly onchain? The ERC‑20 token and its contract on Ethereum are confirmed onchain.
  • Why is a token needed? Staking/reward mechanics linked to mixing operation fees are claimed in Tier‑1 sources.
  • Red flags (based on the information found): absence of verifiable technical details on “AI” and mixing mechanics; the privacy architecture, degree of centralization, as well as tokenomics and distribution parameters need to be double‑checked.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
Token necessity low 1
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 roadmap claims “LNDRY AI Mix & Bridge Bot”.
  • Evidence: Tier‑1 — https://lndry.xyz/
  • Why sufficient / why not (one line): This is an intent/plan; no verifiable description of a working AI component was found.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0 Claim (one line): What exactly the LNDRY AI component does is not established in Tier‑1 sources.
  • Evidence: Tier‑1 — https://lndry.xyz/ ; https://docs.lndry.xyz/
  • Why sufficient / why not (one line): 1 requires a specific description of AI features (inputs/outputs/boundaries), which was not found.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0 Claim (one line): No demo specifically of AI features (not mixing in general) was found per Tier‑1.
  • Evidence: Tier‑1 — https://lndry.xyz/ ; https://docs.lndry.xyz/
  • Why sufficient / why not (one line): A mixing demo is not a demo of an AI component; 1 requires a reproducible example of AI features.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0 Metrics: not found (no Tier‑1 confirmation identified). Context (version/date/how measured): not found (no Tier‑1 confirmation identified).
  • Evidence: Tier‑1 — https://docs.lndry.xyz/
  • Why sufficient / why not (one line): There are no quantitative metrics/benchmarks for the AI component.
  • 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 component (architecture/versions) was not found in Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.lndry.xyz/
  • Why sufficient / why not (one line): 1 requires the architecture/versions/boundaries of the model or system.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0x338be6a72db57a239f0d71d0ec4e5b1e38762e9f
  • Evidence: Tier‑1 — https://lndry.xyz/ ; https://etherscan.io/token/0x338be6a72db57a239f0d71d0ec4e5b1e38762e9f
  • Why sufficient / why not (one line): The contract address is given on the project website and is verifiable via an onchain explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0 What useful logic is onchain: No confirmation of onchain logic (Tier‑1), other than the token, was found.
  • Evidence: Tier‑1 — https://docs.lndry.xyz/ ; https://etherscan.io/token/0x338be6a72db57a239f0d71d0ec4e5b1e38762e9f
  • Why sufficient / why not (one line): 1 requires described and observable onchain logic of the product (access/accounting/rules), not just the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0 “Replace the blockchain” test: it is not established (Tier‑1) that the product breaks down without the blockchain; some of the logic can probably be implemented offchain.
  • Evidence: Tier‑1 — https://docs.lndry.xyz/
  • Why sufficient / why not (one line): 1 requires an explicit argument “without onchain a key property breaks down”, which was not found.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a claimed token, LNDRY (ERC‑20).
  • Evidence: Tier‑1 — https://lndry.xyz/ ; https://etherscan.io/token/0x338be6a72db57a239f0d71d0ec4e5b1e38762e9f
  • Why sufficient / why not (one line): The website gives the ticker and contract address.
  • 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): Mandatory “payment for the service with the token” is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://docs.lndry.xyz/
  • Why sufficient / why not (one line): No clear description of pay‑per‑use with the token was found in the available Tier‑1 materials.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): LNDRY staking with returns from mixing operation fees is claimed (incentives/rewards).
  • Evidence: Tier‑1 — https://lndry.xyz/
  • Why sufficient / why not (one line): The project website contains a description of staking and its link to mixing operation fees.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0 Claim (one line): The use of the token for governance is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://docs.lndry.xyz/
  • Why sufficient / why not (one line): 1 requires an explicit governance mechanism (voting/parameters), which was not found.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0 Claim (one line): The replaceability of the token (USDC/subscription) is not established (no Tier‑1 confirmation identified).
  • Evidence: Tier‑1 — https://docs.lndry.xyz/
  • Why sufficient / why not (one line): 1 requires an argument and a design decision that the token does not perform critical functions.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://lndry.xyz/ Product positioning (dApp/Telegram bot for mixing), LNDRY ticker, tokenomics parameters (total supply, tax), roadmap (including an AI bot as intent), contract address.
Tier‑1 https://docs.lndry.xyz/ Description of positioning and high‑level descriptions of operation (privacy shield, dApp/Telegram bot).
Tier‑1 https://etherscan.io/token/0x338be6a72db57a239f0d71d0ec4e5b1e38762e9f Onchain fact of the existence of the ERC‑20 token contract on the Ethereum network.
Tier‑1 https://dapp.lndry.xyz/ The presence of the claimed dApp (exact features require separate verification).
Tier‑1 https://t.me/EthLaundryBot The presence of the claimed Telegram bot (exact features require separate verification).

No comments to display

Back to top