EncrypGen
EncrypGen (DNA) — 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).
EncrypGen — a project with the DNA token (ERC‑20, Ethereum), positioning itself as a data platform/marketplace (genomics). Per Tier‑1 sources, no confirmation of the existence of an AI component was found (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 project/service that claims a marketplace for data (genomics) using the DNA token (claimed in Tier‑1 on the website).
- Who it’s for: users who own data, and data buyers (researchers/companies) — claimed.
- Why onchain/token: Tier‑1: DNA tokens are described as a means of purchasing genomic data and related products/services in the Gene‑Chain Marketplace; onchain fact: the DNA token contract (ERC‑20, Ethereum).
How it works (very briefly)
- The user does: uploads/manages data in the service (claimed).
- The system does: organizes access/search/purchase of data (claimed).
- The user gets: the ability to sell/buy access to data (claimed).
- Where the blockchain is: the onchain artifact of the DNA token on Ethereum is confirmed; the rest of the logic — not established per Tier‑1.
- Token role (if any): Tier‑1: DNA tokens are described as a means of purchasing genomic data and related products/services in the Gene‑Chain Marketplace.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | EncrypGen |
| Also known as (aliases) | Gene‑Chain; DNA token |
| Logo (logo) | ../assets/542_encrypgen_logo.svg |
| Token symbol (ticker) | DNA |
| Category | Infra |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0xef6344de1fcfC5F48c30234C16c1389e8CdC572C |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | data marketplace (genomics) |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | 0 / 1 / 1 / 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.encrypgen.com/ |
| Docs | https://www.encrypgen.com/ |
| GitHub | https://github.com/encrypgen |
| Releases / Changelog | https://encrypted-genes.medium.com/ |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0xef6344de1fcfC5F48c30234C16c1389e8CdC572C |
| X | https://twitter.com/encrypgen |
| Discord | — |
| Telegram | https://t.me/encrypgentrading |
| Medium | https://encrypted-genes.medium.com/ |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/encrypgen |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/encrypgen/ |
General project overview
In Tier‑1 sources, EncrypGen is described as a service/platform around data (genomics) and the DNA token.
Per Tier‑1 sources, no confirmation of the existence of an AI component (metrics/architecture/demo) was found, so the AI flags are conservatively set to 0.
Features/modules
- Data marketplace/exchange (claimed).
- The DNA token as an element of the economy/payment (claimed; necessity not established).
Typical scenarios
- Scenario 1: the user publishes/manages data → gets the opportunity to monetize (claimed).
- Scenario 2: a data buyer searches for/purchases access → receives data/access (claimed).
Getting started (wallet/network)
- What you need: an account/access to the service (details not established).
- Network/chain: Ethereum (the DNA token — ERC‑20).
- Fees: Ethereum network fees for onchain operations; other service fees — not established.
Architecture/tech (non‑AI)
- Components: the DNA token contract on Ethereum + offchain components of the service (details not established).
- Participant roles: users as data providers and data buyers (claimed).
- Where logic runs: onchain is confirmed only at the token level; the rest — not established.
- Dependencies: — (not found per Tier‑1).
Token/economics (expanded, no forecasts)
- Token utility: Tier‑1: DNA tokens can be used to purchase genomic data and related products/services in the Gene‑Chain Marketplace.
- Protocol necessity drivers: per Tier‑1, the token is described as the currency/means of purchase in the marketplace; the “mandatory nature” of the token as the only payment mechanism is not established.
- Who pays fees: users for transactions on the Ethereum network (gas).
- Where fees go: to the Ethereum network validators (gas); the project’s protocol fees — not established.
- Issuance/burn: — (not established).
- Security/incentive mechanisms: — (not established).
- Distribution and token issuance schedule: — (not established).
- Treasury: — (not established).
Governance
- Who makes decisions: — (not established).
- How protocol parameters change: — (not established).
- Where decisions are discussed/made: — (not established).
- Keys/multisig: — (not established).
Security and incidents
- Audits: — (not found per Tier‑1).
- Bug bounty: — (not found per Tier‑1).
- Incidents: — (not found per Tier‑1).
- Threat model: privacy/data risks require separate verification; for the token there is a Tier‑1 claim about its use as a means of purchase in the marketplace.
Project status and timeline
- Current status: — (not established).
- Key releases/milestones: — (not established).
- Roadmap: —.
Ecosystem/integrations
- Integrations: — (not found per Tier‑1).
- Partners: — (not found per Tier‑1).
- Where it’s actually used: — (not found per Tier‑1).
AI component of the project
- What is real AI here? Per Tier‑1 sources, no confirmation of an AI component (intent/reality) was found, so ai_score = 0.
- What is truly onchain? The DNA token (ERC‑20) on Ethereum is confirmed; other onchain components are not established.
- Why is a token needed? Tier‑1: DNA tokens are described as a means of purchasing genomic data and related products/services in the Gene‑Chain Marketplace.
- Red flags (based on the information found): AI‑washing risk (if AI is claimed outside Tier‑1); the onchain component other than the token is not confirmed per Tier‑1; the details of the protocol economy require separate verification per Tier‑1.
DecAI Fit component summary
- DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
| Component | Level | Score |
|---|---|---|
| AI reality | no Tier‑1 data | 0 |
| Onchain necessity | low | 1 |
| Token necessity | low | 1 |
| Evidence | Tier‑1 partial | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): No Tier‑1 claim about AI intentions/applicability was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a Tier‑1 record of intent we set 0.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): AI functionality is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): demos/examples of AI operation are not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no Tier‑1 demo → 0.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found.
- Context (version/date/how measured): not found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): metrics not found → 0.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a tech description of the AI component is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: the DNA token (ERC‑20): 0xef6344de1fcfC5F48c30234C16c1389e8CdC572C
- Evidence: Tier‑1 — https://etherscan.io/token/0xef6344de1fcfC5F48c30234C16c1389e8CdC572C
- Why sufficient / why not (one line): the existence of the onchain artifact is confirmed in the block explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established (per Tier‑1 only the token is confirmed).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established what breaks down without onchain (per Tier‑1).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, DNA (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0xef6344de1fcfC5F48c30234C16c1389e8CdC572C
- Why sufficient / why not (one line): the existence of the token is confirmed by the 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): Tier‑1: DNA tokens are described as a means of purchasing genomic data and related products/services in the Gene‑Chain Marketplace.
- Evidence: Tier‑1 — https://encrypgen.com/
- Why sufficient / why not (one line): The Tier‑1 source explicitly describes the payment role of the token in the marketplace (even if it is not stated that it is mandatory).
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): incentive/collateral/penalty mechanisms via the token are not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): the use of the token in governance is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- 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): insufficient data → 0 (conservatively).
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://encrypgen.com/ | Tier‑1: the project’s positioning and the claim that DNA tokens can be used to purchase genomic data/services in the marketplace |
| Tier‑1 | https://etherscan.io/token/0xef6344de1fcfC5F48c30234C16c1389e8CdC572C | onchain: the DNA token contract (ERC‑20, Ethereum) |
| Tier‑1 | — | No Tier‑1 source for claim “the product has an AI component” was found. |
| Tier‑2 | https://www.coingecko.com/en/coins/encrypgen | reference token profile (not proof of utility) |
| Tier‑2 | https://coinmarketcap.com/currencies/encrypgen/ | reference token profile (not proof of utility) |
| Tier‑3 | — | — |
No comments to display
No comments to display