LITEPAPER · HANSOME 2.0
HANSOME ALPACAS
Too Hansome to Be Useful. So we built something useful anyway — meme culture, transparency, discovery, and on-chain tools. No promises we can't keep.
- Network
- Robinhood Chain
- Total Supply
- 1,000,000,000 HANSOME
- Tax
- 0%
- Contract
- Immutable, non-mintable
00
Founder Letter
Too Hansome to Be Useful. That was the joke. An alpaca that won the genetic lottery and had absolutely nothing practical to offer. We started HANSOME ALPACAS because that made us laugh — and because meme culture is allowed to be ridiculous before it is allowed to be useful.
HANSOME 2.0 is the next chapter of the same joke: Too Hansome to Be Useful. So we built something useful anyway. Not an enterprise analytics company. Not a whitepaper full of buzzwords. A meme brand that also ships transparency, discovery, and on-chain tools — Scan, Score, and eventually Explore — while keeping the alpaca culture intact.
What we can promise today is still narrower than a hype deck: a fixed, non-mintable supply; an immutable contract; public wallets; honest status labels; HANSOME Scan in Public Beta on Robinhood Chain; and a limited 3-Day ETH Shield promotional trial (LIVE when the campaign window is open — not insurance). Explore remains PLANNED. Launch-related work is CONDITIONAL. Genesis NFT / Alpacas vs Cougars sits under LEGACY. Public Beta means usable and honest — not a finished guarantee of safety or completeness.
This document is the public record of that shift. It says what is real, what is in progress, what is planned, and what is legacy. If HANSOME is still around in a year, we want it to be because a real community stuck with a handsome alpaca that finally learned how to be a little useful — without forgetting it was a meme first.
Thanks for reading this far. Stay Hansome.
— The HANSOME ALPACAS team
01
Introduction / What is HANSOME?
HANSOME ALPACAS is a meme-first project on Robinhood Chain: fixed-supply, zero-tax ERC-20 $HANSOME, trading against ETH through a Uniswap v4 concentrated-liquidity pool. The identity is still the joke — Too Hansome to Be Useful — and the brand is still alpaca meme culture, not a corporate dashboard.
HANSOME 2.0 adds a second layer on top of that meme: transparency, discovery, and on-chain tools. The direction is Meme + Transparency + Discovery + On-chain Tools. HANSOME Scan (Public Beta) lets people inspect Overall Token Score, Structural Score, Analysis Coverage, liquidity, supply & burn, creator behaviour, holders, and contract risk — without confusing popularity for safety. Explore is planned for category and trending discovery later. None of that replaces the meme — it gives the meme something useful to do.
What already exists today: immutable, non-mintable $HANSOME; official liquidity (including Titan-locked position #47299); public wallets; /transparency as the live balance source of truth; HANSOME Scan at /scan in Public Beta (English & Chinese); and the limited 3-Day ETH Shield trial at /shield (LIVE while the campaign is open). What is not live: Explore, public Analytics / Most Searched dashboards, Just Launched, or a finished “everything locked forever” oracle. Status labels in this litepaper are deliberate.
What is HANSOME?
HANSOME ALPACAS (ticker: HANSOME) is a fixed-supply, zero-tax ERC-20 on Robinhood Chain. Its core identity remains meme culture: an extremely handsome alpaca that was never designed as a serious utility product.
Around that token, HANSOME 2.0 ships optional tools and programs with clear status labels: Scan & Score (PUBLIC BETA), 3-Day Limited ETH Shield (LIVE promotional trial — not insurance), Explore (PLANNED), and a conditional Launch path. The token contract itself does not mint utility into existence; tools and trials are separate surfaces with their own maturity. Genesis NFT / Alpacas vs Cougars GameFi is documented under Legacy.
02
Meme Identity
Too Hansome to Be Useful.
Too Hansome to Be Useful. So we built something useful anyway.
HANSOME is a meme brand first. The alpaca, the jawline, the uselessness — that is the culture. Tools come second, as a punchline with a purpose: if we are going to be here after the first hype cycle, we might as well ship transparency and discovery that other meme coins usually skip.
We are not repositioning as an enterprise analytics corporation. Score is not a sales pitch for institutional risk desks. It is a hansome way to look at structural on-chain signals, HANSOME Level (market activity branding), and Analysis Coverage — while keeping the meme voice.
Meme
Culture, jokes, contests, and a mascot people actually want to share. If it stops being funny, the rest does not matter.
Transparency
Public wallets, verifiable liquidity ops, and /transparency as the live source of truth for balances — not vibes.
Discovery
Helping people find and contextualize tokens through Explore (PLANNED) and clear Category / Trending labels — without selling safety.
On-chain Tools
HANSOME Scan & Score (PUBLIC BETA): Overall vs Structural scores, Analysis Coverage, liquidity & burn intelligence — separate axes, honest status.
03
Brand Hierarchy
HANSOME 2.0 is a stack of named products under one meme brand. Each line has a status label. Do not collapse them into “everything is finished” or “nothing works yet.”
HANSOME Scan
PUBLIC BETAPublic Robinhood Chain CA scanner at /scan — Overall Token Score, Structural Score, HANSOME Level, Analysis Coverage, liquidity, supply & burn, creator, holders, and contract risk. Informational only; still improving.
HANSOME Score
PUBLIC BETAOverall Token Score (broader assessment) and Structural Score (on-chain risk & transparency), 0–100 each. Not popularity, not price prediction, not a rug/moon oracle. Always read with Analysis Coverage / Data Confidence.
3-Day Limited ETH Shield
LIVELimited promotional trial at /shield for official Swap purchases (~USD 10–100 protected via frozen ETH thresholds). 10 slots; Agreement v2; manual ETH payout after review. Not insurance. Not a Solidity product. Campaign window and remaining slots apply.
HANSOME Explore
PLANNEDDiscovery UI for categories, tags, and trending — after Scan Public Beta is stable enough. Not live today.
HANSOME Launch
CONDITIONALAny launch-related product path depends on tooling maturity, community need, and explicit go decisions. Not a dated promise.
Genesis NFT / Alpacas vs Cougars
LEGACYSeason-1 GameFi and mint flywheel documentation live under Legacy. Preserved for holders and history — not the primary HANSOME 2.0 product narrative.
04
HANSOME Scan & Score
HANSOME Scan is the public inspection surface at /scan — free, no signup, Robinhood Chain contract addresses. Inside Scan, two scores stay separate: Overall Token Score (broader assessment ordinary users see first) and Structural Score (structural / on-chain risk & transparency). Both ship in Public Beta with Analysis Coverage (Data Confidence).
Structural Score measures structural / on-chain risk and transparency signals only. It is not a popularity contest, not volume fame, and not financial advice. Overall Token Score also reflects market/liquidity health, holder adoption, activity, maturity, and data completeness — still not a safety guarantee or price prediction.
HANSOME Level is meme-branded market/activity presentation (not safety). Liquidity Intelligence covers detectable Uniswap v2 / v3 / v4 structures with pool USD, locked vs unlocked, and per-position detail when reliable. Supply & Burn, Creator Behaviour, Top Holders, wallet relationships, and Contract Risk are part of the same Public Beta surface.
Public Beta means the product is usable today and labeled honestly — not that every token finishes every deep check, every locker is supported, or scores are investment advice.
Try the Public Beta: paste a Robinhood Chain token contract address. Interface available in English and Chinese.
OPEN HANSOME SCAN →Public Beta capabilities (today)
- • Scan ERC-20 contract addresses on Robinhood Chain
- • Overall Token Score vs Structural Score (different meanings — keep them separate)
- • HANSOME Level = market/activity branding — not a safety rating
- • Analysis Coverage / Data Confidence beside scores
- • Overall Score rating bands: VERY WEAK · WEAK · FAIR · GOOD · STRONG (tier labels only — not SAFE/BUY/SELL)
- • Liquidity Intelligence: Uniswap V2 / V3 / V4 structure, pool USD, locked vs unlocked, $/% when reliable, per-position detail
- • Supply & Burn: total supply, known burned + %, supply excluding known burns, burn function / automatic / admin signals
- • Creator Behaviour, Top Holders sample, wallet relationship / concentration signals, Contract Risk
- • Fast Scan first, then progressive Deep enrichment; repeat scans of the same CA are typically faster when a recent result can be reused
- • English and Chinese Scan UI
What each module shows
Overall vs Structural
Overall answers “how does this token look as a whole right now?” Structural answers “what structural / transparency risks show on-chain?” Divergence is expected — clean-but-quiet tokens and hot-but-risky tokens can look different on the two scores.
HANSOME Level
Meme-themed label for recent market activity (volume / txs). It does not measure safety, quality, or investment potential, and it does not rewrite Structural deductions.
Analysis Coverage
How much reliable data we have for this token. Incomplete analysis should look incomplete — Coverage ≠ safety.
Supply & Burn
Total supply, Known Burned (recognized burn/dead evidence + %), supply excluding known burns, and mechanism signals (holder burn, automatic, admin). Known Burned ≠ arbitrary inaccessible wallets. Burns do not boost scores.
Creator · Holders · Contract Risk
Creator sell / transfer-then-sell signals from indexed history; top-holder sample and concentration / relationship cues; contract risk surfaces such as mint, pause, blacklist, tax, proxy, admin, and privileged burn when detected.
Liquidity Intelligence
Multi-version Uniswap pool/position reading with lock status, USD when priced, and honest Unknown / Incomplete when evidence is thin. Detail below.
Overall Score rating bands
Bands color the Overall Token Score tier only. They are not safety labels and not buy/sell signals.
- • 80–100 — STRONG
- • 60–79 — GOOD
- • 40–59 — FAIR
- • 20–39 — WEAK
- • 0–19 — VERY WEAK
How a scan runs (user view)
- • Fast Scan returns a usable first screen quickly (metadata, supply, holders sample, market, early burn signals, provisional scores).
- • Deep Analysis continues afterward for heavier checks (liquidity positions, creator history, relationships, deeper burn enrichment).
- • Scores may show as provisional until Deep finishes; some stages may settle as partial or temporarily unavailable.
- • Refresh can retry incomplete deep checks. Recent results for the same contract are often reused so repeat scans feel faster.
Accuracy & limitations (read this)
- • Informational only — not safety guarantees, not investment advice, not price predictions.
- • Unknown ≠ No / Safe. Missing data must not be read as “clean.”
- • One locked LP position ≠ all liquidity locked.
- • Supporting Uniswap V2 / V3 / V4 structures ≠ supporting every third-party locker.
- • Known Burned = recognized burn evidence — not every wallet that looks “stuck” or inaccessible.
- • Deep may continue after Fast; some results can be partial or temporarily unavailable on heavy tokens.
- • Architecture in plain language: Fast → provisional → Deep enrich → final or honest partial. No claim of instantaneous perfect coverage on every CA.
Score principles (non-negotiable)
- • Overall ≠ safety guarantee. Structural ≠ popularity.
- • Small liquidity, few holders, or low volume ≠ automatically “unsafe” on Structural Score.
- • Liquidity size / slippage may inform Overall; ownership / withdrawal risk may affect Structural Score.
- • Missing data lowers Analysis Coverage; it does not invent safety via a fake high Structural Score.
- • $HANSOME never buys a higher Overall or Structural Score. Holdings of HANSOME do not boost another token’s scores.
- • Category, Trending, and paid placement never affect Overall or Structural scores.
- • One locked position does not mean locked liquidity. Pool ≠ position; version ≠ locker; token-level aggregate must reflect all material positions across searched Uniswap versions.
Uniswap Liquidity & Lock Intelligence (v2 · v3 · v4)
PUBLIC BETAMainstream scanners may provide limited or incomplete visibility into Uniswap positions and third-party lockers on Robinhood Chain. That visibility gap can leave holders looking at a pool TVL number without knowing who can withdraw liquidity, whether a locker is verified, or when a lock expires.
HANSOME Scan Public Beta addresses that gap for readable pool / position / locker evidence — not as a claim that every locker in existence is decoded, and not with “first in the world” marketing.
Critical: a single Titan-locked Position NFT — or a single Uniswap version — must never be presented as “all liquidity locked” when other removable positions exist or when other versions were not searched.
Public Beta capabilities
- • Probe active Uniswap v2 / v3 / v4 deployments on Robinhood Chain (factory / PoolManager paths)
- • Pool ≠ position: pair/pool identity vs ownership slots (v2 LP tokens, v3/v4 position NFTs)
- • Per-position owner, locker type, lock/unlock, range, and liquidity / USD where decodable
- • Token-level aggregate across versions: ALL LOCKED · MIXED · ALL UNLOCKED · UNKNOWN / INCOMPLETE
- • Position counts (detected / locked / unlocked / unknown) and INCOMPLETE COVERAGE warnings
- • Lock distribution $ / % only when economically comparable; otherwise “unavailable” with reason
- • Locker name when recognized (Titan supported first — not every third-party locker)
- • Explicit split: protocol version support vs locker decode support
- • Separation of size vs ownership / withdrawal risk in the UI and Score inputs
Explicit lock statuses
- • Position: LOCKED — VERIFIED ON-CHAIN
- • Position: UNLOCKED / EOA-CONTROLLED
- • Position: LOCK DETECTED — EXPIRY UNKNOWN · UNSUPPORTED LOCKER · UNABLE TO DETERMINE
- • Token aggregate: ALL LOCKED · ⚠️ MIXED — LOCKED + REMOVABLE · ALL UNLOCKED · UNKNOWN / INCOMPLETE
How to read these statuses
- • One locked position does not mean locked liquidity.
- • Supporting Uniswap v2/v3/v4 structures ≠ supporting every third-party locker.
- • Unknown ≠ unlocked. “UNKNOWN / INCOMPLETE” or INCOMPLETE COVERAGE means enumeration or evidence is insufficient — never treat a single locker hit or single version as fully locked.
- • A detected lock ≠ “safe.” MIXED means removable liquidity still exists alongside any verified lock.
- • Liquidity visible does not necessarily mean liquidity understood. Pool depth alone can be a misleading comfort signal if withdrawal control is opaque.
Meme coins live and die on trust theater. Showing a big liquidity number without lock / ownership context is how that theater happens. We’d rather say “we don’t know yet” with a clear status than invent safety.
This is a visibility problem we encountered building on Robinhood Chain with Uniswap v4 and third-party lockers (including Titan), while v2 and v3 are also active on-chain. Closing that gap carefully is part of what Scan is for.
Relationship to HANSOME Score
- • Size ≠ Lock Status ≠ Ownership / Withdrawal Risk ≠ Range Status. Keep them separate in the product.
- • Small liquidity ≠ unsafe. Large liquidity ≠ safe.
- • Score uses token-level aggregate ownership (e.g. MIXED), not a single locked NFT or a single Uniswap version.
- • Liquidity size remains slippage / depth context for Overall — not a popularity boost and not an automatic Structural penalty for being small.
- • Missing locker or multi-version coverage lowers Analysis Coverage and may yield UNKNOWN / INCOMPLETE — it does not invent “unlocked” or “fully locked.”
Status: PUBLIC BETA — Uniswap v2/v3/v4 structure reading ships today; lock verification covers known lockers (Titan path mature). Unsupported lockers and incomplete enumeration show as Unknown / Incomplete. HANSOME’s own multi-position MIXED case (Titan-locked #47299 plus removable Treasury positions) is a reference example of honest aggregation — not proof that every token’s locker set is fully decoded.
05
Overall · Structural · HANSOME Level · Trending · Category · Analysis Coverage
Discovery axes plus Analysis Coverage. They are strictly separated. Mixing them is how meme tools become dishonest.
Overall Token Score
Broader 0–100 assessment ordinary users see first (structural + market health + adoption + activity + maturity + analysis coverage). Not a safety guarantee. Shown with rating bands VERY WEAK → STRONG.
Structural Score
Structural risk & transparency (0–100). Not popularity. Low volume alone does not mean unsafe.
Activity / HANSOME Level
Raw Activity remains Low / Medium / High (engine). The UI presents it as branded HANSOME Level (e.g. 😐 KINDA HANSOME). Presentation rename only — it does not change Structural Score, Overall Score, Analysis Coverage, or risk deductions. Overall may still incorporate activity numerically from volume/txs.
Trending
Relative momentum (PLANNED with Explore). Trending ≠ safer. Organic Trending is never pay-to-rank.
Category
Taxonomy labels (e.g. Animal Memes, DeFi, Gaming). Category does not affect Overall or Structural scores. Explore taxonomy remains PLANNED.
Analysis Coverage / Data Confidence
Data completeness and sample maturity (shown beside scores; also a small Overall input). Coverage ≠ safety. New or thinly indexed tokens should show uncertainty here.
Hard separations
- • Overall ≠ Structural ≠ Activity ≠ Trending ≠ Category.
- • Overall ≠ safety guarantee. Structural ≠ popularity. HANSOME Level ≠ safety.
- • Analysis Coverage = data completeness / maturity — not a second popularity meter.
- • Trending ≠ safer.
- • Category does not affect Overall or Structural scores.
- • Promoted ≠ organic Trending. Any future paid placement must be labeled Promoted and must never mix into organic Trending or scores.
- • $HANSOME never buys Overall or Structural Score.
06
HANSOME Explore
Explore is the planned discovery layer: browse by Category / tags, surface Trending with transparent relative-momentum logic, and keep Promoted placements clearly labeled if they ever exist.
Public Analytics / Most Searched / visitor analytics dashboards and Just Launched remain PLANNED as public discovery surfaces — do not read them as shipped products. Private aggregate ops tooling (if any) is not a public Analytics product.
Explore depends on Scan Public Beta stability and taxonomy workflows. It is PLANNED — not described as live in this document.
Until Explore exists, discovery remains informal (community, listings, charts, and individual /scan lookups). That is fine. We would rather ship Explore late and honest than early and fake.
07
3-Day Limited ETH Shield
3-Day Limited ETH Shield is a small promotional trial for official Buy HANSOME swaps on the site Swap (Universal Router). It is LIVE while the campaign window is open and slots remain — not a permanent product line, not insurance, and not a funded or locked insurance pool.
Rules are formalized as Agreement v2 (shield-agreement-v2.0). Capacity is 10 policies total. Policies #1–5 use a 50% compensation ratio; policies #6–10 use 30%. Protected purchase size is roughly USD 10–100, expressed as ETH amounts frozen from an ETH/USD reference at campaign open.
Observation runs 72 hours from the purchase block time. The downside trigger is −30%. At expiry the wallet must still hold at least 50% of the protected HANSOME amount. Qualifying official Swap purchases can auto-activate after terms signature and tx confirmation — no Solidity Shield contract, and no automatic on-chain ETH transfer for payout.
Eligible for Compensation ≠ Paid. Any promotional ETH payout is manual after admin review. Approximately USD 400 is the theoretical maximum total campaign liability across all 10 policies — not the amount available to one participant.
Key facts (v2)
- • 10 slots total — #1–5 up to 50% of protected purchase; #6–10 up to 30% (subject to tier caps)
- • Protected size ≈ USD 10–100 via ETH thresholds frozen at campaign open
- • 72-hour observation window from purchase block time; −30% trigger; hold ≥50% protected HANSOME at expiry
- • Agreement v2 must be wallet-signed before Swap; signature confirms terms only (no spend authority)
- • Happy path: Agreement → official Swap → auto-read purchase tx → activate; one active policy per address; each purchase tx usable once
- • Manual payout after review; no auto ETH transfer; no new Shield Solidity
- • ~USD 400 = theoretical max total campaign liability (5× tier-1 cap + 5× tier-2 cap) — not per participant
How it works
- Open /shield while the campaign is open, read Agreement v2, check the box, and wallet-sign terms.
- Buy HANSOME with ETH on the official Swap (fee tier 500). Success can save the tx for Shield.
- Return to /shield — confirm the auto-found purchase (or paste the hash) and sign to activate.
- Observation runs 72 hours. Hold ≥50% of protected HANSOME at expiry. Trigger: −30%.
- If eligible after evaluation, promotional ETH payout is manual. Eligible ≠ Paid.
What this is not
- • Not insurance, not a guarantee, not a funded/locked product claim
- • Not an on-chain claim contract — no Solidity Shield; payouts are off-chain / manual
- • Not open when the campaign is closed, sold out, or outside the published window
- • Not a promise that every applicant receives compensation; rules, holding, and review apply
- • Live status, remaining slots, and frozen ETH thresholds are always authoritative on /shield and status APIs
Check whether the campaign is open, read Agreement v2, and see remaining slots. English and Chinese UI.
OPEN 3-DAY SHIELD →08
$HANSOME Utility
$HANSOME is still a meme token first: fixed supply, 0% tax, immutable contract, Robinhood Chain. There is no staking product and no yield mechanism baked into the token contract.
HANSOME 2.0 utility is ecosystem-level, not a list of invented holder perks. The token anchors the brand, treasury, and liquidity; tools (Scan Public Beta, Explore planned) and limited programs (3-Day Shield promotional trial) sit around the same culture and transparency standard. This litepaper does not invent new Genesis NFT holder benefits.
If future tool access, community programs, or branded products attach more concrete utility, they will be announced with dates and status labels — not silently implied here.
Meme & brand anchor
The cultural center of HANSOME ALPACAS — contests, content, and community identity.
Treasury & liquidity fuel
Official wallets and Uniswap v4 liquidity policy (see Tokenomics, Treasury, Liquidity). Live balances: /transparency.
Tools ecosystem
Scan & Score PUBLIC BETA; 3-Day Shield LIVE trial (promotional, not insurance); Explore PLANNED; Launch CONDITIONAL. Utility grows with shipped surfaces — not with slogans.
Legacy GameFi (separate)
Genesis / Alpacas vs Cougars economics remain documented under Legacy. They are not the primary 2.0 utility story.
09
Tokenomics
- Treasury90%
- Liquidity5%
- Founder5%
Total Supply
1,000,000,000 HANSOME
The supply was fixed at deployment and cannot change. There is no mint function in the contract — not for the team, not for an owner, not for anyone.
Initial Distribution (At Launch)
This is how the supply was split across the project's three token-holding wallets on day one — not how much each wallet holds today:
Liquidity
Deployed into the official Uniswap v4 pool at launch.
50,000,000 HANSOME (5%)
Treasury
Its starting balance, not its current one — see the note below and Treasury Policy for what's happened since.
900,000,000 HANSOME (90%)
Founder
Founder allocation.
50,000,000 HANSOME (5%)
These percentages describe the initial split at launch, not a live snapshot. Current balances move over time — most notably the Treasury's, which decreases as tokens are deployed into official liquidity under the Treasury and Liquidity policies below. A lower Treasury balance almost always means tokens were converted into a public, verifiable liquidity position, not that they were sold. For what every wallet actually holds right now, go to /transparency — that page, not this document, is the live source of truth.
Why fixed supply?
A mint function is a standing promise that the rules can change later. Removing it entirely means no one — including the team — can ever dilute holders, no matter how the project evolves. The tradeoff is real: it also means the project can never simply print its way out of a liquidity problem. That constraint is treated as a feature, not a bug, and it directly shapes the Treasury and Liquidity policies below.
10
Treasury Policy
The Treasury wallet started with the largest single allocation of HANSOME — 90% of supply at launch. Its balance today is lower than that, and keeps changing over time, mainly because deploying tokens into official liquidity is itself a Treasury action (see below). This section describes policy — what the Treasury is for and how it's used. For what it actually holds right now, that's always /transparency, never this document. It's a single, publicly-visible wallet — not yet split into named sub-funds with fixed percentages for each purpose.
Liquidity
Primary current use
Most Treasury deployment to date has gone toward funding and reinforcing the official Uniswap v4 liquidity position. This is the main reason the Treasury's current balance is lower than its initial 90% allocation — those tokens weren't sold, they were converted into a public, verifiable liquidity position (see the Liquidity Wallet on /transparency and the Liquidity Policy below).
Community
Planned — TODO
A dedicated allocation or budget for community incentives has not been finalized. Any future commitment here will be published, not assumed.
Development
Planned — TODO
No formal development sub-budget has been carved out yet. HANSOME 2.0 tooling (Scan Public Beta today; Explore planned) is the intended product direction those funds would support once a budget is published — not an open-ended promise of spend.
Team
See Founder allocation
The only team-linked allocation is the Founder wallet (50,000,000 HANSOME, 5%). There is no separate, additional team fund inside the Treasury.
Transparency
Every wallet referenced above is public. Addresses and Uniswap v4 pool/position details are listed below; current balances are read live from the contract at /transparency. That page, not this document, is the source of truth for what each wallet holds today — the figures below are each wallet's initial allocation at launch, not a live number.
Deployment Wallet
Contract deployment and technical operations.
Initial allocation: 0%
Liquidity Wallet
Official Uniswap v4 liquidity management.
Initial LP deposit: 50,000,000 HANSOME + 0.075 ETH
Treasury
Treasury, ecosystem growth, partnerships, future liquidity, marketing and development.
Initial allocation: 900,000,000 HANSOME (90%) — current balance is lower; see /transparency
Founder Wallet
Founder allocation.
Initial allocation: 50,000,000 HANSOME (5%)
11
Liquidity Policy
Concentrated Liquidity
HANSOME trades through a Uniswap v4 pool using concentrated liquidity: capital is deployed across a defined price range instead of the full 0-to-infinity curve. This makes each dollar of liquidity work harder inside that range, at the cost of the position becoming fully one-sided if price moves outside it. That tradeoff is deliberate, not accidental — and it means liquidity depth is a policy decision, not a set-and-forget default.
Long-Term LP Strategy
The current approach favors a small number of well-understood positions over constant micromanagement. The intended long-term shape is a barbell: one tighter position for capital efficiency near the current price, plus at least one wider or full-range position sized as a standing backstop, so a single large trade can never fully exhaust tradeable liquidity in one direction. As of July 2026, that barbell is live — see Liquidity Optimization below for what changed.
LP Fees
The pool carries a 0.05% swap fee, which accrues to whoever holds the liquidity position — currently the Treasury. These fees are real, on-chain revenue generated independently of any token tax, and the intent is to periodically collect and recycle them back into liquidity rather than let them sit unclaimed.
On-Chain Verification
The official Uniswap v4 LP position (#47299) is locked via TitanLockerManagerV2 until July 15, 2027. That isn't something you have to take our word for — the lock contract and the lock transaction are both public on Blockscout, so anyone can verify it independently.
Liquidity Optimization (July 2026)
In July 2026, the Treasury carried out a liquidity optimization on the official Uniswap v4 pool. The original 365-day locked position (#47299, see On-Chain Verification above) was left completely unchanged — nothing about that lock was touched or unwound. Alongside it, the Treasury added two new, Treasury-owned liquidity positions: a narrow-range position sized to reduce swap slippage near the current price, and a wider-range position held as additional downside protection. Combined, this meaningfully increased the capital backing official liquidity beyond the original locked position alone. This was funded through disclosed Treasury liquidity management, and every step of it is publicly verifiable on-chain.
Improved Trading Experience
Since the optimization above, swap slippage on the official pool has been reduced noticeably at typical trade sizes. Medium and larger trades now execute more efficiently, with less price impact than before. Market depth is better on both sides of the current price, and the overall experience for anyone buying in for the first time is meaningfully smoother than it was.
Multiple LP Positions
A single concentrated position has a hard capacity limit in each direction. Running more than one position — at different ranges, potentially funded from different sources — is the standard way serious concentrated-liquidity operators avoid that limit becoming a single point of failure. As described in Liquidity Optimization above, this is now implemented for HANSOME: the original locked position runs alongside two additional Treasury-owned positions.
Why We Won't Constantly Chase Price With Reactive Liquidity
Adding liquidity immediately after every large trade, in direct reaction to that trade, tends to just get consumed by the next large trade — it's a treadmill, not a strategy. Instead, liquidity decisions are meant to be sized ahead of expected activity and tied to durable milestones (like sustained market-cap tiers), not to the most recent headline or the most recent scare.
12
Revenue Strategy
HANSOME has 0% transaction tax by design, so it doesn't generate revenue the way older “tax token” meme coins did. Funding for liquidity and for HANSOME 2.0 tools has to come from real sources — not from printing more HANSOME. Here's what's running today, what's in development, and what remains exploratory. Nothing below is guaranteed.
LP Fees
ActiveThe 0.05% Uniswap v4 pool fee is the one revenue source already running today, scaling automatically with trading volume. It's small, it's real, and it's the only item on this list that does not depend on shipping a new product.
Scan & Score ecosystem
IN DEVELOPMENTHANSOME Scan Public Beta is live as a free product. Any future monetization (if any) will be disclosed separately and must never include paying for a higher Score or organic Trending rank. Monetization itself is not a live revenue line today.
Explore discovery
PLANNEDIf Explore ships, labeled Promoted placements (if ever offered) would be the only paid discovery surface — never mixed into Score or organic Trending. Explore itself remains planned.
Merchandise
ExploratoryApparel, plushies, stickers — a natural fit for the mascot. Nothing has been designed, produced, or sold yet. We'd rather do it right once there's a community big enough to want it.
Partnerships
ExploratoryNo partnerships, sponsorships, or cross-promotions are assumed. If the right one fits the brand, it will be announced when real — not listed as live here.
13
Roadmap — HANSOME 2.0
Phased roadmap with honest status labels. Current milestones: HANSOME Scan Public Beta + limited 3-Day ETH Shield trial (LIVE while open). Conditional items require explicit go decisions. Planned items are not live.
- Phase 0
Foundation (shipped)
Completed- Deploy fixed-supply, non-mintable, immutable HANSOME contract on Robinhood Chain
- Create the official Uniswap v4 ETH/HANSOME liquidity pool
- Launch the public website, swap interface, and /transparency page
- Lock official Uniswap v4 LP position (#47299) via Titan Locker — unlock ~2027-07-15
- Treasury-led liquidity optimization: multiple positions alongside the locked NFT
- Publish litepaper + Legacy GameFi documentation
- Phase 1
Scan & Score Public Beta
PUBLIC BETA- HANSOME Scan at /scan for Robinhood Chain CAs — PUBLIC BETA
- Overall Token Score + Structural Score + Analysis Coverage / Data Confidence
- HANSOME Level (market/activity branding, not safety) + Overall rating bands
- Liquidity Intelligence across Uniswap V2 / V3 / V4 + locked/unlocked + per-position detail
- Supply & Burn + Creator Behaviour + Top Holders + Contract Risk
- Fast Scan + progressive Deep enrichment; faster repeat scans when a recent result can be reused
- English / Chinese Scan UI
- Continued reliability & coverage hardening inside Public Beta (not a “finished forever” claim)
- Phase 1b
3-Day Limited ETH Shield (v2)
LIVE- Limited promotional trial at /shield — LIVE while campaign open (not insurance)
- 10 slots; #1–5 50% / #6–10 30%; ~USD 10–100 protected via frozen ETH thresholds
- Agreement v2; 72h observation; −30% trigger; hold ≥50% at expiry
- Auto-activate from official Swap purchase tx on the happy path
- Manual payout after review; no Shield Solidity; no automatic ETH transfer
- ~USD 400 theoretical max total campaign liability (not per participant)
- Phase 2
Explore & taxonomy
PLANNED- Category / tag taxonomy with manual verify workflow — PLANNED
- HANSOME Explore discovery UI (/explore) — PLANNED (not live)
- Trending as relative momentum; Promoted never mixed into organic Trending or Score
- Public Analytics / Most Searched — PLANNED (not a public product today)
- Just Launched — PLANNED (not live)
- Phase 3
Launch path
CONDITIONAL- HANSOME Launch-related product work — CONDITIONAL on tooling maturity and explicit go decisions
- No fixed listing dates, no price targets, no promised exchange outcomes
- CoinGecko / CoinMarketCap applications remain process items, not roadmap guarantees
- Legacy
Genesis NFT / GameFi
LEGACY- Alpacas vs Cougars gameplay + GameFi economic model preserved under Legacy
- Mint flywheel documentation preserved under Legacy — not the primary 2.0 narrative
14
Legacy: Genesis NFT + GameFi
This section preserves Season-1 GameFi material: gameplay overview, the GameFi economic model, and the mint-revenue flywheel. It is LEGACY relative to HANSOME 2.0’s meme + tools direction.
Nothing here invents new NFT holder benefits. For live game mechanics, use the Game surface. For economic math, use the Legacy economic-model documents linked below.
Gameplay Overview (Legacy)
LEGACY — HANSOME: Alpacas vs Cougars is more than a collectible NFT project.
HANSOME: Alpacas vs Cougars
One world.
Two destinies.
🦙 Survive as an Alpaca.
🐆 Hunt as a Cougar.
Every NFT is playable.
Every decision matters.
Every Genesis NFT has a role inside an on-chain survival game where players compete, survive, and earn rewards.
Players may become:
- 🦙 Alpacas — survive, hide, and outlast the hunt.
- 🐆 Cougars — track, hunt, and eliminate prey.
Each day, players make strategic decisions through the game's:
Commit Move → Reveal Move → Settlement → Claim Rewards
Different NFT traits and abilities influence gameplay, creating a unique experience for every holder.
This Litepaper provides only a simple overview of the legacy game ecosystem.
For detailed gameplay mechanics, NFT abilities, locations, reward pools, settlement rules, and claiming instructions, please visit the Game section.
Want to learn how the game works?
This Litepaper provides only a high-level Legacy overview.
- • Daily gameplay loop
- • NFT abilities
- • Reward pools
- • Locations
- • Hunting mechanics
- • Settlement rules
- • Claim rewards
GameFi Economic Model (Legacy)
LEGACY — HANSOME: Alpacas vs Cougars is a day-settled GameFi economy on Robinhood Chain. Daily rewards are paid from the GameTreasury balance of $HANSOME — they are not newly minted. Outcomes depend on participation, decisions, treasury health, and market conditions. This section does not promise profits or fixed yields.
The full mathematical analysis — emission bands, pool splits, Alpaca vs Cougar economics, game-theory framing, treasury runway, and why the design targets long-term sustainability versus typical P2E — is published as a standalone Legacy report for players and researchers.
What the model explains
- • Daily pool Rd = f(G) with implemented step bands (R0 = 400,000 when G ≥ 0.70·G0)
- • Launch Treasury: initially funded with 30,000,000 HANSOME → starting band 80,000/day; higher bands unlock automatically as Treasury grows (60M / 120M / 210M)
- • Pool split: Alpaca 80% · Cougar base 10% · Hunting 10%
- • Conservation: player claims + penalties + unallocated = Rd
- • Protocol band reference G0 = 300,000,000 (design scale); gross runway illustration G0 / R0 ≈ 750 days at top band (actual life varies with funding, step-downs, sinks, and claims)
- • Two-sided value: player agency and NFT utility alongside sustainable ecosystem runway
- • Long-term design: fixed-supply rewards from GameTreasury, step-down emission, progressive treasury expansion without contract upgrades, Alpaca/Cougar mutual demand (no profit guarantees)
Rewards are contingent. Missing Reveal, safe mode (G < Gsafe), or population imbalance can reduce or eliminate a day’s earnings. Not investment advice. Legacy documentation — not the primary HANSOME 2.0 product narrative.
Mint Flywheel (Legacy)
LEGACY — Building a sustainable GameFi ecosystem was a Season-1 vision around Genesis mint revenue.
Revenue generated from the HANSOME: Alpacas vs Cougars NFT mint was described as reinvested into the HANSOME ecosystem through:
- 🎮 Game development
- 📢 Community events & rewards
- 🤝 Marketing & partnerships
- 💧 Ecosystem growth
This flywheel remains documented for Legacy context. HANSOME 2.0’s primary loop is meme culture → transparency → tools → discovery — not mint-first growth.
A stronger ecosystem still matters. The sequencing and product center of gravity have shifted.
NFT Mint Revenue
Game Development
More Players
Stronger Community
Ecosystem Growth
Further Development
15
Community
Hype is a spike. Community is a floor. HANSOME would rather keep a hundred people who find the alpaca funny — and who care about honest status labels — than ten thousand who forget the ticker next week.
Telegram is active: meme contests, giveaways, AMAs, and community events. Marketing and KOL work exist to bring in people worth keeping, not to paper over missing products.
HANSOME 2.0 asks the community for the same deal as always: meme culture first, transparency always, and tools that earn trust by shipping with clear LIVE / PUBLIC BETA / IN DEVELOPMENT / PLANNED / CONDITIONAL / LEGACY labels.
16
Long-Term Vision
There is no guarantee this works. The shape we want is a loop: meme culture that funds honesty, honesty that makes tools trustworthy, tools that make discovery useful — without confusing Public Beta with “finished forever,” or roadmap with live.
Today HANSOME sits early in that loop: strong meme identity, real on-chain transparency, Scan Public Beta shipping, limited 3-Day Shield trial when open, Explore planned, Launch conditional, GameFi under Legacy. This document will be updated as statuses change — including admitting when something slips.
17
FAQ
The same meme brand — Too Hansome to Be Useful — plus a tools direction: transparency, discovery, and on-chain Scan/Score (PUBLIC BETA), a limited 3-Day ETH Shield promotional trial (LIVE when open — not insurance), Explore (PLANNED), and Launch (CONDITIONAL). Genesis GameFi is Legacy.
DOC
Documents
Official downloadable files served from /docs on this site. Prefer PDF for sharing; Markdown for reading in a text editor. GameFi economic-model files are Legacy documentation.
- PDF ↓
Litepaper (English PDF)
/docs/litepaper-en.pdf
- PDF ↓
Litepaper (Chinese PDF)
/docs/litepaper-zh.pdf
- PDF ↓
Legacy — GameFi Economic Model (English PDF)
/docs/HANSOME_GAME_ECONOMIC_MODEL_EN.pdf
- PDF ↓
Legacy — GameFi Economic Model (Chinese PDF)
/docs/HANSOME_GAME_ECONOMIC_MODEL_ZH.pdf
- Open
Legacy — GameFi Economic Model (English Markdown)
/docs/HANSOME_GAME_ECONOMIC_MODEL_EN.md
- Open
Legacy — GameFi Economic Model (Chinese Markdown)
/docs/HANSOME_GAME_ECONOMIC_MODEL_ZH.md
18
Changelog
A record of this document's own revisions — not the whole project's history, just this litepaper.
- v2.2August 2026
- · Documented 3-Day Limited ETH Shield (Phase 15C v2) as LIVE promotional trial: /shield section, brand hierarchy, roadmap Phase 1b, FAQ, utility, founder/intro mentions, and closing link.
- · Recorded v2 rules accurately: 10 slots (#1–5 50% / #6–10 30%), ~USD 10–100 protected via frozen ETH thresholds, 72h / −30% / hold ≥50%, Agreement v2, Swap auto-tx happy path, manual payout, no Solidity Shield, no automatic ETH transfer, ~USD 400 campaign-total liability framing (not per participant).
- · Clarified that public Analytics / Most Searched remain PLANNED; Scan Public Beta status unchanged. No Tokenomics / Treasury / Liquidity / Legacy rule changes.
- v2.1July 2026
- · Aligned litepaper with shipped Public Beta: HANSOME Scan at /scan is PUBLIC BETA (not “IN DEVELOPMENT / not available”). Documented Overall vs Structural, HANSOME Level, Analysis Coverage, Overall bands, Liquidity V2–V4, Supply & Burn, Creator / Holders / Contract Risk, Fast→Deep progressive enrichment, EN/ZH, and honest limitations.
- · Updated brand hierarchy, roadmap Phase 1, utility, FAQ, long-term vision, and closing links. Kept Explore / Analytics / Most Searched / Just Launched as PLANNED. Added PUBLIC BETA status label.
- · Preserved Tokenomics / Treasury / Liquidity / Legacy facts; no scoring-formula changes in this document revision.
- v2.0July 2026
- · HANSOME 2.0 rewrite: meme identity core (“Too Hansome to Be Useful” / “…So we built something useful anyway”), brand hierarchy with status labels, Scan & Score, axes + Confidence separations, Explore (PLANNED), $HANSOME utility, phased roadmap with Conditional Launch, Legacy section for Genesis + GameFi + mint flywheel.
- · Added Uniswap Liquidity & Lock Intelligence under Scan & Score: visibility-gap framing, capabilities, explicit lock statuses, Score relationship (size ≠ lock ≠ ownership/withdrawal ≠ range), Titan #47299 note, roadmap + FAQ.
- · Revenue strategy reframed around ecosystem tools; Documents relabel GameFi economic model as Legacy; FAQ Score disclaimers; closing disclaimer strengthened.
- · Preserved verified Tokenomics / Treasury / Liquidity facts (1B supply, 0% tax, non-mintable, Robinhood, 90/5/5, wallets, Uniswap v4, Titan #47299 unlock ~2027-07-15, /transparency for live balances). Fixed stale “single position” FAQ language.
- v1.7.1July 2026
- · Expanded the GameFi Economic Model report with a long-term sustainability section (P2E comparison, fixed supply, treasury-gated emission, player–ecosystem alignment, Alpaca/Cougar two-sided economy).
- v1.7July 2026
- · Added a GameFi Economic Model section with links to the bilingual mathematical analysis report and PDFs (emission bands, pool splits, sustainability, two-sided value).
- v1.6July 2026
- · Added a Gameplay Overview section with an Alpacas vs Cougars illustration and a CTA to the Game page for full mechanics.
- · Added a Building a Sustainable Ecosystem section describing mint-revenue reinvestment and the ecosystem growth flywheel.
- v1.5July 2026
- · Completed a Treasury-led liquidity optimization on the official Uniswap v4 pool: added two new Treasury-owned positions — a narrow-range position for lower swap slippage and a wide-range position for additional downside protection — while leaving the original 365-day locked position (#47299) completely unchanged.
- · Updated the Liquidity Policy section to reflect that the barbell liquidity strategy, previously described as planned, is now live across three Treasury-linked positions.
- · Added notes on the improved trading experience following the optimization: reduced swap slippage, more efficient execution for medium and larger trades, and better market depth.
- · Added notes on recent infrastructure improvements: swap infrastructure, gas-fee handling on Robinhood Chain, transaction reliability, and internal liquidity management tooling.
- · Expanded the Community section to reflect AMA sessions, KOL collaborations, and ongoing marketing campaigns alongside existing meme contests, giveaways, and community events.
- · Expanded the Transparency pillar in Core Philosophy to explicitly note that all liquidity operations are performed on-chain and are publicly verifiable, and that the project prioritizes long-term sustainability over short-term hype.
- v1.4July 2026
- · Officially listed on GeckoTerminal.
- · Officially listed on DexScreener.
- · Submitted a CoinGecko listing application (pending review).
- · Submitted a CoinMarketCap listing application (pending review).
- · Officially locked the Uniswap v4 LP position (#47299) for 365 days via Titan Locker, unlocking July 2027 — a concrete, on-chain demonstration of long-term commitment to liquidity.
- · Updated the Roadmap's liquidity plans: rather than committing to a fixed second position, liquidity depth is now monitored on an ongoing basis, with more added only if trading volume and community growth genuinely call for it.
- · Updated the Roadmap to reflect current milestones.
- · Updated the Community section to reflect the active Telegram community, regular meme contests, giveaways, and ongoing community events.
- · Minor wording improvements and documentation updates throughout the litepaper.
- v1.3July 2026
- · Clarified Tokenomics and Treasury Policy: the 90% Treasury figure is the initial allocation at launch, not a live balance. Added explicit language that Treasury tokens are expected to move into official liquidity over time, and that a decreasing Treasury balance means tokens were converted into a public liquidity position, not sold.
- · Removed hardcoded current-balance language from the Litepaper; every wallet section now points to /transparency as the live source of truth instead of stating a number here.
- · Added a FAQ entry: "Why is the Treasury balance lower than the stated 90%?"
- · /transparency itself now reads each official wallet's current HANSOME balance live from the contract, shown alongside its initial allocation.
- v1.2July 2026
- · Realigned the Founder Letter, Introduction, Vision, Core Philosophy, Revenue Strategy, Roadmap, Community, and Long-Term Vision sections with the project's actual direction: HANSOME starts as a meme coin, but the token is meant to be the beginning of a real alpaca brand — content, community events, meme contests, merch, and partnerships if the community keeps growing — not the end of the story.
- · Added a "The Token Is the Start" pillar to Core Philosophy and new FAQ entries covering merch, community events, partnerships, and what HANSOME actually does today.
- v1.1July 2026
- · Added bilingual support (English / Traditional Chinese) with a single shared page and language switch.
- · Added the Founder Letter, Changelog, and Language & Translations sections.
- · Added downloadable PDF export in both languages.
- v1.0July 2026
- · Initial publication: Introduction, Vision, Core Philosophy, Tokenomics, Treasury Policy, Liquidity Policy, Revenue Strategy, Roadmap, Community, Long-Term Vision, and FAQ.
19
Language & Translations
This document is available in English and Chinese. The Chinese version is written by hand to read naturally, not run through machine translation — if you spot a place where the meaning drifts between the two versions, treat the English version as the reference and let us know. Additional languages may be added later; the structure of this document is built so that doing so doesn't require rebuilding the page.
This document reflects HANSOME ALPACAS as of publication and will be revised as statuses change. It is not financial advice. HANSOME Score / Scan (Public Beta) are informational heuristics — not investment recommendations, popularity ranks, or guarantees of safety. 3-Day Limited ETH Shield is a promotional trial — not insurance, not a funded product claim, and not an automatic on-chain payout. Crypto is volatile. DYOR. Status labels in this litepaper (LIVE, PUBLIC BETA, IN DEVELOPMENT, PLANNED, CONDITIONAL, LEGACY) override marketing shorthand.