Hedge Lords crown HEDGE LORDS

Everything, plainly

THE DOCS

How Hedge Lords works — the mint, the burns, the hourly engine, the launchpad that funds it all, and exactly what the team can and cannot touch.

SECTION 01

What is Hedge Lords

Hedge Lords is a 5,555-piece pixel NFT collection on Robinhood Chain (chain id 4663), tied to the $HEDGE burn token and funded by a token launchpad. An activated Lord automatically collects the assets you choose every hour — tokenized stocks or USDG — paid for by protocol revenue. Those assets build up inside the NFT's own ERC-6551 wallet and travel with it if you sell.

What makes the court different is where the money comes from. The yield engine is fed by the Launchpad: bonding-curve launches that graduate onto Uniswap V4 through our hook, paying curve fees, a perpetual skim on every swap of every pool, and probate settlements when launches die. The Lords aren't a project with a launchpad attached — they are the house the launchpad pays.

┌──────────────────────────────────────────┐ │ THE LAUNCHPAD │ │ curve fees · perpetual skim · probate │ └───────────────────┬──────────────────────┘ │ + $HEDGE trading fees ▼ ┌─────────────────────────┐ │ HOURLY EARNING ENGINE │ │ 80% buys stocks/USDG │ └───────────┬─────────────┘ ▼ ┌──────────────────────────────────────────┐ │ 5,555 LORDS — each with an ERC-6551 │ │ vault, weighted by tier × rarity │ └──────────────────────────────────────────┘
SECTION 02

Network Parameters & Contracts

  • Network Name: Robinhood Chain Mainnet · Chain ID: 4663 · Gas: ETH
  • RPC Endpoint: https://rpc.mainnet.chain.robinhood.com
  • Block Explorer: robinhoodchain.blockscout.com
ContractStandardAddress
$HEDGE TOKENERC-200x… [Pending]
HEDGE LORDS NFTERC-721 + 49060x… [Pending]
EARNING ENGINECustom Router0x… [Pending]
THE VAULTERC-65510x… [Pending]
LAUNCHPAD + PROBATEV4 Hook Suite0x… [Pending]
ERC-6551 REGISTRYCanonical0x…6551
This page is the single source of truth for contract addresses. An address you found anywhere else is not ours. The team never opens a DM and never asks for a signature on an outside site. Keep this page saved and check it before every interaction.
SECTION 03

$HEDGE — the burn token

$HEDGE is never paid out. It is not a reward, not a dividend, not an emission. The only way it ever moves through the protocol is when a holder burns it — to activate a Lord, climb a tier, wake a transferred Lord, change a mandate, or fund a takeover. Supply only falls.

Deflation runs on three fronts:

  • Holder burns: every activation and upgrade permanently destroys $HEDGE.
  • Collection burns: takeovers destroy NFTs; 5,555 is the ceiling forever, and the real number only shrinks.
  • External-revenue burns: 20% of every probate settlement buys $HEDGE off the market and burns it — deflation funded by other projects' activity, not by holders spending their own bags.
SECTION 04

Mint & rarity

Minting is paid in ETH. Your piece is drawn inside your own mint transaction and shows the moment it confirms — real art, real traits, instantly, here and on OpenSea. No reveal day. Each mint draws at random from whatever remains unclaimed, so every one of the 5,555 is dealt exactly once — and the team pre-selects, withholds, and reserves nothing.

Rarity carries a small permanent yield boost (Squire 1.00× up to King 1.25× — final table ships with the contract). Because rarity touches yield, smart contracts are barred from minting: a contract could otherwise cancel its own mint whenever the draw came up common, re-rolling until a grail appeared. Wallet-only minting closes that door before it opens.

SECTION 05

Activation & tiers

A freshly minted or bought Lord arrives dormant. Burn $HEDGE to put it on the payroll at Tier 1, then keep burning to climb. Burns are cumulative and permanent — tiers are welded to the token itself, so selling a Lord sells its tier along with it.

TierTotal $HEDGE burnedMultiplier
TIER 1 (ACTIVE)66,6661.00×
TIER 2166,6661.25×
TIER 3366,6661.80×
TIER 4666,6662.50×
TIER 5 (EXECUTIVE)1,666,6663.33×

Active status, though, doesn't transfer: a Lord lands dormant in its new owner's wallet, and a small wake burn switches it back on. Tier and boosts carry over untouched — nothing about the NFT itself ever resets. A Lord's total weight in each round is tier × rarity (× takeover bonuses) — and that multiplier is published as a live OpenSea trait via ERC-4906, so the market can filter and price it.

SECTION 06

Hostile takeovers

Sacrifice a Lord of strictly lower rarity to permanently boost a greater one, plus a $HEDGE burn fee. Each Lord can absorb at most three others, at escalating cost. The absorbed NFT is destroyed forever; everything it had banked moves into the survivor's vault in the same transaction, and nothing is left behind on a burned token. Each takeover adds a permanent gold mark to the survivor's art.

♛ Read the tape: the pot is shared, so a boosted Lord takes a bigger slice and every other slice thins by a hair. Your gain is the court's rounding error — and the collection gets permanently rarer. That's the whole deal, printed in plain ink.
SECTION 07

Earning & the vault

The payroll runs itself. A round settles every hour with nothing to claim, ever — the pot splits across all active Lords by their multipliers. You pick up to three assets — tokenized stocks or USDG for a stable payout — and a mandate: Accumulate (pure DCA), Balanced (auto-rebalance toward target weights), or Secure (profits above a threshold skim into USDG). Fresh activations default to USDG until you choose. Splits change once per day; mandate changes burn a small $HEDGE fee. Only Lords already active when a round opens are counted in it, so rounds can't be jumped at the last second.

The engine can't be robbed by its own bot. Every buy carries a minimum-output check the contract computes for itself from a rolling on-chain price average; fills that land meaningfully under it revert, and the balance carries into the next round. Sub-minimum amounts accumulate the same way instead of evaporating. The worst a failed or hijacked keeper can manage is a postponed round — the funds roll forward untouched.

The vault answers to the token. Hourly earnings bank inside the Lord's ERC-6551 wallet indefinitely — withdrawing is free, and the contract contains no parameter that could ever attach a fee to it. Moving vault contents requires holding the token, and the destination is hardwired to the holder's own address: there is no code path through which the team, the keeper, or the deployer can reach in. Sell the Lord and its bank rides along — check any Lord's holdings on the explorer before buying. Prefer direct deposit? Flip any Lord to pay its owner's wallet each hour instead; banking in the vault is just the default posture. A weekly Opening Bell bonus round can be triggered by anyone, with a small tip to whoever rings it — a ritual, not a requirement: base earning never depends on it.

SECTION 08

The Launchpad & the hook

The pad is a fair-launch bonding curve: anyone launches in seconds, everyone buys the same curve, no allocations and no tier gates — speed is the point. Launches can pair against ETH, USDG, or tokenized stocks, with an optional creator fee. Curve launches and V4 hooks both already exist on Robinhood Chain; what the court adds is the machine around them.

At graduation, raised liquidity is seeded into a Uniswap V4 pool owned by the protocol — never the creator — deployed through the Hedge Lords hook, which enforces at pool level:

  • Anti-snipe launch fees: swap fees open high at graduation and decay over the first minutes, taxing sniper bots without touching organic buyers.
  • The lock itself: liquidity rules live in the hook; the pool cannot be pulled outside them.
  • The perpetual skim: 0.05% of every swap on every pool launched here streams to the Lords' reward pot, forever. Stock-paired pools pay it in tokenized stock — the exact asset the engine distributes.
  • Native health measurement: pool health is computed from its own swaps (long TWAP + volume), not an external oracle — which is what makes probate un-spoofable.

Revenue flow: 80% of everything that reaches the engine — curve fees, skim, probate, $HEDGE trading fees — buys the assets Lords picked. 20% funds keeper gas, the site, and development, taken from newly arrived fees only.

SECTION 09

Probate — the Liquidation Desk

Most launches die, on every chain, and their liquidity stays buried forever. Here, dead value gets recycled. A pool — or an ungraduated curve — enters probate when it has spent roughly 30 days below a $5,000 market cap, measured on a long TWAP with a volume floor so the trigger can't be wicked in either direction. A grace period follows in which anyone can contest before settlement executes.

The estate settles in three parts:

  • 50% to the dead token's holders — claimable pro-rata by snapshot. The creator's wallet is always excluded, so deaths can't be farmed by launching garbage.
  • 30% to the Lords' reward pot — into the hourly engine.
  • 20% buyback-and-burn of $HEDGE — deflation on external revenue.

Dust rule: estates under ~$500 skip the claims machinery entirely and route to pot + burn — pro-rata claims on pocket change is gas theatre. Unclaimed holder allocations sweep to the pot after a fixed window. All trigger parameters are fixed on-chain and published here before launch.

♛ For launch creators, this is the pitch to your community: if this project dies, holders get real value back. A stronger promise than burned LP — where death means everyone loses everything.
SECTION 10

Security & honesty

What nobody can do — including us:

  • Vaults ship with no owner key, no pause switch, no upgrade path, and no back door. The flip side of that lock: assets sent there by accident are unrecoverable — the same wall that keeps everyone out keeps mistakes in.
  • Withdrawals cannot be fee'd: there is no setting in the contract that could add one later.
  • The engine's buys are slippage-bounded by the contract itself; a compromised keeper can delay rounds, never drain them.
  • Probate parameters are fixed on-chain; nobody can trigger an unwind early or redirect a settlement.

What the team does control — stated plainly, because pretending otherwise is how projects lie: the keeper that submits rounds (if it dies, rounds delay and anyone can self-claim vault contents for cents), the minimum trade size parameter, the website and its frontend, and pad curation/social channels. None of these touch banked funds. Contracts will be verified on the explorer at deployment; audit status will be published here honestly, whatever it is.