buyback policy

for site, readme, and pinned thread.

the short version

every 90 days, 50% of accumulated royalties are used to buy the lowest-priced hyper claudes on hyperevm secondary markets and burn them. the other 50% covers operations. every transaction is published with hashes. if royalties stop flowing, buybacks pause. no royalty, no buyback.

that's the whole thing. the rest is detail.

---

the long version

royalty source. the contract sets a 5% default royalty via erc-2981. the royalty receiver is a multi-sig safe with two signers. royalty enforcement depends on the marketplace honoring erc-2981. see failure modes.

every 90 days, the safe executes:

1. collect. all royalties received in the prior 90-day window.
2. split. 50% transferred to a dedicated buyback wallet. 50% retained by the safe for operations: infrastructure, security review, and continued work on the hyper claude site and tooling.
3. buy. the buyback wallet sweeps the lowest-priced listings on hyperevm secondary markets at the time of execution, starting at the floor and working upward until the budget is exhausted.
4. burn. every bought-back token is sent to the contract's burn() function and permanently destroyed. MAX_SUPPLY stays at 2,222 as the hard cap on mints. circulating supply falls.
5. publish. every buy and every burn is listed on hyperclaude.art/buybacks with tx hashes, token ids, prices paid, and timestamps.

failure modes we will not hide from:

• royalty leakage. hyperevm secondary markets may not enforce erc-2981. if they route around royalties, the buyback fund thins. if it dries up entirely, buybacks pause. we will not subsidize buybacks from treasury reserves or external revenue. that would turn this from a royalty-recycling policy into an ongoing commitment we cannot honestly guarantee.
• nothing to buy. if no listings sit below a reasonable ceiling during a quarter, the unspent buyback budget rolls forward to the next quarter. it does not get rerouted to ops.
• key loss. if the safe signers become compromised or unreachable, the policy is unexecutable until key rotation. rotation events get posted to the site and the account.
• policy change. the policy above is a stated commitment, not a smart-contract enforced one. nothing in solidity prevents the safe from breaking this policy. the only enforcement mechanism is public accountability plus the on-chain record of past behavior. buyers should weigh this accordingly.

---

what this policy is not

holders own a piece of pixel art on hyperevm. nothing more is promised. if buybacks add value, that is a byproduct.

---

verification

• royalty receiver address: (publish after mainnet deploy)
• buyback wallet address: (publish after mainnet deploy)
• contract: (publish after mainnet deploy)
• every quarterly report links tx hashes on the hyperevm block explorer

this document is version-controlled in the project repo. any change produces a new version with a visible diff. the version displayed on the site always matches the latest version in the repo.