Verification

Is hypurr.trade safe?

hypurr.trade is an unofficial community-built interface and is self-verifiable: confirm the Marketplace, Bids, and Hypurr NFT addresses on /verify and HyperEVMScan before signing. The contracts are designed for a 0% marketplace contract fee, normal network gas, no admin, no proxy, no upgrade path, native HYPE settlement, and full seller proceeds; no external audit is claimed unless one is published.

Fee
0% contract fee
Admin
none intended
Launch
facts set

Design

  • Community-built and unofficial; not affiliated with, sponsored by, or endorsed by Hyper Foundation.
  • 0% marketplace contract fee; users still pay normal network gas.
  • No owner/admin, proxy, upgrade, pause, fee recipient, royalty, or admin withdrawal path.
  • Hypurr-only settlement on HyperEVM mainnet with native HYPE payments.
  • Verified source, ABIs, deploy blocks, and onchain state are the authority.
  • Wallet calls pin expected terms, so changed seller, price, amount, or expiry facts revert.

Caveats

  • No external professional audit is claimed unless a published audit exists.
  • Immutable contracts cannot be patched in place after deployment.
  • Collection bids are collection-wide; any current Hypurr owner can accept an active bid for one token.
  • Noncustodial asks can revive inside the one-day window if a seller reacquires and reapproves before cancellation, clearing, or expiry.
  • Contract bidders receive filled bids through raw ERC-721 transferFrom and must control received NFTs.
  • NFTs sent directly to settlement contracts can be permanently locked; there is no NFT rescue function.

Checklist

  1. 1. Open /verify and confirm the marketplace, bids, and Hypurr NFT addresses.
  2. 2. Open each finalized contract on HyperEVMScan and confirm verified source.
  3. 3. Confirm both contracts point to the Hypurr NFT address and there is no owner/admin/proxy/upgrade/fee path.
  4. 4. Read the transaction in the wallet and reject any changed address, seller, price, amount, expiry, recipient, token, or HYPE value.
  5. 5. Use /llms.txt or /safety.json for an AI-readable summary when needed.