HotKeySwap
HotKeySwap — 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).
HotKeySwap — an AI/Other + DeFi project on Ethereum (EVM), token (symbol: HOTKEY).
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 DEX/aggregator and a set of interfaces for swap/bridge across several networks.
- Who it’s for: DeFi users who need swapping and bridging without manual route selection.
- Why onchain/token: the HOTKEY token exists on EVM networks; the project claims AI routing and product features (DEX/bridge), but the necessity of the token for accessing the service is not confirmed.
- What you can actually touch (Tier‑1): the web DEX/interfaces from the official website/documentation (swap/bridge).
How it works (very briefly)
- The user does: sets the input asset/network and the target asset/network (swap/bridge).
- The system does: selects a route via DEXs/aggregators/bridges (the materials claim this is done with the help of AI algorithms).
- The user gets: a completed swap/bridge and the resulting asset in the target network.
- Where the blockchain is: operations take place onchain in the selected networks; HOTKEY is a token on several EVM networks.
- Token role (if any): per the sources found, the token participates in the ecosystem (contracts across networks), but its specific “mandatory nature” for using the DEX/bridge is not proven.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | HotKeySwap |
| Also known as (aliases) | HOTKEY; Hotkeyswap |
| Logo (logo) | — |
| Token symbol (ticker) | HOTKEY |
| Category | AI/Other | 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 | 0x018DD3A0Dd7F213cc822076b3800816d3CE1ED86 |
| Token model (token_type) | — |
| Max supply | 100,000,000 HOTKEY |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | total supply: 100,000,000; burned: 5,000,000 (per the docs) |
| Governance | company |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI routing for cross-chain swaps |
| Use‑case (use_case) | swap + bridge aggregation |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 2 / 1 / 0 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://hotkeyswap.com/ |
| Docs | https://docs.hotkeyswap.com/ |
| App / Demo | https://dex.hotkeyswap.com/ |
| GitHub | https://github.com/HotKeySwap |
| Releases / Changelog | https://twitter.com/HotKeySwap |
| Whitepaper | https://docs.hotkeyswap.com/ |
| Roadmap | https://docs.hotkeyswap.com/introduction/roadmap-and-milestones |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x018dd3a0dd7f213cc822076b3800816d3ce1ed86 |
| X | https://twitter.com/HotKeySwap |
| Discord | — |
| Telegram | https://t.me/HotKeySwap |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/hotkeyswap |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/hotkeyswap/ |
General project overview
HotKeySwap describes itself as a DeFAI platform with a DEX/route aggregation and cross‑chain operations (swap/bridge). The documentation claims that the system uses AI algorithms to select efficient routes and execute trades via various protocols and networks.
Features/modules
- Cross‑chain swap/bridge: exchanging and transferring assets between networks.
- DEX interfaces: the web DEX and other interfaces listed on the website.
- AI routing (claimed): route selection taking into account cost/slippage/network state.
Typical scenarios
- Scenario 1: a user performs a cross‑chain swap, receiving an asset in another network.
- Scenario 2: a user bridges HOTKEY between networks via the official bridge.
Getting started (wallet/network)
- What you need: a web3 wallet and access to the DEX/bridge web interface.
- Network/chain: Ethereum (for the main pair of HOTKEY contracts; there are also contracts on other networks per the docs).
- Fees: gas in the selected network(s) and possible protocol/bridge fees (depend on the route).
Architecture/tech (non‑AI)
- Components: DEX/bridge web interfaces; the HOTKEY token; integrations with DEXs/aggregators and bridges (claimed).
- Participant roles: users; liquidity providers/protocols through which the swaps go; the team/operators.
- Where logic runs: execution of swap/bridge — onchain; route selection/aggregation — may be partially offchain (per the product description).
- Dependencies: EVM networks, bridges (for example LayerZero for HOTKEY), external DEXs/aggregators.
Token/economics (expanded, no forecasts)
- Issuance/burn: the documentation specifies a total supply of 100,000,000 and a burned supply of 5,000,000.
- Contracts across networks: the documentation lists the HOTKEY addresses on Ethereum and on Base/BSC/Arbitrum.
- Purpose of the token: claimed in general terms (an ecosystem token); detailed “mandatory for the service” rules were not found per Tier‑1 sources as of the verification date.
Governance
- Who makes decisions: company (per public materials).
- How product parameters change: via product/contract updates; a formal governance process was not found per Tier‑1 sources as of the verification date.
Security and incidents
- Audits: no confirmed public audits were found per Tier‑1 sources as of the verification date.
- Bug bounty: not found per Tier‑1 sources as of the verification date.
- Incidents: no public postmortems were found per Tier‑1 sources as of the verification date.
Project status and timeline
- Current status: the web interfaces are available; the HOTKEY token on mainnet networks.
- Roadmap: there is a roadmap page in the official documentation.
Ecosystem/integrations
- Integrations: bridges/DEX protocols (claimed in the documentation and on the website); swap/bridge interfaces.
- Partners: — (no Tier‑1 confirmations of partnerships were recorded per Tier‑1 sources as of the verification date).
- Where it’s actually used: the DEX and bridge (Tier‑1 links on the website/in the docs).
AI component of the project
- What is real AI here? the documentation claims that “AI algorithms” select optimal swap/bridge routes (AI routing).
- What is truly onchain? the HOTKEY token and the swap/bridge operations (execution in the networks); the addresses of HOTKEY contracts on several networks are listed.
- Why is a token needed? the token exists and is bridged between networks; the detailed “necessity” of the token for accessing the service is not confirmed per Tier‑1 sources as of the verification date.
- Red flags (based on the information found): AI‑washing (few tech details about the “AI algorithms”); token‑washing (it is unclear whether the token is mandatory for the service); what to double‑check — the DEX/bridge contract(s) and their addresses, as well as the real rules for using the token.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 2 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| 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 part of a working product; a separate “intent‑only” roadmap item is not required.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without an explicit “roadmap/intent” artifact we set 0.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): it is claimed that AI algorithms select the most efficient routes for cross‑chain swap/bridge (routing/optimization).
- Evidence: Tier‑1 — https://docs.hotkeyswap.com/introduction/our-solution
- Why sufficient / why not (one line): the Tier‑1 documentation describes the role of AI routing and its purpose.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): public web DEX/swap/bridge interfaces are available, and the official links lead to them.
- Evidence: Tier‑1 — https://hotkeyswap.com/ ; https://dex.hotkeyswap.com/
- Why sufficient / why not (one line): the product can be opened and used as a demo interface (its existence is confirmed by the Tier‑1 website).
- 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/benchmarks of the “AI routing” were not found per Tier‑1 sources as of the verification date.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): a detailed architecture/versions of the AI component were not found (there are product descriptions without tech details).
- Evidence: Tier‑1 — https://docs.hotkeyswap.com/introduction/our-solution
- Why sufficient / why not (one line): without an architecture/a description of the models we set 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: HOTKEY (Ethereum): 0x018DD3A0Dd7F213cc822076b3800816d3CE1ED86; Base/BSC/Arbitrum: 0x374Ad0440Cd5c8E1A8412C156BeeEcE108EF4bB6
- Evidence: Tier‑1 — https://docs.hotkeyswap.com/introduction/usdhotkey
- Why sufficient / why not (one line): the official documentation lists the contract addresses.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: the addresses/contracts of the product’s DEX/bridge logic (other than the HOTKEY token contracts) are not confirmed per Tier‑1 sources as of the verification date.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without addresses/a description of deployed contracts with useful logic we set 0.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the criticality of onchain for the claimed AI routing is not proven per Tier‑1 sources as of the verification date.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without explicit proof we set 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the HOTKEY token exists (the contracts are listed in the official documentation).
- Evidence: Tier‑1 — https://docs.hotkeyswap.com/introduction/usdhotkey
- Why sufficient / why not (one line): the contract addresses are listed in the Tier‑1 docs.
- 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): payment for the service with the HOTKEY token (as mandatory) could not be confirmed per Tier‑1 sources as of the verification date.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without Tier‑1 payment/access rules we set 0.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): incentives/collateral/penalties necessary for the protocol are not confirmed per Tier‑1 sources as of the verification date.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without incentive mechanics we set 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): governance via the token is not confirmed per Tier‑1 sources as of the verification date.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without a description of voting/a DAO we set 0.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): per the sources found, the token looks replaceable (payments/access can also be implemented without a separate token).
- Evidence: Tier‑1 — https://docs.hotkeyswap.com/introduction/usdhotkey
- Why sufficient / why not (one line): no proof of irreplaceability was found → we consider it replaceable and set 1.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.hotkeyswap.com/introduction/our-solution | The AI routing claim and the purpose of the product |
| Tier‑1 | https://hotkeyswap.com/ | The existence of the product and links to the swap/bridge interfaces |
| Tier‑1 | https://docs.hotkeyswap.com/introduction/usdhotkey | Tokenomics and the official addresses of the HOTKEY contracts |
| Tier‑2 | https://coinmarketcap.com/currencies/hotkeyswap/ | Token profile (for reference) |
| Tier‑3 | https://twitter.com/HotKeySwap | Marketing announcements/updates (context) |
No comments to display
No comments to display