Browse documentation16 articles
Protocol
DocsProtocol
PROTOCOL

Security & Authorities

Who controls what, what has been verified on Mainnet, and what has not.

Wallet signing

The connected wallet signs its own launch, trade, and claim transactions in Phantom. HYMET does not ask for a private key or recovery phrase. Read the network, recipient, and amounts in the wallet prompt before approving. Holder payouts are sent by the keeper and need no holder signature.

Authority roles

Wallet addresses, program IDs, and authority roles are different things. This documentation does not publish operational wallet identities.

Mint and freeze authorities
Verified as revoked before launch registration
Creator
Claims the creator share of its own launch; cannot change the split
Platform fee recipient
Receives only the 20% HYMET share
Keeper
Funds and closes payout rounds from the holder pool; cannot reach creator or HYMET funds
Program upgrade authority
Can upgrade the distributor and rotate the keeper key; upgrades are public on-chain

Distributor program

Fee math and account checks run on-chain. After each transfer the program confirms that its vault still covers everything owed. Each payout group can be paid only once, only to the wallet's canonical HYPE account, and never beyond the funded amount.

Mainnet program
9X9fnj4Uh9WC9nmxCahTVsixHZ6VGxNpMesuGhK239Px
Upgradeable
Yes
Build
Reproducible
Review
Internal security review; no external audit yet

Verified on Mainnet

These flows have run on Mainnet with real HYPE, on HYMET's own test tokens, and the results matched on-chain records. Distributor launches used a 50/50 split at 1% and 2% trading fees.

  • Launches through the distributor and the native route.
  • Buying and selling on Meteora DBC with Phantom.
  • Keeper settlement of DBC fees, including the 20% HYMET share and the creator and holder split.
  • Creator claims from the distributor.
  • Funded holder payouts to wallets that already had a HYPE account, on two tokens.
  • Recording carried amounts for wallets below their minimum, with their original balances proven against the on-chain snapshot.
  • Exact reconciliation of chain state, database records, and wallet payments.

Validated only on Devnet, a local validator, or in tests

These flows are implemented, but have not yet run on Mainnet. Treat them as validated in test environments only.

  • Graduation, DBC-to-DAMM v2 migration, and canonical pool registration, at a 1% fee only. No other fee rate has been graduated in any environment.
  • DAMM v2 trading and DAMM v2 fee settlement.
  • Launches with a 0% creator and 100% holder split, and any split other than 50/50 through the distributor.
  • Repeated payout rounds on one token at the 15-minute interval, and a carried amount growing until it is paid.
  • Keeper-created HYPE accounts at the 0.05 HYPE minimum.
  • Payment of carried amounts to wallets that have sold, which has been simulated only.
  • Native-route creator claims and platform claims.

Transaction availability

Mainnet transaction construction is guarded by both server and public configuration. A page being available does not mean every transaction is enabled. HYMET also validates the configured HYPE mint, network, pool accounts, fee recipients, and confirmed launch state where applicable.