You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/oft-alt/README.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,7 @@ This example demonstrates the most common scenario for OFTAlt deployments:
53
53
```
54
54
55
55
**This example includes both contracts:**
56
+
56
57
-**`MyOFT.sol`** - Standard OFT for regular EVM chains with native gas fees (deployed on Arbitrum)
57
58
-**`MyOFTAlt.sol`** - OFTAlt for chains with Alt Endpoints using ERC-20 fees (deployed on Tempo)
58
59
@@ -63,6 +64,7 @@ The `lz:oft:send` task automatically detects which endpoint type is being used a
63
64
The **OFTAlt** (Omnichain Fungible Token Alt) is a variant of the standard OFT designed for blockchains that use [Alt Endpoints](https://docs.layerzero.network/v2/concepts/protocol/layerzero-endpoint-alt). Alt Endpoints are deployed on chains where transaction fees are paid in ERC-20 stablecoins rather than native tokens.
64
65
65
66
Examples of chains using Alt Endpoints:
67
+
66
68
-**Tempo**: A payments-focused blockchain where fees are paid in TIP-20 stablecoins
67
69
68
70
The OFTAlt works identically to standard OFT in terms of token transfer mechanics—burning on the source chain and minting on the destination chain—but handles fee payment differently.
@@ -71,12 +73,12 @@ The OFTAlt works identically to standard OFT in terms of token transfer mechanic
- Native tokens for gas on standard EVM chains (e.g., ETH on Arbitrum Sepolia)
130
133
-**ERC-20 fee tokens** (stablecoins) on Tempo testnet for LayerZero fees
131
134
@@ -263,7 +266,7 @@ pnpm test:hardhat
263
266
264
267
### Adding other chains
265
268
266
-
If you're adding another EVM chain, first, add it to the `hardhat.config.ts`.
269
+
If you're adding another EVM chain, first, add it to the `hardhat.config.ts`.
267
270
268
271
Then, modify `layerzero.config.ts` with the following changes:
269
272
@@ -341,15 +344,15 @@ Calls the configuration functions between your deployed OApp contracts on every
341
344
342
345
Running `lz:oapp:wire` will make the following function calls per pathway connection for a fully defined config file using your specified settings and your environment variables (Private Keys and RPCs):
343
346
344
-
- <ahref="https://github.com/LayerZero-Labs/LayerZero-v2/blob/main/packages/layerzero-v2/evm/oapp/contracts/oapp/OAppCore.sol#L33-L46"><code>function setPeer(uint32 _eid, bytes32 _peer) public virtual onlyOwner {}</code></a>
347
+
- <ahref="https://github.com/LayerZero-Labs/LayerZero-v2/blob/main/packages/layerzero-v2/evm/oapp/contracts/oapp/OAppCore.sol#L33-L46"><code>function setPeer(uint32 \_eid, bytes32 \_peer) public virtual onlyOwner {}</code></a>
0 commit comments