[RFC-05] List hMON (Holistic MON) as Neverland Collateral
Summary
Fastlane is preparing to launch hMON as part of the upcoming shMonad upgrade. This RFC asks Neverland to list hMON as a new reserve asset, with both collateral and borrowing enabled once the Chainlink oracle path is live and shMonad is upgraded.
hMON tokenizes the existing shMonad Degen Pool. Users deposit MON into the zero-yield tranche and receive hMON 1:1. That MON is still staked through shMonad, but the staking rewards are not paid to the hMON holder. Instead, those rewards are donated into the pooled shMON exchange rate.
The easiest way to think about hMON is that it is MON principal exposure with a different exit path than wMON. hMON does not unwrap directly to MON. A holder can sell hMON directly where liquidity exists, or convert hMON into shMON at the current shMON deposit rate and then exit through immediate liquidity routes such as the shMonad atomic pool or secondary markets.
For pricing, the proposed Chainlink path is:
hMON/USD = hMON->shMON conversion rate x shMON/USD
This avoids depending on shallow hMON spot liquidity at launch. The oracle can read shMonad’s on-chain conversion quote and compose it with the existing shMON/USD oracle path.
The initial listing should match Neverland’s shMON LTV, liquidation threshold, and liquidation bonus.
Motivation
The Degen Pool already exists in shMonad today, but it is not liquid. Users deposit MON, receive no token back, and donate the staking yield to shMON holders.
The upgrade changes that by tokenizing the position as hMON. That makes the zero-yield tranche transferable and usable in DeFi without changing the underlying economics. hMON holders keep the MON principal exposure. shMON holders continue to receive the donated yield.
Listing hMON on Neverland would give the asset an immediate productive use case:
- hMON holders can borrow against their position without first converting into shMON.
- Users can borrow hMON directly when they want zero-yield tranche exposure.
- Neverland gets a Monad-native collateral asset with a clean on-chain pricing route.
- More hMON utility can make the zero-yield tranche more useful, which supports the shMON yield profile.
There is also a points angle, but it should stay separate from Neverland risk decisions. Fastlane points rules live on the shMonad points page, and 10x exposure only applies when hMON is deployed into qualifying DeFi integrations. Neverland does not need to enforce those rules, but a Neverland listing would be one of the more important venues for hMON utility.
Protocol and Collateral Details
hMON is the tokenized form of shMonad’s zero-yield tranche, also known as the Degen Pool.
When a user deposits MON into the zero-yield tranche:
- The user receives hMON 1:1 against the deposited MON.
- The MON enters shMonad’s normal staking flow.
- Staking rewards from that MON are not credited to the hMON holder.
- Those rewards accrue to pooled shMON equity.
- The hMON holder can later convert hMON into shMON at the current deposit exchange rate.
Core token properties:
| Property | hMON |
|---|---|
| Name | Holistic MON |
| Symbol | hMON |
| Decimals | 18 |
| Standard | ERC-20 plus EIP-2612 permit |
| Balance behavior | Non-rebasing |
| Mint path | Deposit MON into the zero-yield tranche |
| Conversion path | Burn hMON / zero-yield balance and mint shMON |
| Direct MON redemption | No direct hMON-to-MON path |
The main hMON functions are:
interface IShMonadZeroYield {
function depositToZeroYieldTranche(uint256 assets, address receiver)
external
payable;
function convertZeroYieldTrancheToShares(uint256 assets, address receiver)
external
returns (uint256 shares);
function previewDeposit(uint256 assets)
external
view
returns (uint256 shares);
function getZeroYieldToken()
external
view
returns (address token);
}
Liquidators will have two practical exit routes:
- Sell seized hMON directly into hMON liquidity where available.
- Convert hMON into shMON through shMonad, then exit shMON through the atomic pool or existing DEX liquidity.
Atomic unstaking is instant when liquidity is available, but it charges a utilization-based fee. For Neverland risk purposes, the relevant liquidation routes are the immediate routes only: direct hMON liquidity, shMonad atomic liquidity, and external shMON DEX liquidity.
Launch Liquidity and Initial hMON Float
The shMonad upgrade tokenizes the current zero-yield Degen Pool into hMON. As of the June 15, 2026 on-chain snapshot at block 81,486,630, roughly 20.8MM hMON will become available once the upgrade is live.
There is also existing instant liquidity for the shMON leg after conversion. The same snapshot shows roughly 1.3MM MON available in the shMonad atomic unstaking pool.
Current shMON pool liquidity across Uniswap, PancakeSwap, Balancer, and Curve totals approximately $774k. This is aggregate pool TVL, not guaranteed liquidation capacity at a fixed slippage. It is still relevant because liquidators have more than one immediate route after converting seized hMON into shMON.
Fastlane also plans to incentivize two direct hMON liquidity pools with PancakeSwap and Balancer. Once those pools are live, liquidators can choose between selling hMON directly or converting hMON into shMON and using the existing shMON liquidity stack. That gives the market two liquidation paths instead of relying only on the hMON → shMON conversion route.
Oracle Path
The proposed Chainlink oracle composes two pieces:
- The hMON-to-shMON conversion quote from shMonad.
- The Chainlink shMON/USD feed.
Because 1 hMON represents 1 MON in the zero-yield tranche, the hMON-to-shMON leg can be quoted with:
uint256 shmonOut = IShMonad(shMonad).previewDeposit(1e18);
Then:
hMON/USD = shmonOut / 1e18 x shMON/USD
The state-changing conversion function, convertZeroYieldTrancheToShares(uint256 assets, address receiver), uses the same deposit-rate math. The oracle should read the view quote and should not use hMON DEX spot pricing as the primary source.
Recommended oracle controls:
| Control | Recommendation |
|---|---|
| Primary price path | Chainlink composed hMON->shMON x shMON/USD |
| hMON->shMON leg | shMonad previewDeposit(1e18) |
| USD leg | Chainlink shMON/USD |
| Staleness checks | Required on Chainlink feed updates |
| Sanity bounds | Required against expected MON/shMON behavior |
| DEX spot dependency | Not required for primary pricing |
| Launch gate | Listing should wait until the Chainlink path is live and reviewed |
This is the cleanest path for launch because it prices hMON from protocol conversion math and the existing shMON oracle, rather than from early hMON market depth.
Risk and Safety Considerations
hMON is simple economically, but it is still a new collateral asset. The main risks Neverland should underwrite are:
- shMonad and hMON smart contract risk.
- Oracle risk across both the shMonad conversion quote and the shMON/USD feed.
- Liquidity risk if liquidators need to sell hMON directly, or convert hMON into shMON and then exit during stressed conditions.
- Closed-mode risk: if shMonad is closed, hMON transfers, approvals, and permits remain live, but new hMON minting and hMON-to-shMON conversion are blocked.
- MON market risk, since hMON ultimately represents MON-denominated principal.
- Points-policy risk, since points treatment is external to Neverland and should not be counted as collateral value.
Those risks are why this RFC proposes capped supply, capped borrowing, isolation at launch, and collateral parameters that match shMON.
Proposed Collateral Parameters
hMON should launch as both collateral-enabled and borrow-enabled. Borrowing matters because some users will want hMON exposure without sourcing spot liquidity, and because a borrow market gives the asset more utility than a collateral-only listing.
Suggested initial parameters:
| Parameter | Proposed launch value |
|---|---|
| Collateral enabled | Yes |
| Borrowing enabled | Yes |
| LTV | 55% |
| Liquidation Threshold | 60% |
| Liquidation Bonus | 15% |
| Oracle | Chainlink composed hMON->shMON x shMON/USD |
| Supply Cap | 70MM shMON-equivalent, about 110MM hMON today |
| Borrow Cap | 5MM shMON-equivalent, about 8MM hMON today |
| Isolation Mode | Enabled at launch |
| E-Mode | Disabled at launch |
The 55% LTV and 60% liquidation threshold match shMON’s current Neverland collateral parameters. The difference is liquidation execution: seized hMON depends on direct hMON liquidity or the hMON → shMON → immediate exit route. The 15% liquidation bonus compensates liquidators for taking that additional route, liquidity, and execution risk during the early market.
The supply cap should match shMON’s current Neverland supply cap in shMON-equivalent terms, not raw token units. At the current hMON → shMON conversion rate, a 70MM shMON-equivalent cap is roughly 110MM hMON. The configured hMON unit cap should be calculated at listing using the live conversion rate. shMON is not borrow-enabled today, so hMON should launch with a separate borrow cap of 5MM shMON-equivalent, or roughly 8MM hMON at today’s rate. That gives the borrow market room to start while keeping utilization and liquidation risk contained until direct hMON liquidity is live and tested.
The supply cap can be raised later through governance after:
- The Chainlink oracle path has run in production.
- hMON supply distribution is easier to observe.
- Liquidators have tested direct hMON exits and the hMON → shMON → atomic MON / DEX exit path.
- Direct hMON liquidity and shMON liquidity are deep enough to support larger liquidations.
Fastlane views these as starting parameters. Neverland and its risk partners should make the final call based on current liquidity, volatility, liquidation capacity, oracle implementation, and protocol risk.
DUST Incentive Request
Fastlane is also asking Neverland to consider a DUST incentive allocation for hMON once the oracle is live and the market is enabled.
The goal is to seed the market, make hMON visible to Neverland users, support early borrow demand, and help establish liquidator familiarity with the asset.
Exact DUST sizing and duration should be decided by Neverland and veDUST governance. Fastlane can coordinate separate shMonad points messaging, but Fastlane points and Neverland DUST incentives should be treated as separate programs.
Conclusion
hMON gives the existing shMonad Degen Pool a liquid ERC-20 form. It is non-rebasing, represents MON principal in the zero-yield tranche, and converts into shMON at the current deposit exchange rate.
The requested Neverland listing is intentionally controlled: collateral enabled, borrowing enabled, capped supply, capped borrowing, isolation at launch, Chainlink-composed pricing, shMON-matched LTV and liquidation threshold, and a higher liquidation bonus for hMON-specific execution risk.
If the community is aligned on the oracle path and initial risk settings, this RFC can move toward a Neverland Governance Vote.
References
- shMonad analytics dashboard: ShMonalytics - ShMonad Analytics Dashboard
- shMonad deposit paths: Depositing MON | shMonad
- shMonad exchange-rate documentation: MON / shMON Exchange Rate | shMonad
- shMonad unstaking documentation: Atomic (Instant) Unstaking | shMonad
- shMonad points page: Points | SHMONAD
- Uniswap shMON / MON pool: https://dexscreener.com/monad/0x1f86a9f2441cac9b942cfb5445530cdbb28717ed
- PancakeSwap shMON / USDC pool: https://dexscreener.com/monad/0xad69e5f688d37a45aa8536ba9707772ef16aa5d8
- Balancer Monad pool API: https://api-v3.balancer.fi/graphql
- Curve MON LSTs pool: Curve.finance
- Neverland lending model: https://docs.neverland.money/
- Neverland smart contracts: Smart Contracts | Neverland Documentation
- Chainlink Data Feeds API reference: Data Feeds API Reference | Chainlink Documentation