standards_skill

This skill explains HyperCore HIP-1, HIP-2, HIP-3 and HyperEVM ERC-20 standards, guiding token creation, liquidity, and when to use each.
  • Python

2.6k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill standards

  • SKILL.md5.9 KB

Overview

This skill explains token standards on Hyperliquid: ERC-20 and other EVM-compatible standards on HyperEVM, plus HIP-1/HIP-2/HIP-3 native standards on HyperCore. It clarifies when to use each standard, how native HyperCore tokens differ from EVM tokens, and the key interfaces and flows for creating markets and liquidity. The goal is a practical decision guide for launches, trading, and cross-layer composability.

How this skill works

The skill inspects the two-layer model: HyperEVM uses standard EVM token interfaces (ERC-20, ERC-721, ERC-4626, ERC-2612) that behave like Ethereum. HyperCore implements protocol-level native tokens (HIP-1) with built-in spot orderbooks and automated liquidity (HIP-2) and allows builder-controlled DEXs (HIP-3). It shows creation flows: API-based HIP-1 deployment and HIP-2 seeding, versus smart-contract ERC-20 deployment on HyperEVM.

When to use it

  • Use ERC-20 on HyperEVM when you need full EVM composability and DeFi integrations (DEXs, lending, vaults).
  • Choose ERC-4626 for tokenized vaults and yield-bearing contract patterns.
  • Use HIP-1 on HyperCore when you want native spot trading and immediate orderbook presence.
  • Seed HIP-2 if you want built-in AMM-style liquidity and to avoid cold-start liquidity problems.
  • Use HIP-3 to run a curated or platform-specific spot DEX with listing control and optional fees.

Best practices

  • Launch as HIP-1 to obtain instant native trading, then bridge to HyperEVM for DeFi composability.
  • Seed sufficient HIP-2 liquidity on launch to ensure price discovery and reduce volatility.
  • Keep HIP-1 token parameters conservative: name ≤20 chars, symbol ≤6 chars, choose decimals (commonly 6 or 8).
  • Use ERC-20 for governance or contracts requiring on-chain mint/burn logic; HIP-1 supply is fixed at creation.
  • Confirm token decimal conventions (USDC=6 on HyperEVM) to avoid integration errors.

Example use cases

  • Launch a speculative token: create HIP-1 and seed HIP-2 for instant market depth. Then wrap to ERC-20 for yield integrations.
  • Deploy a governance token on HyperEVM (ERC-20) to integrate with HyperSwap V2 and lending protocols.
  • Create a curated marketplace using HIP-3 to control listing and charge platform fees.
  • Build a staking vault as an ERC-4626 on HyperEVM while using a HIP-1 wrapper for spot trading on HyperCore.
  • Issue NFTs or collectible assets using ERC-721 on HyperEVM where EVM tooling is required.

FAQ

No. HIP-1 tokens are created via protocol/API on HyperCore and are first-class protocol assets—no Solidity contract deployment is required.

When does HIP-2 graduate to a full orderbook?

Graduation occurs when the market cap surpasses a configured threshold; at that point liquidity transitions from bonding-curve AMM to a full limit orderbook. Exact thresholds vary by configuration.

Can I have both HIP-1 and ERC-20 representations?

Yes. A recommended hybrid approach launches HIP-1 for native trading and then bridges or wraps to ERC-20 on HyperEVM for DeFi composability and broader integrations.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
standards skill by openclaw/skills | VeilStrat