# LayerZero and Hyperlane, both always

Pangea v4: how a coin launches today. Every new launch is a v4 launch. A v4 coin lives on up to six chains: Robinhood Chain, Base, Ethereum, BNB Chain (BSC), Solana and Elysium. The four EVM chains and Solana carry LayerZero and Hyperlane; Elysium carries Hyperlane only. This tab is all of v4: creating a coin, chains and pairs, fees and holder rewards, opening a chain later, handing over, launching from your own wallet, the Bundle Kit, bridging, contracts and the API. Coins launched before v4 are in the v3 and v2 tabs.

Every v4 coin uses both LayerZero and Hyperlane. Neither is a fallback for the other, and neither the creator nor the sender chooses between them: both are always on, on every route that has both. A route that touches Elysium has Hyperlane only, because LayerZero does not reach Elysium.

## What holds on both

- Supply stays exact: the tokens are burned on the source chain before anything is minted on the destination.
- A message is received only over the transport it was sent on, from that route's peer, and at most once.
- There is no mint cap per transport.
- A coin uses only the transports in its transport list, fixed at its launch: by default every transport all its chains have, LayerZero and Hyperlane today. A transport Pangea adds later is offered only to coins launched after it was added.
- The default is per route, set by the contracts themselves: LayerZero and Hyperlane on every route, and Hyperlane only on a route that touches Elysium, whatever the coin's home chain. The launch page shows the transports of each route; it does not ask for them.
- Elysium is opt-in per coin. Elysium has no LayerZero endpoint, so transfers to and from Elysium go over Hyperlane. A coin that lists Elysium keeps LayerZero and Hyperlane between its other chains (for example Ethereum and Base); only its Elysium routes are Hyperlane only. Elysium messages are attested by Pangea's validator alone. The launch page says so before you pick Elysium.

## Who checks a message

- Every mint needs two signer sets, Pangea's and one Pangea does not control. Two, not more, for speed; a route is set once, so no third set can be added to it later.
- LayerZero: Pangea's verifier and LayerZero Labs' verifier.
- Hyperlane: Pangea's own validators and Hyperlane's validators: the Abacus Works set on Ethereum, Base and BNB Chain, the default set on Robinhood Chain and Solana. Pangea's set can never be removed from a route; the Hyperlane side can be rotated, as verifier sets are on LayerZero.
- A coin that uses both transports is as strong as the weaker of the two: either can deliver it.

## How long each waits

Every wait Pangea runs is 1 block on every chain: its LayerZero verifier and Hyperlane validators, its Hyperlane message delivery, its delivery, its bridge indexer and the settle of a sponsored launch. That is the fastest setting, and Pangea accepts the reorg risk that comes with it. The one exception is a Hyperlane message sent from Solana: Hyperlane message delivery reads Solana only once a block is finalized, so that message waits until the block is finalized. A Hyperlane message also waits for Hyperlane's set (except from Elysium, where Pangea's validator signs alone), which keeps its own wait, so on some chains it is slower:

| From | Pangea's LayerZero verifier waits | Pangea's Hyperlane validator waits |
| --- | --- | --- |
| Ethereum | 1 block | 1 block |
| Base | 1 block | 1 block |
| BNB Chain | 1 block | 1 block |
| Robinhood Chain | 1 block | 1 block |
| Elysium | no LayerZero | 1 block (Pangea's validator alone) |
| Solana | 1 block | until the block is finalized, about 13 seconds |

> **Note:** A transfer is followed on the explorer of its transport: LayerZero Scan or the Hyperlane Explorer. The Bridge page links each transfer to the right one.

## The fee you pay: fee up to X, unused part refunded

- Every paid send (the Bridge page, the SDK and Pangea's bots) pays the quoted transport and delivery fee plus a buffer, so a cost figure raised between the quote and the landing cannot make the send fail. The card says "fee up to X, unused part refunded": X is the most it can take, and the unused part is refunded to the sender in the same transaction (LayerZero and Hyperlane both refund what the fee did not use). From Solana the card says "Transport fee up to X SOL": only what is charged is paid, the rest stays in your wallet.
- The buffer is the larger of 15% and the keeper's max step: 50% now. The max step is the largest raise the deviation keeper may post for one cost figure in one post; a bigger move is posted in several steps, each at most the max step, so one buffer always covers one post.
- The max step is one config value, `PANGEA_KEEPER_MAX_STEP_BPS`, read by the keeper, the web, the SDK and the bots alike: a whole number of basis points from 500 to 5,000. Unset, it is the default 5,000 (50%); here it is 5,000 (50%). An invalid value is never used: the keeper refuses to start on it.

## Sending from Solana

From Solana a v4 coin is bridged on the Bridge page too: Quote shows the cost read from the chain, transport and delivery, and Bridge then signs exactly the quoted transaction.

## Cheapest chain: a sale through Solana

A Cheapest chain sale through Solana sends your coins to Pangea's sale program on Solana with your sale's order, and the app offers it only while that program is set up to receive it. Send to the sale composer only through the app or the SDK: a hand-made transfer to it carries no order and may not be recoverable.

Part of the Pangea documentation, v4 tab: https://www.pangea.trade/app/docs.md