// THE LOG · v1.0

The log.

Everything about HOOF — what it is, how it works, and what we're not pretending it is.

CHAPTER I

What is HOOF.

HOOF is a Solana token where every whole-integer balance grants you a unique pixel-art horse.

Hold 0.5 HOOF? It's just a fungible token. Cross 1.0, 2.0, 3.0 — and you become the temporary owner of horses #1, #2, #3, each rendered from the signature of your purchase. Sell back below the integer, and the horse moves on.

The supply is hard-capped at 5,000. No team allocation, no vesting, no inflation. 100% of supply seeded into a permanently-locked SOL/HOOF Meteora pool at launch.

The horses live in the herd gallery. You can browse all 5,000 slots, see which are minted, filter by trait, sort by rarity. Every horse links to a detail page with full provenance.

The short versionBuy ≥ 1 HOOF, get a horse. Buy 10 HOOF, get ten horses. Sell, lose them. The horses are deterministic — same trade signature, same horse, every time, anywhere.
CHAPTER II

The slot mechanic.

How whole-integer ownership actually works.

HOOF has 9 decimals — the Solana standard. So 1 HOOF = 1,000,000,000 base units. The token is fully divisible: you can hold 0.123456789 HOOF.

But slots map to whole integers. Slot #1 is owned by whichever wallet was last seen crossing the 1.0 HOOF threshold upward. Slot #2 by whoever last crossed 2.0. And so on, up to slot #5000.

When you buy enough HOOF to cross from, say, 4.7 to 5.3, you've crossed the 5.0 boundary — slot #5 is now yours. If you sell back to 4.6, slot #5 returns to the pool of unminted slots, and the next wallet to cross 5.0 takes it.

Concrete example

  1. Alice buys 3.4 HOOF. She owns slots #1, #2, #3. Slots #4 and #5 don't exist yet.
  2. Bob buys 7.2 HOOF. He owns slots #1 through #7. But Alice still owns #1, #2, #3.

Wait — that doesn't work. Both Alice and Bob can't own slot #1.

So the actual rule is: slot ownership is assigned by the order in which wallets cross each threshold. Alice crossed 1.0 first; she owns #1. When Bob crosses 1.0, his "first slot" goes to the next available number. In Bob's case, since Alice holds slots #1-#3, Bob's seven slots are #4 through #10.

This means there's a strict ordering: the herd grows monotonically. The 1,000th wallet to cross 1.0 gets a slot somewhere in the high 1000s, depending on how much everyone before it bought. Once a slot is owned, it stays owned until the holder sells below the corresponding integer.

ImportantThis means slot numbers are chronological assignment markers, not floor balances. Slot #1 isn't "the first integer of HOOF" — it's "the slot held by the first wallet to ever cross 1.0 HOOF, until that wallet sells."
CHAPTER III

The renderer.

How the art is actually generated. Read this carefully — it's the heart of the project.

Every horse is described by a 32-byte seed derived from the transaction that made it. The seed is computed:

seed = keccak256(slotId || transferSignature || newOwnerPubkey || prevOwnerPubkey)

The first eight bytes of the seed encode eight visual layers:

ByteLayerRange
0Body palette64 colors (rarity-biased)
1Mane style16 styles
2Pose8 poses
3Tack16 saddle/gear options
4Scenery16 backgrounds
5Aura8 effects
6Eyes8 expressions
7Rarity tiercommon (60%), uncommon (28%), rare (10%), legendary (2%)

Total combinations: ~134 million. With 5,000 slots, the herd samples a tiny slice.

The renderer is a deterministic public function — `hoof-renderer.js`, ~600 lines, MIT-licensed. Given a seed, it always returns the same 24×24 SVG. You can verify any horse locally:

// In your browser console on hoof.fun:
const seed = '20fa030502067f00...';
const svg = HoofRenderer.render(seed);
// open the SVG in a tab — same horse as on the slot page

Where the art lives

When a slot's seed changes (because of a trade), our indexer renders the SVG and pins it to IPFS via Pinata, returning a CID. The CID gets written into the slot's record, and the URL gets returned by the API.

The chain of trust is: anyone can take the on-chain transfer signature, derive the seed, run the public renderer, and get the same SVG. We don't have to be trusted as the source of truth — the seed is.

CHAPTER IV

Liquidity.

One pool, locked liquidity, no rug-pull surface.

$HOOF trades on a single SOL/HOOF Meteora DAMM v2 pool. At launch, 100% of the 5,000 supply is paired with seed SOL and the entire LP position is permanently locked. Neither the team nor anyone else can withdraw it.

This means:

  • You can always sell. The pool is always there.
  • The team can't pull liquidity. Verified on-chain — locked LP NFT.
  • Jupiter routes through it. Standard Solana plumbing.

What it does not mean:

  • The price is stable — it's a memecoin with a tiny float, expect volatility.
  • You won't get sandwiched — Jupiter MEV protection is on, but it's not perfect.
CHAPTER V

What we are not.

Honesty before hype. HOOF is inspired by uPEG. It's not a clone.

uPEG — the Unipeg project on Ethereum — works because Uniswap v4 has hooks: custom code that runs inside the swap, in the same atomic transaction. The trade itself generates the art.

Solana doesn't have v4 hooks. Token-2022 has a `TransferHook` extension, but Meteora DAMM v2 (and most other Solana AMMs) do not support tokens with transfer hooks. So we couldn't build the v4-pure version even if we wanted to.

What we built instead:

  • The chain is the source of truth for ownership (Token-2022 SPL, on-chain balances).
  • The seed is derivable from on-chain transfer signatures (anyone can recompute it).
  • The renderer is a public deterministic function (anyone can run it).
  • Our indexer is the bridge — it watches transfers, computes seeds, runs the renderer, pins to IPFS.

This is not "fully on-chain art generation" — that would require the Solana program calling our renderer in the swap transaction. We don't do that. The art is generated server-side after observing the trade.

It is "fully on-chain provenance" — every horse can be reproduced from public chain data using public code. If our server disappears, anyone can run the renderer and rebuild the herd. That's the property that matters.

The line we won't crossWe will never claim HOOF is "fully on-chain art." It's deterministic-renderer-with-on-chain-seed art. Both phrases are accurate, and we use the second one.
CHAPTER VI

Tokenomics.

FieldValue
Token nameHOOF
Symbol$HOOF
StandardToken-2022 SPL
Decimals9
Max supply5,000 HOOF (5,000 × 10⁹ base units)
Initial circulating5,000 (100%, all into pool)
Mint authorityRevoked at deploy
Freeze authorityRevoked at deploy
Team allocation0%
PoolSOL/HOOF Meteora DAMM v2, LP locked permanently
Trading fee1% (LP fee) — 100% to LP, no platform skim

The team (us) provided seed SOL for the pool. We do not hold any HOOF, do not receive trading fees, and have no operational levers over the token after deploy. The pool collects fees as standard LP rewards, but since the LP position is locked, those fees are effectively trapped in the pool.

CHAPTER VII · LEGAL

Terms.

By using hoof.fun, you agree to:

  • HOOF is an on-chain experiment, not a financial product. We are not your financial advisor.
  • We provide infrastructure — the website, the indexer, the renderer. We do not custody any funds.
  • You are responsible for your own keys, taxes, and jurisdictional compliance.
  • The horses have no claimed real-world value. They are pixel art deterministically generated from on-chain data. They may have collector value, or none. We make no representations.
  • HOOF is not available where token issuance or trading is prohibited.

HOOF is provided "as is" with no warranty.

CHAPTER VIII · LEGAL

Privacy.

What we collect:

  • Public Solana wallet addresses that connect to hoof.fun.
  • Standard server logs (IP, user agent, request paths) — 30 day retention.

What we don't collect:

  • Email, phone, KYC.
  • Browser fingerprints, marketing trackers, cookies.
  • Private keys. Ever.

On-chain data is permanent and public — wallet addresses, balances, transfers are all visible to anyone with a Solana RPC.

For off-chain data removal: privacy@hoof.fun

CHAPTER IX · LEGAL

Risk & disclaimers.

Total loss is possibleHOOF is a tiny-float token with 5,000 supply. The vast majority of memecoins lose most or all of their value. Only trade with what you can afford to lose entirely.

Risks

  • Total loss. The token can go to zero and stay there.
  • Extreme volatility. 5,000 hard-cap means small flows move price hard.
  • Smart contract risk. Token-2022, Meteora, Solana — all software, all has bugs.
  • Indexer dependency. The herd gallery and slot pages depend on our indexer running. If it stops, the chain still has ownership, but the gallery won't update until we restore it.
  • Regulatory risk. Laws change.

What HOOF guarantees

  • Mint and freeze authority are revoked at deploy.
  • LP is permanently locked.
  • The renderer is public, deterministic, and MIT-licensed.
  • The seed for any horse can be recomputed from on-chain data.

What HOOF does not guarantee

  • Anything about price.
  • That horses will be tradable forever.
  • That the platform stays online in your jurisdiction.
  • That a "rare" or "legendary" horse has any market premium.
  • Investment advice. We are not your advisor.