EndpointV2, with LZEndpointDollar (LZD) as the fee token. LayerZero fees are paid through ERC-20 transfers instead of msg.value.
What changes on Tempo
| Standard EVM | Tempo | What changes |
|---|---|---|
| EndpointV2 | EndpointV2Alt | accepts ERC-20 fee payments instead of native value |
| Native token fees | LZD | canonical USD fee token wrapping whitelisted stablecoins |
| OApp | OAppAlt | OApp variant for chains without a native gas token; fees are paid in LZD instead of msg.value |
| OFT / OFTAdapter | OFTAlt / OFTAdapterAlt | OFT variants for chains without a native gas token |
| ERC-20 | ERC-20 and TIP-20 | Tempo’s native token standard with role-based administration |
Developing on Tempo: Tempo’s EVM has higher opcode costs than standard EVMs, and fork testing requires Tempo’s Foundry fork. See the Tempo developer docs for more info.
Support OFTs and OApps
Adapt your OFT and OApp deployments for Tempo: fee payment, OFTAlt
contracts, and the wrapper flow.
LZEndpointDollar (LZD)
API reference for the canonical fee token: wrapping, unwrapping, whitelisting,
and contract addresses.
Alt Variants (OFTAlt & OAppAlt)
Why Tempo needs OFTAlt and OAppAlt, how the ERC-20 fee path works, and
comparison with standard contracts.
TIP-20 Token Standard
How Tempo’s native token standard works with LayerZero: roles, ERC-20
compatibility, and OFTAlt integration.
Stargate UX
Consumer-side UX differences when using Stargate on Tempo: approvals,
supported tokens, and gas estimation.
Tempo uses EndpointV2Alt, a variant of the LayerZero Endpoint designed for chains without a native gas token. See the EndpointV2Alt concept page for protocol-level details. For questions, join the LayerZero Discord.