XMAQUINA
XMAQUINA — 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).
XMAQUINA — an AI/Other | DeFi project on the Base network, token (symbol: DEUS).
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 DAO/community that positions itself around “Physical AI” and describes collective decisions/participation via token staking.
- Who it’s for: DAO/community members who want to participate in decision-making (per the project description).
- Why onchain/token: per Tier‑1, the DEUS token is used for participation in governance via staking; the token contract on the Base network is confirmed.
How it works (very briefly)
- The user does: joins the community and holds/stakes the DEUS token (per the Tier‑1 description).
- The system does: provides the ability to participate in decision-making (governance) when staking.
- The user gets: participation in governance (without assumptions about returns/investment value).
- Where the blockchain is: the DEUS token contract is on the Base network; the staking/participation mechanics are described in the documentation.
- Token role: governance (via staking).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | XMAQUINA |
| Also known as (aliases) | DEUS, deus-token |
| Logo (logo) | ../assets/674_deus-token_logo.svg |
| Token symbol (ticker) | DEUS |
| Category | AI/Other | DeFi |
| Primary chain (chain) | Base |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Base; Ethereum L2) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x940A319B75861014A220D9c6c144d108552B089B |
| Token model (token_type) | utility (staking + incentives + governance) |
| Max supply | 1 000 000 000 DEUS (capped) |
| Issuance | — |
| Tokenomics (tokenomics, brief) | Tier‑1: total/max supply 1B; the token is non-transferable; distribution (Genesis Auction 30%, DAO Treasury 30%, etc.). |
| Governance | DAO (per the Tier‑1 description) |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | Physical AI |
| Use‑case (use_case) | DAO coordination + governance via staking |
| 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 2 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.xmaquina.io/ |
| Docs | https://docs.xmaquina.io/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://xmaquina.gitbook.io/xmaquina/ |
| Roadmap | https://www.xmaquina.io/blog/the-next-steps-for-the-dao |
| Security advisories | — |
| Explorer | https://basescan.org/token/0x940A319B75861014A220D9c6c144d108552B089B |
| App / Demo | — |
| X | https://twitter.com/xmaquina |
| Discord | https://discord.com/invite/xmaquina |
| Telegram | — |
| Medium | — |
| Audit report(s) | https://xmaquina.gitbook.io/xmaquina/deus-genesis-auction/security-and-audits |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/xmaquina |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/deus-token/ |
General project overview
In the Tier‑1 documentation, XMAQUINA is described as a DAO positioned around “Physical AI” that states the goal of giving participants a “stake” in technologies/companies related to robotics and automation. At the same time, Tier‑1 confirmation that the project provides its own working AI component (model/agent/inference) as part of the product/protocol was not found — therefore AI is recorded at the intent level (AI_0=1).
Features/modules
- DAO and governance: participation via staking of the DEUS token (per Tier‑1).
- Communications/documentation: GitBook + the project website.
- DEUS token: an onchain contract on Base.
Typical scenarios
- Scenario 1: a participant stakes DEUS → participates in governance (per Tier‑1).
- Scenario 2: a participant follows updates/proposals → votes/participates in discussions (the voting mechanics are not established in this card).
Getting started (wallet/network)
- What you need: an EVM wallet (Base) and access to the project’s instructions.
- Network/chain: Base.
- Fees: Base network fees for operations with the token/staking.
Architecture/tech (non‑AI)
- Components: the token contract on Base; governance/staking (described at the documentation level).
- Participant roles: token holders/stakers; governance participants.
- Where logic runs: onchain — token operations and (presumably) staking; offchain — communications/coordination (not strictly established).
- Dependencies: Base (Ethereum L2).
Token/economics (expanded, no forecasts)
- Token utility: staking DEUS for participation in governance (per Tier‑1).
- Protocol necessity drivers: per Tier‑1, participation in governance is tied to staking of the token.
- Who pays fees: users (Base gas).
- Where fees go: to Base validators (gas).
- Issuance/burn: — (not established).
- Security/incentive mechanisms: Tier‑1: Governance V2 describes staking DEUS → mint xDEUS and “protocol rewards” (additional details pending release).
- Distribution and token issuance schedule: — (not established).
- Treasury: — (not established).
Governance
- Who makes decisions: the DAO/token holders (per the Tier‑1 description).
- How protocol parameters change: — (not established per Tier‑1).
- Where decisions are discussed/made: — (not established).
- Keys/multisig: — (not established).
Security and incidents
- Audits: there is a link to the Security and Audits section (see links_*).
- Bug bounty: —.
- Incidents: — (not established).
- Threat model: this card lacks Tier-1 details of the staking/voting mechanics and key management; the AI direction is claimed at the intent level, but without supporting artifacts.
Project status and timeline
- Current status: active (there is documentation and an onchain token).
- Key releases/milestones: —.
- Roadmap: see links_* (in the current list — a link to “next steps for the DAO”).
Ecosystem/integrations
- Integrations: — (not established).
- Partners: — (not established).
- Where it’s actually used: — (not established).
AI component of the project
- What is real AI here? the Tier‑1 mentions relate to the “Physical AI” domain (positioning/direction), but no Tier‑1 proof of the project’s own AI component was found.
- What is truly onchain? the DEUS token on the Base network (the contract is specified).
- Why is a token needed? Tier‑1: staking of the DEUS token for participation in governance.
- Red flags (based on the information found): the risk of AI‑washing (AI appears as a topic, but without an AI component); the risk of token‑washing (if the token is used only as “membership”), a lack of Tier‑1 details on the governance/staking implementation (contracts/addresses/parameters).
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 | medium | 2 |
| Evidence | Tier‑1 present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): Tier‑1 describes the project as a DAO around “Physical AI”.
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): This is intent/positioning; no proof of a working AI component was found (AI_1..AI_4=0).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): No Tier‑1 description of a specific AI feature/module in the project’s product was found.
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): The documentation describes the DAO/mission, not the operation of an AI module.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No demos/examples of an AI component were found (an AI component is not established).
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): 1 requires a demo surface.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): Quality metrics of an AI component are absent (an AI component is not established).
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No Tier‑1 tech description of an AI module/model versions was found.
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): The documentation does not describe the AI architecture of the product.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Base
- Addresses/identifiers: DEUS token: 0x940A319B75861014A220D9c6c144d108552B089B
- Evidence: Tier‑1 — https://basescan.org/token/0x940A319B75861014A220D9c6c144d108552B089B
- Why sufficient / why not (one line): The token contract on a public network confirms the onchain component.
- 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 (other than the existence of the token).
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): 1 requires a Tier‑1 description of specific useful onchain logic (contracts/rules/governance mechanism), not a general formulation.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established (a Tier‑1 argument for onchain criticality is absent).
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): Under the conservative rule — 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, DEUS.
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): Tier‑1 directly mentions the “DEUS token”.
- 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): A payment role of the DEUS token (pay for service) is not established in Tier‑1.
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): 1 requires explicit mechanics of payment for the service.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): Tier‑1 describes staking DEUS → mint xDEUS and access to protocol rewards (participation incentives).
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/overview/governance-overview/governance-v2-post-tge
- Why sufficient / why not (one line): There is an explicit Tier‑1 statement about rewards, although the details of the mechanics have not yet been disclosed.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): Participation in governance requires staking of the DEUS token (per Tier‑1).
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): The documentation explicitly states “stake the DEUS token to participate in decision-making”.
- 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.
- Evidence: Tier‑1 — https://xmaquina.gitbook.io/xmaquina/
- Why sufficient / why not (one line): TK_4=1 requires an explicit justification that “it can be replaced without loss of meaning”.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.xmaquina.io/deus-token/tokenomics | Tier‑1: DEUS tokenomics (supply 1B capped, non-transferable, distribution, governance/incentives). |
| Tier‑1 | https://xmaquina.gitbook.io/xmaquina/overview/governance-overview/governance-v2-post-tge | Tier‑1: Governance V2 (staking DEUS → xDEUS, governance rights, protocol rewards, OPX proposals/veto). |
| Tier‑1 | https://basescan.org/token/0x940A319B75861014A220D9c6c144d108552B089B | Onchain fact: the DEUS token contract on the Base network. |
| Tier‑1 | https://xmaquina.gitbook.io/xmaquina/deus-genesis-auction/security-and-audits | Tier‑1: the “Security and Audits” section (the existence of a page about security/audits). |
| Tier‑1 | — | No Tier‑1 source for claim “a working AI component (model/agents/inference) in the product” was found. |
No comments to display
No comments to display