Skip to main content

Gemach

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

Gemach — a DeFi ecosystem/DAO with a claimed AI assistant and the GMAC token (ERC‑20; Ethereum).

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 set of DeFi products and interfaces (trading terminal/lending/execution of onchain operations via a bot), governed through a DAO.
  • Who it’s for: users who need a single interface for DeFi operations and ecosystem products; DAO members.
  • Why onchain/token: onchain is used to interact with DeFi operations and tokens; GMAC is described as a governance token and a mechanism of access/coordination in the DAO.
  • What you can actually touch (Tier‑1): https://gemach.io/ (ecosystem products) and https://t.me/Gemach_Bot (GBot in Telegram).

How it works (very briefly)

  1. The user does: uses Gemach products (via the website/bot/interface — following the project’s links).
  2. The system does: executes the selected onchain operations (swap/bridge/lending/staking — as claimed in the documentation).
  3. The user gets: the result of the onchain operation and the state/positions in the respective protocols.
  4. Where the blockchain is: operations take place in the connected networks; the GMAC token is on Ethereum (ERC‑20).
  5. Token role: GMAC is described as a governance token and a tool for access/coordination in the DAO.

Quick links: AI thesis fit

Project passport

Field Value
Project name Gemach
Also known as (aliases) Gemach DAO; GMAC
Logo (logo) ../assets/317_gemach_logo.svg
Token symbol (ticker) GMAC
Category AI/Agents | DeFi
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 0xd96e84ddbc7cbe1d73c55b6fe8c64f3a6550deea
Token model (token_type) utility (governance)
Max supply 500 000 000 GMAC
Issuance —
Tokenomics (tokenomics, brief) In the documentation GMAC is described as a governance token and a mechanism of access to the products/community; max supply 500M.
Governance DAO
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) NL assistant/agents for DeFi operations
Use‑case (use_case) DeFi super app (swap + bridge + lend)
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

In its official documentation Gemach describes itself as a community‑driven DAO that is building an “all‑in‑one DeFi super app” with a set of products (including a trading terminal and lending/yield). A separately claimed component is “Gemach AI” — a natural‑language assistant that (per the description) can perform typical onchain operations (swap/bridge/lending/staking) and launch agents to automate actions.

Features/modules

  • DeFi interfaces and ecosystem products: a trading terminal, lending/execution of DeFi operations (per the documentation).
  • Gemach AI (per the documentation): a natural‑language assistant and a set of agent scenarios for automation.
  • Ecosystem tokens: GMAC (governance/access) and related products/tokens (GLEND is mentioned).

Typical scenarios

  • Scenario 1: a user performs basic DeFi operations via the interface/bot → gets an onchain result in the selected network/protocol.
  • Scenario 2: a DAO member uses GMAC to access features/participate in governance → gets voting rights/participation in proposals (per the documentation).

Getting started (wallet/network)

  • What you need: an EVM wallet (for operations in EVM networks) and/or access to the products via the official links.
  • Network/chain: GMAC — Ethereum (ERC‑20); the product claims support for multiple networks via a single interface.
  • Fees: network fees of the selected network + fees of the protocols/services used (if applicable).

Architecture/tech (non‑AI)

  • Components: web interface/bot + interaction with onchain protocols (swap/bridge/lending, etc. — per the documentation).
  • Where logic runs: execution of DeFi operations — onchain; interfaces/coordination — offchain.

Token/economics (expanded, no forecasts)

  • GMAC (per the documentation): a governance token and a tool for access/coordination in the DAO; max supply 500M.
  • Distribution/vesting: a detailed distribution/vesting table per Tier‑1 is not recorded in this card.

Governance

  • Who makes decisions: DAO (per the documentation).
  • Where decisions are made (governance): the project’s snapshot space (see links_*).

Security and incidents

  • Audits: the GLend documentation has an Audits section with links to reports (links — in Evidence/links_*).
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: key risks — dependence on the correctness of integrations/protocols and the lack of Tier‑1 metrics/technical details (version/architecture/quality assessment) for the AI assistant/agents.

Project status and timeline

  • Current status: active (based on the presence of products/links in the documentation).
  • Roadmap: published in the project documentation.

Ecosystem/integrations

  • Integrations: —.
  • Where it’s actually used: user scenarios and products are described in the documentation (see links_*).

AI component of the project

  • What is real AI here? The Tier‑1 documentation describes “Gemach AI” — a natural‑language assistant that (per the project’s claim) performs onchain operations and supports agent scenarios for automation.
  • What is truly onchain? Onchain operations in the connected networks (swap/bridge/lending/staking — per the description) and the ERC‑20 token GMAC on Ethereum.
  • Why is a token needed? GMAC is described as a governance token and a tool for access/coordination in the DAO.
  • Red flags (based on the information found): despite the presence of Tier‑1 guides and links to products, metrics/quality and the strict boundaries of “what exactly the AI does” remain unrecorded; it should be double‑checked what exactly is executed onchain and what remains on the service side.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 2
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): 0
  • Claim (one line): In the documentation AI is described as part of the current product, not just as a “plan”.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao
  • Why sufficient / why not (one line): AI_0 requires the scenario “intent only, without a working component”; here a working assistant is claimed.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): In the documentation Gemach AI is described as a natural‑language assistant that performs swap/bridge/lending/staking and agent scenarios.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao
  • Why sufficient / why not (one line): Tier‑1 explicitly describes the purpose of the AI assistant and the type of operations.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The Tier‑1 documentation contains reproducible guides on using Gemach AI (getting started + example requests), and official links to the products are published.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao/products/gemach-ai/getting-started ; https://docs.gemach.io/gemach-dao/products/gemach-ai/using-the-chat-interface ; https://docs.gemach.io/gemach-dao/miscellaneous/links
  • Why sufficient / why not (one line): There are step‑by‑step instructions and “what you can touch”; metrics/quality (AI_3) and the technical architecture (AI_4) are not disclosed per Tier‑1.
  • 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.gemach.io/gemach-dao
  • Why sufficient / why not (one line): No Tier‑1 metrics/benchmarks of the AI assistant’s quality were found.
  • 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) is not recorded by Tier‑1.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao
  • Why sufficient / why not (one line): Insufficient details for a flag of 1.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: GMAC ERC‑20: 0xD96e84DDBc7CbE1D73c55B6fe8c64f3a6550deea
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao/ecosystem-tokens/gmac ; https://etherscan.io/token/0xD96e84DDBc7CbE1D73c55B6fe8c64f3a6550deea
  • Why sufficient / why not (one line): The token is listed in the official documentation and there is an onchain artifact in the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: specific addresses/contracts of Gemach products, other than the GMAC token, are not recorded in this card.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao
  • Why sufficient / why not (one line): OC_2 requires verifiable onchain artifacts of the logic; they are not collected in this card.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the criticality of onchain for Gemach’s core functions is not substantiated by Tier‑1.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao
  • Why sufficient / why not (one line): There is no explicit argument that the product “breaks” without a blockchain (rather than just changing the execution method).
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, GMAC (ERC‑20).
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao/ecosystem-tokens/gmac
  • Why sufficient / why not (one line): The official documentation describes GMAC as the native token of the DAO.
  • 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): No unambiguous Tier‑1 statement was found that GMAC is used as a mandatory payment token for the service.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao/ecosystem-tokens/gmac
  • Why sufficient / why not (one line): GMAC is described as an access/governance token, but a payment use‑case is not explicitly singled out.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties as a protocol necessity for GMAC are not recorded in Tier‑1.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao/ecosystem-tokens/gmac
  • Why sufficient / why not (one line): There is no sufficient description of incentives/collateral/penalties specifically as a protocol necessity.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): GMAC is described as a token for participation in DAO proposals and votes in proportion to holdings.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao/ecosystem-tokens/gmac
  • Why sufficient / why not (one line): The documentation directly describes the governance use‑case.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token in the governance/access role is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.gemach.io/gemach-dao/ecosystem-tokens/gmac
  • Why sufficient / why not (one line): The documentation describes the role of the token but does not provide a strict argument of “irreplaceability”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.gemach.io/gemach-dao Description of Gemach as a DAO/DeFi ecosystem and of the claimed “Gemach AI” (an assistant for performing onchain operations).
Tier‑1 https://docs.gemach.io/gemach-dao/miscellaneous/links Tier‑1 links to the products (including the Gemach app and GBot).
Tier‑1 https://docs.gemach.io/gemach-dao/products/gemach-ai/getting-started A step‑by‑step guide to connecting a wallet and starting to work with Gemach AI (demo surface).
Tier‑1 https://docs.gemach.io/gemach-dao/products/gemach-ai/using-the-chat-interface Example requests and the workflow via the Gemach AI chat interface (demo surface).
Tier‑1 https://gemach.io/ The interface of the ecosystem products (what you can touch).
Tier‑1 https://t.me/Gemach_Bot GBot: a Telegram interface for executing actions/trading (what you can touch).
Tier‑1 https://docs.gemach.io/gemach-dao/ecosystem-tokens/gmac GMAC as the native token of the DAO (governance/access) and max supply 500M.
Tier‑1 https://etherscan.io/token/0xD96e84DDBc7CbE1D73c55B6fe8c64f3a6550deea Onchain artifact: the GMAC contract (ERC‑20) in the explorer.
Tier‑1 https://docs.gemach.io/gemach-dao/products/glend/audits The Audits section for one of the products (GLend) with links to auditors’ reports.

No comments to display

Back to top