Composability

Built to leave the protocol

A Leaf becomes valuable when it can be used somewhere else.

HyperLeaf therefore treats composability as a first-class product goal rather than an implementation detail.

The composability stack

A Leaf can become useful at several layers:

Leaf asset
   ↓
DEX / secondary market
   ↓
lending / collateral
   ↓
vaults / structured products
   ↓
trading / margin / treasury systems

Each integration increases the number of things a productive position can do without forcing the underlying position to unwind.

ERC-20 simplicity, economic specificity

Every Leaf aims to look familiar to HyperEVM applications: an ERC-20 asset with a predictable transfer interface.

But the economic meaning remains listing-specific.

A lending protocol integrating hNEST should understand hNEST’s backing and withdrawal characteristics.

A market integrating a C1 Leaf should understand that the token is backed but not protocol-redeemable.

A C2 integration should expose the queue and maturity behavior rather than pretending the asset is instant cash.

Intrinsic yield composes differently from side rewards

When yield is embedded in the Leaf itself, composability is straightforward.

If the Leaf becomes worth more underlying over time, an LP or lending position can naturally carry that value.

Side-token rewards are different.

A wallet can claim a reward directly, but a smart-contract position such as an AMM pair may not automatically claim the same reward stream.

That is why HyperLeaf does not promise that every Leaf earns the same external HYPE reward regardless of where the token is held.

The composability rule

The token should remain useful even when a secondary reward subsystem is unavailable.

Core transfers should not depend on the perfect operation of a reward distributor.

Likewise, a reward mechanism should not be allowed to turn a marketable Leaf into an unusable asset merely because accounting on one reward path is temporarily broken.

What integrations should check

Before integrating a Leaf, an external protocol should evaluate:

• backing unit;
• supply / solvency model;
• exit topology;
• market liquidity;
• yield behavior;
• pause and incident semantics.

The best integrations expose these parameters rather than hiding them behind a generic APY number.