Somnia
Somnia is supported in Frax Mesh as a standard EVM deployment in the Fraxtal hub model. It uses the same deterministic 0x000000... OFT address set as Tempo, but it does not use Tempo's TIP-20 extensions or stablecoin-denominated gas flow. On Somnia, bridge fees are paid in native gas and routing uses the standard OFT and HopV2 contracts.
Network Constants
| Item | Value |
|---|---|
| Chain ID | 5031 |
| LayerZero EID | 30380 |
| RPC | https://api.infra.mainnet.somnia.network |
| Explorer | explorer.somnia.network (opens in a new tab) |
| Admin Safe | 0x9527e19F55d1afCE9F1e9Edcea79552bF41983F9 (opens in a new tab) |
| ProxyAdmin | 0x000000dbfaA1Fb91ca46867cE6D41aB6da4f7428 (opens in a new tab) |
| LayerZero Endpoint | 0x6F475642a6e85809B1c36Fa62763669b1b48DD5B (opens in a new tab) |
Required Contracts
Somnia is fully wired into the Fraxtal hub with the complete Frax OFT set plus the HopV2 relay contracts.
For the complete crosschain address matrix, including Fraxtal lockboxes and all remote Hop contracts, see Addresses.
Routing Model
- Fraxtal is the hub chain for Somnia.
Somnia -> FraxtalandFraxtal -> Somniaare the direct routes.Somnia -> other EVM chainsrelays through Fraxtal with HopV2.- Somnia uses standard OFT fee quoting and native gas. There is no Somnia-specific TIP-20 fee token path.
HopV2 Admin Configuration
The Somnia deployment in hop-v2 (opens in a new tab) includes a dedicated DeployRemoteHopV2Somnia script and a Fraxtal-side SetSomniaExecutorOptions admin script.
| Item | Value |
|---|---|
| Executor | 0x4208D6E27538189bB48E603D6123A94b8Abe0A0b (opens in a new tab) |
| DVN | 0x282b3386571f7f794450d5789911a9804FA346b4 (opens in a new tab) |
| Send library | 0xC39161c743D0307EB9BCc9FEF03eeb9Dc4802de7 (opens in a new tab) |
| Required receive gas | 1,000,000 |
The required Fraxtal-side executor option is setExecutorOptions(30380, options) with a 1_000_000 receive gas budget. That is the deployed configuration used for composed Fraxtal to Somnia deliveries.
Deployment Coverage
The canonical Somnia implementation lives in these scripts:
- DeployRemoteHopV2Somnia.s.sol (opens in a new tab)
- SetSomniaExecutorOptions.s.sol (opens in a new tab)
- SetupSourceFraxOFTFraxtalHubSomnia.s.sol (opens in a new tab)
- SetupDestinationFraxOFTFraxtalHubSomnia.s.sol (opens in a new tab)
- SendFraxOFTFraxtalToSomnia.s.sol (opens in a new tab)
- SendFraxOFTSomniaToFraxtal.s.sol (opens in a new tab)
The OFT setup scripts cover all six deterministic OFTs on Somnia, and the destination setup script narrows the pairing to the required Fraxtal and Somnia configs for hub routing.
Verified Routes
The Frax team has already recorded successful send transactions in both directions:
| Direction | LayerZeroScan |
|---|---|
| Fraxtal -> Somnia | tx (opens in a new tab) |
| Somnia -> Fraxtal | tx (opens in a new tab) |
That means the required Somnia surface area is in place: deterministic OFTs, HopV2 relay, RemoteAdmin, executor options, and tested Fraxtal hub routes.