Holdstation
Holdstation — 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).
Holdstation — a DeFi / AI/Agents project on zkSync Era, token (symbol: HOLD).
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 trading platform/infrastructure for trading (derivatives) with a focus on a smart wallet.
- Who it’s for: active DeFi traders and zkSync users.
- Why onchain/token: onchain is needed for the wallet/contracts and for accounting of operations; the token — for utility/incentives in the ecosystem (per the documentation).
How it works (very briefly)
- The user does: connects a wallet and uses the trading functions.
- The system does: executes operations via smart contracts/wallet logic on zkSync Era.
- The user gets: access to trading tools and services.
- Where the blockchain is: the HOLD token and contract components on zkSync Era (Ethereum L2).
- Token role (if any): a utility token (staking/incentives/possible discounts — per the whitepaper).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Holdstation |
| Also known as (aliases) | HOLD |
| Logo (logo) | ../assets/175_holdstation_logo.svg |
| Token symbol (ticker) | HOLD |
| Category | AI/Agents | DeFi |
| Primary chain (chain) | zkSync Era |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | L2 (ZK Rollup, zkSync Era on Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0xEd4040fD47629e7c8FBB7DA76bb50B3e7695F0f2 |
| Token model (token_type) | utility (governance) |
| Max supply | 7,903,700 HOLD (fixed), decimals: 18 |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | token utility + staking/incentives (per the whitepaper) |
| Governance | — |
| Admins/keys | — |
| Audit | yes (PeckShield) |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI agents/bots for trading |
| Use‑case (use_case) | derivatives/trading |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 2 / 1 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://holdstation.com/ |
| Docs | https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf |
| GitHub | https://github.com/holdstation |
| Releases / Changelog | https://blog.holdstation.com/ |
| Whitepaper | https://holdstation.com/whitepaper |
| Roadmap | https://docs.holdstation.com/holdstation/overview/introduction/roadmap |
| Security advisories | — |
| Explorer | https://explorer.zksync.io/address/0xed4040fD47629e7c8FBB7DA76bb50B3e7695F0f2 |
| X | https://twitter.com/HoldstationW |
| Discord | https://discord.com/invite/holdstation |
| Telegram | https://t.me/HoldstationW_EN |
| Medium | https://holdstation.medium.com/ |
| Audit report(s) | https://github.com/peckshield/publications/blob/master/audit_reports/PeckShield-Audit-Report-Holdstation-v1.0.pdf |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/holdstation-2 |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/holdstation/ |
General project overview
Holdstation is a DeFi trading project in the zkSync Era ecosystem. The public documentation describes trading functions and a smart wallet, and also claims AI functions related to trading bots/agents.
Features/modules
- Trading platform (derivatives/trading).
- Smart wallet (contract components on L2).
- AI direction (AI agents for trading — claimed).
Typical scenarios
- Scenario 1: a user trades → gets trade execution via the Holdstation interface.
- Scenario 2: a user uses the smart wallet → gets convenient management of onchain operations.
Getting started (wallet/network)
- What you need: an EVM wallet and assets on zkSync Era.
- Network/chain: zkSync Era.
- Fees: zkSync fees + possible protocol fees.
Architecture/tech (non‑AI)
- Components: a web client + contract components (wallet/token) on zkSync Era + the offchain part of the service.
- Participant roles: users/traders.
- Where logic runs: onchain — wallet/accounting, offchain — part of the service/interface logic.
- Dependencies: zkSync Era, Ethereum L1, RPC/indexing.
Token/economics (expanded, no forecasts)
- Token utility: in the whitepaper, the token is described as the ecosystem’s utility asset (including staking/incentives).
- Issuance/burn: fixed supply 7,903,700 HOLD (per the explorer).
- Security/incentive mechanisms: staking is claimed.
Governance
- Who makes decisions: — (no confirmed DAO process in this card).
Security and incidents
- Audits: a PeckShield report is published (see links).
- Bug bounty: not found.
Project status and timeline
- Current status: active.
- Roadmap: available in the project documentation (see link).
Ecosystem/integrations
- Integrations: the zkSync Era ecosystem (wallets/DEX/infra — as the product develops).
AI component of the project
- What is real AI here? The official materials mention AI agents/bots for trading, but within this card no public demo/metrics were found.
- What is truly onchain? the HOLD token and contract components on zkSync Era.
- Why is a token needed? a utility token for staking/incentives and ecosystem functions.
- Red flags (based on the information found): the AI part without a demo/metrics (AI‑washing risk).
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | medium | 2 |
| 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): AI is described as a functional direction/module, so we count it as AI_1, not as “intent only”.
- Evidence: Tier‑1 — https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf
- Why sufficient / why not (one line): there is a description of AI functions (AI_1), so AI_0 does not apply.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): AI agents/bots for trading and for automating trading actions are claimed.
- Evidence: Tier‑1 — https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf , https://docs.holdstation.com/holdstation/overview/introduction/roadmap
- Why sufficient / why not (one line): there is a direct description of AI functions in the project’s documents.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): no public repeatable demo of the AI agents was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a demo we do not raise the flag.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): quality metrics are not published.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): no detailed technical description of the AI models/versions/architecture was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): the description is not technical enough for AI_4=1.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: zkSync Era
- Addresses/identifiers: HOLD: 0xEd4040fD47629e7c8FBB7DA76bb50B3e7695F0f2
- Evidence: Tier‑1 — https://explorer.zksync.io/address/0xed4040fD47629e7c8FBB7DA76bb50B3e7695F0f2
- Why sufficient / why not (one line): the token/contract address is verifiable in the explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: a smart wallet/contract components for user operations (per the whitepaper).
- Evidence: Tier‑1 — https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf
- Why sufficient / why not (one line): onchain logic beyond the token is described.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: no strict argument was found that without the blockchain the product loses its meaning (above the level of “accounting/execution”).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient data for OC_3=1.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the HOLD token exists.
- Evidence: Tier‑1 — https://explorer.zksync.io/address/0xed4040fD47629e7c8FBB7DA76bb50B3e7695F0f2
- Why sufficient / why not (one line): the token is verifiable onchain.
- 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): the token utility includes payment/fees/discounts (per the whitepaper).
- Evidence: Tier‑1 — https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf
- Why sufficient / why not (one line): the utility is described in the official document.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): staking/incentives based on HOLD are claimed.
- Evidence: Tier‑1 — https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf
- Why sufficient / why not (one line): staking is described as part of the token economy.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): the governance role of HOLD is not unambiguously confirmed within this card.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient data.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): a utility token (discounts/incentives) is theoretically replaceable; strict irreplaceability is not proven.
- Evidence: Tier‑1 — https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf
- Why sufficient / why not (one line): there is no “without the token the product breaks” test.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://static.holdstation.com/doc/Holdstation-Whitepaper.pdf | description of the product, the token and the AI direction |
| Tier‑1 | https://docs.holdstation.com/holdstation/overview/introduction/roadmap | roadmap/plans (including AI functions) |
| Tier‑1 | https://explorer.zksync.io/address/0xed4040fD47629e7c8FBB7DA76bb50B3e7695F0f2 | onchain facts on HOLD (supply/decimals) |
| Tier‑1 | https://github.com/peckshield/publications/blob/master/audit_reports/PeckShield-Audit-Report-Holdstation-v1.0.pdf | public audit |
| Tier‑3 | — | — |
No comments to display
No comments to display