fa
Feedback

فریب کلاهبرداران را نخورید! تل‌متریو این کانال‌ها را شناسایی و برچسب‌گذاری می‌کند 👉 برای مشاهده برچسب، اشتراک تهیه کنید

HONO Protocol Updates

HONO Protocol Updates

رفتن به کانال در Telegram

Welcome to the official HONO Protocol channel! 🚀 Powering liquidity for community projects and growing ecosystems on Web3. Stay tuned for updates and opportunities. Farm🦉 today at @HootizenBot!

نمایش بیشتر
2 683
مشترکین
-1624 ساعت
-347 روز
-3630 روز

در حال بارگذاری داده‌ها

ابر برچسب‌ها
هیچ داده‌ای
مشکلی وجود دارد؟ لطفاً صفحه را تازه کنید یا با مدیر پشتیبانی ما تماس بگیرید.
اشارات ورودی و خروجی
---
---
---
---
---
---
جذب مشترکین
اکتبر '26
اکتبر '26
+4
در 0 کانال‌ها
سپتامبر '260
در 0 کانال‌ها
Get PRO
اوت '260
در 0 کانال‌ها
Get PRO
ژوئیه '260
در 0 کانال‌ها
Get PRO
ژوئن '260
در 0 کانال‌ها
Get PRO
مه '260
در 0 کانال‌ها
Get PRO
آوریل '260
در 0 کانال‌ها
Get PRO
مارس '260
در 0 کانال‌ها
Get PRO
فوریه '260
در 0 کانال‌ها
Get PRO
ژانویه '260
در 0 کانال‌ها
Get PRO
دسامبر '250
در 0 کانال‌ها
Get PRO
نوامبر '250
در 3 کانال‌ها
Get PRO
اکتبر '250
در 0 کانال‌ها
Get PRO
سپتامبر '250
در 0 کانال‌ها
Get PRO
اوت '25
+1
در 0 کانال‌ها
Get PRO
ژوئیه '250
در 0 کانال‌ها
Get PRO
ژوئن '25
+9
در 0 کانال‌ها
Get PRO
مه '25
+1
در 0 کانال‌ها
Get PRO
آوریل '25
+4
در 0 کانال‌ها
Get PRO
مارس '25
+37
در 0 کانال‌ها
Get PRO
فوریه '25
+5
در 0 کانال‌ها
Get PRO
ژانویه '250
در 0 کانال‌ها
Get PRO
دسامبر '240
در 0 کانال‌ها
Get PRO
نوامبر '240
در 0 کانال‌ها
Get PRO
اکتبر '24
+2
در 0 کانال‌ها
Get PRO
سپتامبر '24
+3
در 0 کانال‌ها
Get PRO
اوت '24
+9
در 0 کانال‌ها
Get PRO
ژوئیه '24
+5
در 0 کانال‌ها
Get PRO
ژوئن '24
+6
در 0 کانال‌ها
Get PRO
مه '24
+3
در 0 کانال‌ها
Get PRO
آوریل '24
+4
در 0 کانال‌ها
Get PRO
مارس '24
+4
در 0 کانال‌ها
Get PRO
فوریه '24
+2
در 0 کانال‌ها
Get PRO
ژانویه '24
+5
در 0 کانال‌ها
Get PRO
دسامبر '23
+7
در 0 کانال‌ها
Get PRO
نوامبر '23
+4
در 0 کانال‌ها
Get PRO
اکتبر '23
+4
در 1 کانال‌ها
Get PRO
سپتامبر '23
+7
در 0 کانال‌ها
Get PRO
اوت '23
+44
در 0 کانال‌ها
Get PRO
ژوئیه '23
+7
در 0 کانال‌ها
Get PRO
ژوئن '23
+6
در 0 کانال‌ها
Get PRO
مه '23
+5
در 0 کانال‌ها
Get PRO
آوریل '23
+2
در 0 کانال‌ها
Get PRO
مارس '23
+7
در 0 کانال‌ها
Get PRO
فوریه '23
+6
در 0 کانال‌ها
Get PRO
ژانویه '230
در 0 کانال‌ها
Get PRO
دسامبر '22
+3
در 0 کانال‌ها
Get PRO
نوامبر '22
+2
در 0 کانال‌ها
Get PRO
اکتبر '22
+3
در 0 کانال‌ها
Get PRO
سپتامبر '22
+3
در 0 کانال‌ها
Get PRO
اوت '22
+5
در 0 کانال‌ها
Get PRO
ژوئیه '22
+1
در 0 کانال‌ها
Get PRO
ژوئن '22
+5
در 0 کانال‌ها
Get PRO
مه '22
+11
در 0 کانال‌ها
Get PRO
آوریل '22
+6
در 0 کانال‌ها
Get PRO
مارس '22
+3
در 0 کانال‌ها
Get PRO
فوریه '220
در 0 کانال‌ها
Get PRO
ژانویه '22
+3
در 0 کانال‌ها
Get PRO
دسامبر '21
+34 453
در 0 کانال‌ها
Get PRO
نوامبر '21
+55
در 0 کانال‌ها
Get PRO
اکتبر '21
+42
در 0 کانال‌ها
Get PRO
سپتامبر '21
+7 364
در 0 کانال‌ها
Get PRO
اوت '21
+4 530
در 0 کانال‌ها
Get PRO
ژوئیه '21
+4 968
در 0 کانال‌ها
تاریخ
رشد مشترکین
اشارات
کانال‌ها
23 اکتبر0
22 اکتبر+1
21 اکتبر0
20 اکتبر0
19 اکتبر0
18 اکتبر0
17 اکتبر0
16 اکتبر0
15 اکتبر+2
14 اکتبر0
13 اکتبر0
12 اکتبر+1
پست‌های کانال
​​v3 gives every graduated token three venues: the bonding curve, the V4 AMM pool, and the order book. A short guide to what each is for. The bonding curve is for launch. A token does not start with a market; the curve manufactures one. Price discovery from the first buy, automatic liquidity, no creator capital required. Use it to launch, and to buy into tokens that have not graduated yet. The AMM pool is for casual size and passive liquidity. After graduation, the token trades on a Uniswap V4 pool paired with HONO. Anyone can swap at the pool price or add liquidity and earn fees. The tradeoff: price moves against you as you trade, so larger orders pay more slippage. Use it for convenience and for providing liquidity. The order book is for precision. A limit order executes at the price you name or not at all. Makers escrow funds into the contract and wait. Takers fill at the posted price. There is no slippage against a curve because there is no curve: you trade against a specific offer at a specific price. Partial fills let large orders work through the book in pieces. Two different tools. The AMM prices every trade against a formula. The order book lets you name your price and let the market come to you. On a CEX, the order book was the whole product and the venue held your funds. On v3, both venues exist side by side, the AMM is standard V4, and the order book is contract-escrowed.

2
​​Engineering check-in, same format as last time. Done since the last update: - The deployment scripts were rebuilt into a staged sequence and the run is underway on Sepolia, stage by stage. The earliest stages are on-chain already: the lock pool is deployed and upgraded, and HONO is running its v3 implementation. Running the sequence is surfacing the problems we built it to catch: ordering issues where later stages consume earlier outputs, and inconsistent contract-address naming across scripts. Both get fixed as they come up. - The peg keeper is implemented: fee and profit calculation, plus an arbitrage bot that runs through a V4 flash loan. - The hUSDC base layer and the airdrop streamer are implemented. - A first round of vulnerability fixes landed, and a second hardening pass across the backing engine, fee collection, vesting, and token creation contracts is in the working tree now. - Frontend integration is moving: the hUSDC and airdrop pages are being wired to the new contracts, and dead v2 bindings are being removed. Still in progress: the independent review of the new contracts, the hUSDC vault selection, the remaining stages of the testnet deployment run, validation against the Glamsterdam upgrade's new gas model, and the rest of the frontend wiring. Same rule as before: no date until the review, the vault selection, the testnet run, and the Glamsterdam validation all clear. When the last item is done, the go-live post follows.
13
3
​​Ethereum's next major upgrade, Glamsterdam, is close. It activated on Sepolia on October 6 and reaches the Hoodi testnet on October 26, with mainnet activation expected to follow in the coming weeks. It is one of the reasons the launch timeline moved, and it explains a bet v3 made from the start. What the upgrade does. Two headline changes. First, enshrined proposer-builder separation: today the handoff between block proposers and block builders runs through trusted third-party relays outside the protocol. Glamsterdam moves that exchange into the protocol itself, removing the need to trust relays for it. Second, block-level access lists: every block records the accounts and storage it touched, which lets nodes read state and validate transactions in parallel instead of strictly in sequence. What it does to gas. Parallel validation is what makes higher gas limits safe. Ethereum's block capacity has been rising through 2026 and Glamsterdam is designed to sustain it: more block space per block means less fee pressure at the same demand. The upgrade also reprices some operations upward to reflect what they actually cost the network, so the honest claim is more capacity, not cheaper gas. Why it matters for v3. L1 has always had the deepest liquidity and the strongest security. What it lacked was cheap enough block space for high-frequency designs, and a fully on-chain order book is the most gas-sensitive design there is: every offer, fill, and cancel is a transaction. Cost is the reason applications left L1 for faster chains and L2s. Glamsterdam directly attacks that reason, and we expect applications to start returning to L1 as capacity rises. v3 is built to already be there. Why it moved the timeline. Glamsterdam reprices gas, including deployment and state-creation costs, and it changes how blocks are produced and validated. Shipping a new protocol right before a hard fork that changes its cost model means re-validating after the fork anyway. We are validating the deployment against the post-upgrade gas model as part of the remaining checklist, so the contracts launch tuned for the network they will actually run on. Same story the earlier posts told, at the protocol layer: the post-CEX market needs on-chain venues, and on-chain venues need an L1 with the capacity to run them.
16
4
​​A question inside the hUSDC design worth answering directly: when depositors earn yield, who pays it? The answer is ERC-4626 vaults. When you deposit USDC into the PSM, the USDC does not sit idle. It goes into yield-earning ERC-4626 vaults, and the vault return belongs to the depositors who supplied the USDC. ERC-4626 is the tokenized vault standard. It defines a fixed interface for deposits, withdrawals, and share accounting. Any contract that understands the standard can interact with any compliant vault, and the same accounting rules apply everywhere. That is why the deposits stay composable instead of locked into a proprietary wrapper. Depositors earn from two sources. First, the yield the underlying vault generates on the deposited USDC. Second, a share of hUSDC/USDC DualPool swap fees, which grow with trading volume through the pool. What we have not finalized is vault selection. Which ERC-4626 vaults hold the deposits is an engineering decision still in progress, and it is one of the remaining items before launch. The yield source is part of the security model, not a detail to hand-wave, so we are not announcing a vault before the selection is done. We will publish it with the deployment. The structure: USDC in, yield vault, hUSDC out, DualPool fees on top. The depositor return comes from yield sources denominated in dollars.
19
5
​​A closer look at a piece of v3 we have referenced but not walked through: the DualPool. The DualPool is the hUSDC/USDC pool on Uniswap V4. It is where hUSDC trades against the USDC that backs it. Why it exists. hUSDC is a USDC derivative: minted 1:1 against USDC deposits in the PSM, value based on USDC. For hUSDC to function as the protocol's liquidity layer, it needs a deep, tradeable market against USDC. The DualPool is that market. The price targets approximately $1.00, held by arbitrage rather than a guarantee. Three layers work together: 1. External arbitrage. If hUSDC trades below USDC on the DualPool, arbitrageurs buy hUSDC cheap and exchange it 1:1 for USDC at the PSM. If it trades above, they mint hUSDC at the PSM and sell into the pool. The price deviation is the profit opportunity. 2. The DualPool hook's own arbitrage. The hook runs arbitrage logic inside the pool and captures deviations before external bots need to. The pool self-corrects at the contract level. 3. The PSM as backstop. The PSM exchanges hUSDC and USDC at 1:1. As long as the PSM holds USDC, that conversion anchors the price range. It is an economic equilibrium, not a promise. The distinction matters: a guarantee depends on an issuer staying solvent and honoring it. An equilibrium depends on incentives, and incentives keep working as long as the arbitrage is profitable. DualPool swap fees flow back to hUSDC depositors on top of vault yield. More volume through the pool, more fees, better depositor return.
25
6
​​Another piece of v3 that has not gotten a post yet: the contest system. Every token that graduates from the bonding curve gets a trading contest that runs forever, in weekly epochs. Here is how it works. During each 7-day epoch, the contracts track buy-side volume on that token, denominated in HONO. Buys on the Uniswap V4 pool count. Buys on the order book count. Both venues feed the same leaderboard. Meanwhile, the fees that token generates accumulate: LP fees on the V4 pool plus order book fees. When the epoch ends, the creator's fee share is paid out first, and the rest becomes the epoch's prize pot, denominated in HONO. To qualify for a share of the pot, your buy volume for that epoch has to clear a threshold (170 HONO, dust trades under 1 HONO do not count). Everyone who qualified splits the pot pro-rata to their volume. If nobody qualifies, the pot rolls into the next epoch. One detail worth knowing: the first person to claim in an epoch earns a 1% bounty carved from the pot, and their claim is what triggers fee collection and finalization for the next epoch. There is no team-run cron job. The keeper work is done by whoever claims first, paid for by the bounty. The system runs itself. This is a demand-side incentive. Protocol fee revenue goes back to the people buying the token, every week, in HONO. On boom.lol, fees left the system. On v3, part of them come back as prizes for the traders who generated the volume.
32
7
​​A feature we have not covered yet: staking xHONO lowers your trading fees across the protocol. The base taker fee is 1.00%. Your discount depends on how much xHONO you have staked, read directly from the staking contract at the moment of the trade: - 50 xHONO: 10% off, you pay 0.90% - 200 xHONO: 20% off, you pay 0.80% - 1,000 xHONO: 35% off, you pay 0.65% - 5,000 xHONO: 55% off, you pay 0.45% - 20,000 xHONO: 70% off, you pay 0.30% - 50,000 xHONO: 85% off, you pay 0.15% - 100,000 xHONO: Protocol Ally, you pay 0.00% Below Protocol Ally, the fee floor is 0.10%. The discount applies in two places. On the order book, the contract checks your tier before every fill. On our Uniswap V4 pools, the hook adjusts the pool's LP fee to your tier in real time when you swap through the router. Same stake, lower cost, on both venues. The second part is something V4 hooks make possible that was not possible before: a pool that charges different fees to different swappers, computed per swap. High-tier stakers get tighter effective spreads on the AMM, not just on the order book. For active traders the math compounds. Lower fees mean more aggressive orders fit inside the same budget, which means better placement on the book and better fill economics. Staking is not just voting and rewards anymore. It is a trading advantage.
30
8
​​Status update from the engineering side. The contracts are written and compiling. The test suite is running with fuzz testing at 10,000 runs. The frontend is wired to the new contracts and we are fixing the remaining integration issues. The order book is implemented and tested. The MCP server is in development. The bot trading system is in development. What is left before we go live: completing the independent review of the new contracts, finalizing the hUSDC vault selection, and running the full deployment script on a test network end to end. We are not giving a date until those things are done. If the review or the testnet deployment surfaces issues, we fix them before we ship. No rush to launch with broken code. We will post the go-live date the moment engineering confirms the deployment is ready.
31
9
​​Tying the agentic trading pillar together. AI is the dominant narrative of 2026. Every protocol is talking about it. Most are not built for it. Most DeFi protocols are built for humans: a browser, a wallet extension, a connect button, a form, a submit. That works when a human is making every decision. It does not work when an AI agent is making a thousand decisions per minute. HONO Protocol is built for both. The order book is composable: other contracts can call it directly. The subgraph exposes a clean GraphQL API for reading market state. The MCP server lets any LLM agent read markets and build transactions. The bot trading system lets users author strategies that execute deterministically. MetaMask Agent Wallet handles signing with built-in threat scanning, MEV protection, and potentially gasless relay. This is not a bolt-on AI feature. It is infrastructure designed from the start to be traded by agents and bots, not just humans. The order book's escrow model, the subgraph's event design, the MCP server's read-only architecture, the bot system's JSON strategy format: every piece was designed with programmatic trading in mind. The protocols that capture AI-driven volume are the ones built for it. HONO Protocol is built for it.
33
10
​​More on the bot trading system. Two advanced features that go beyond passive market making. Active fill strategies. The standard market making bot only posts orders and waits for someone to fill them. Active fill strategies let the bot take liquidity: fill opposing offers on the order book to capture arbitrage, rebalance inventory, or tighten effective spreads. Three active fill modes. Arbitrage: if the bot's oracle price differs from an existing offer, fill it for instant profit. Inventory rebalance: if inventory drifts, fill an opposing offer to correct it immediately instead of waiting for someone to fill your skewed quotes. Cross-offer arbitrage: if a sell offer is priced below the bot's buy offer, fill the sell offer and capture the spread. Formula-driven offer bots. For users who need more than the fixed-spread model, the bot supports user-supplied mathematical formulas for price and size. The user writes expressions like "price = oracle (1 - 0.02 - level0.005)" and "size = max(10, 100 / (1 + vol))", and the bot evaluates them each cycle against live on-chain state. This lets users express non-linear spreads, volatility-scaled sizing, time-decaying quotes, and any other pricing logic that a fixed spread cannot capture. The formulas run in a sandboxed expression language. Everything else (reconcile, risk guard, scheduling, logging) is reused from the standard bot. Designated filler bots. A bot that only fills offers created by a specified maker address. Useful for creators who want to create liquidity for their own token's market, or for protocol-level designated market makers. These are the tools that let sophisticated users and protocols run professional-grade market making on HONO Protocol. This is what deep, efficient on-chain markets require.
30
11
​​The second piece of agentic trading: the bot trading system. The bot trading system is a user-driven platform for running trading strategies on the order book. Users design strategies in a web UI, the bot runs them on a schedule, and the strategies execute deterministically. The key design decision: strategy is data, not code. A strategy is a typed, versioned JSON document. The user authors it. The executor interprets it. This makes strategies auditable, versionable, and safe to run server-side. There is no arbitrary code execution. Three modes. Flat market making: post bids and asks at a fixed spread from mid. Inventory-skewed quoting: shift prices based on inventory, using the Avellaneda-Stoikov model. Pegged quoting: track an external price source. Every bot cycle runs through an unbypassable risk guard. The risk guard checks daily loss limits, token risk tiers, gas prices, and position limits. Strategy parameters can tighten risk but never loosen the hard limits. The risk guard runs inside the executor, after the strategy interpreter and before the on-chain calls. AI is available as an optional configuration assistant. It can suggest parameter tweaks. The user approves or rejects. AI never touches the executor path. Removing AI breaks nothing in the trading loop. This is not AI making trading decisions. This is users authoring strategies, a deterministic executor running them, and an optional AI assistant suggesting tweaks. The user is always in control.
28
12
​​Pillar three: agentic trading rails. Today, the MCP server. MCP stands for Model Context Protocol. It is a standard that lets AI agents interact with external tools. We built an MCP server that lets any LLM agent, Claude, Devin, Cursor, or any other, read HONO Protocol market state and build transactions. Here is how it works. The agent runs on the user's machine. It calls our MCP server to read order book state, check prices, and build unsigned transactions. It calls MetaMask Agent Wallet to sign and broadcast those transactions. Our server never sees private keys. It never broadcasts. It reads state, computes strategy, and hands off unsigned transactions to the signing layer. This means an AI agent can do something like: read the order book, find an arbitrage opportunity between the bonding curve and the order book, build the calldata for both transactions, and hand them to MetaMask to sign and send. All without a human clicking buttons. The agent orchestrates. The protocol provides the interface. The wallet signs. Three separate processes, clean separation of concerns. This is what it means to be built for AI agents. Most DeFi protocols are built for humans in a browser. The protocols that expose clean programmatic interfaces are the ones that capture AI-driven volume.
28
13
​​Tying it together: what hUSDC means for HONO, and the full picture of the liquidity loan. HONO's intrinsic value is backed by what is in the vault. In v3, that backing is hUSDC. Every hUSDC in the vault is backing for HONO. hUSDC is a USDC derivative backed by USDC in yield vaults. So HONO is backed by a yield-earning dollar asset, not just protocol fees. The backing is concrete and grows over time as the vault earns. Now the liquidity loan, in full. A creator who wants to skip the bonding curve locks xHONO. The protocol mints hUSDC, converts it to HONO via the vault, and pairs the HONO with the creator's token on Uniswap V4. The pool is live from the first block. The minted hUSDC never reaches an end user. It flows from the PSM mint, into the HONO vault, into the LP. It stays inside the protocol. No leak, no dump risk. It is a loan, not a gift. The liquidity is protocol-owned and can be reclaimed if the token is abandoned. Backers get their xHONO back on wind-down. Swap fees on the HONO/NewToken pool split three ways: the protocol (with a decaying share as the token grows), the xHONO backers, and the token creator. The decaying protocol share gives the creator a reason to keep promoting. xHONO holders can crowdfund a token's liquidity loan. A creator proposes a pool, xHONO holders contribute toward the required lock, and everyone shares in the fee revenue. The flywheel: USDC gets deposited into the PSM. hUSDC gets minted. The USDC earns yield for depositors. The hUSDC backs HONO. HONO pairs with every new token on V4 and the order book. More tokens launching and trading means more HONO pairs, more volume through the hUSDC/USDC DualPool, more vault yield, stronger HONO backing. The loop runs. This is what makes HonoProtocol DeFi infrastructure. The order book provides limit-order trading. The launchpad brings tokens and volume. The USDC derivative layer provides the liquidity and backing the ecosystem builds on. HONO is the token at the center. xHONO governs, earns, and bootstraps liquidity. hUSDC is the credit layer underneath. USDC is what comes in at the start. None of this replaces HONO or xHONO. It is the infrastructure they sit on.
39
14
​​The infrastructure layer underneath HONO is called hUSDC. It is a USDC derivative. Here is what that means. You deposit USDC. The protocol mints hUSDC to you 1:1. Your USDC goes into yield-earning ERC-4626 vaults. The hUSDC you receive represents your deposit, and it is used across the protocol: it backs HONO, it denominates token launches, it provides liquidity for the hUSDC/USDC pool. hUSDC is a USDC derivative because its value is based on USDC. Every hUSDC is backed 1:1 by USDC sitting in yield-earning vaults. The USDC earns yield for the depositors who lent it. The hUSDC circulates as the liquidity layer of the protocol. The price stays near $1.00 through arbitrage, not through a guarantee. Three layers: external arbitrage between the PSM and the DualPool, the DualPool hook's own arbitrage, and the PSM as a 1:1 backstop. It is an economic equilibrium, not a promise. This is what makes HonoProtocol DeFi infrastructure. The launchpad brings tokens and volume. The order book provides limit-order trading. The USDC derivative layer provides the liquidity and backing that the ecosystem builds on.
38
15
​​We mentioned a second path to launch, where a creator locks xHONO to get a live HONO/NewToken pool from the first block. That is the new use for xHONO. Here is what we can say now, before the full hUSDC reveal. A creator who wants to skip the bonding curve locks xHONO. The protocol uses that lock to bootstrap a HONO/NewToken pool on Uniswap V4. The pool is live from block one. The creator gets an immediate market. xHONO holders can also crowdfund a token's launch by contributing to the lock. The mechanism creates new demand for xHONO from outside the existing holder base. Every token that launches via this path locks xHONO. More launches means more locked xHONO. The full details, including what gets minted, how the pool is funded, and how fees split, depend on the USDC derivative layer we have not introduced yet. That comes tomorrow. Once you see what sits underneath HONO, the liquidity loan mechanism makes sense as part of the picture. For now: xHONO still stakes, votes, and earns. It also bootstraps liquidity for new tokens. More utility, not less.
35
16
​​xHONO is the staking and governance token. Nothing about that changes in v3. You stake HONO, you get xHONO. You vote with xHONO across two pools: the Mint pool, which funds staking rewards, and the DAO pool, which sends wstETH to the DAO address. You earn wstETH rewards streamed over time, claimed as HONO. All of that is intact. The staking contract is the same model, upgraded for v3. Existing stakes and votes carry over. The rewards stream kept running. What is new is a second use for xHONO. It does not replace staking or voting. It sits alongside them, and it creates new demand for xHONO from outside the existing holder base. We will cover the details when we introduce hUSDC. For now: if you hold xHONO, your position is exactly where you left it. Staking, voting, and rewards are all intact, and something new is coming.
38
17
​​Back to the token most of you hold. What HONO does in v3. HONO is the token at the center of every launch. When a token launches on the bonding curve, buyers use HONO to buy in. When it graduates, the HONO from the curve becomes the initial liquidity for the Uniswap V4 pool. Every new token on HonoProtocol is paired with HONO. HONO is also the trading pair on the order book. Tokens listed on the order book trade against HONO. The order book, the bonding curve, and the V4 pools all use HONO as the settlement asset. What backs HONO is the next piece of the story. There is a USDC derivative layer underneath HONO that we will introduce in two days. For now, the point is simple: HONO is not being replaced. It is not legacy. It is the token the protocol is built around, and it is the token every part of the system uses. If you hold HONO, you hold the token that the entire ecosystem runs on.
39
18
​​To close out the launchpad section, here is what we learned from running boom.lol and what changed in v3. The bonding curve, graduation, and liquidity management now run inside a single Uniswap V4 hook instead of across multiple separate contracts. On boom.lol, each piece was a separate contract with its own routing. Fewer moving parts means fewer failure points and lower integration overhead. The graduation threshold is denominated in HONO, which means a token has to attract real buying pressure before it gets an open market pool. Boom.lol used a market cap threshold in ETH. The HONO threshold ties graduation to the protocol's own token, which aligns incentives. The bonding curve uses a constant-product AMM model with a virtual HONO reserve baked in at pool creation. This gives every token a fair starting price without requiring the creator to front capital. The 1% trading fee on the bonding curve is the same as boom.lol. The graduation fee is 2%. Both are on-chain and transparent. The second launch path, the liquidity loan, is new. Boom.lol only had the bonding curve. We learned that some creators do not need price discovery because they already have a community. They need a live market from block one. And the on-chain order book is entirely new. Boom.lol graduated tokens to a Uniswap pool and that was it. V3 graduates tokens to a V4 pool and they can also be listed on the order book for limit order trading. This is the limit-order trading experience that the post-CEX market needs.
46
19
​​We mentioned a second path to launch. Here is the high-level picture. Full details come with the hUSDC announcement. Path one: the bonding curve. A token launches, trades on the curve against HONO, and graduates to a Uniswap V4 pool when it hits the threshold. This is the community-driven path. Price discovery happens on the curve. Open to anyone. Path two: a creator who already has a community can get a live HONO/NewToken pool on Uniswap V4 from the first block, without running the bonding curve. This path requires locking xHONO. The protocol handles the rest. Both paths end at the same place: a HONO/NewToken pool on Uniswap V4. The difference is how you get there, and who the path is for. The bonding curve is for tokens that need price discovery and community accumulation. The second path is for creators who already have both and want to skip straight to a live market. This is something boom.lol did not have. It is one of the things we learned was missing.
45
20
​​More on graduation, since it is the moment a token becomes a real market asset. When a token on the bonding curve hits the graduation threshold, the curve's liquidity converts into a Uniswap V4 pool. The token and the HONO that were on the curve become the initial LP. From that block on, the token trades on the open AMM with standard V4 mechanics. A few things happen at graduation that matter. The HONO that was collected on the bonding curve backs the new pool. The token gets a real, tradeable market, not a thin book. The creator's fee, if they set one, continues to route to them on the AMM, same as on the curve. The graduation threshold is set in HONO, not in token supply. A token has to attract real HONO buying pressure to graduate. It filters out tokens that cannot generate demand before they hit the open market. After graduation, the token is a standard V4 asset. It can be traded, pooled, routed through aggregators, and listed on the on-chain order book. On boom.lol, graduation meant seeding a Uniswap pool and burning the LP. On v3, graduation means converting the bonding curve liquidity into a V4 pool managed by the hook. Same concept, better mechanics.
48