layerzero-messaging

LayerZero Messaging (Hedera)

OFT pattern: deploy paired Omnichain Fungible Tokens — a standard OFT on the EVM side and an HTS connector OFT on Hedera — then setPeer both ways and send with LayerZero V2 fees.

OFT (EVM)  ←setPeer→  HTSConnectorOFT (Hedera)
  │ send / quoteSend          │ _debit burn / _credit mint (HTS 0x167)
  └──────── Endpoint V2 + ULN + DVN + Executor ────────┘

This skill focuses on LayerZero V2 OApp/OFT + Hedera HTS. Educational templates may use simple workers and a manual/UI lzReceive relay — not the same as production LayerZero Labs verification.

Quick Reference

See references/hedera-endpoints.md for where to source Endpoint/ULN/DVN addresses. See references/examples.md for wire and send sketches.

Critical: Wire Both Directions

Incomplete peer config bricks the pathway. For each local OApp:

1. setPeer(remoteEid, remoteOAppAsBytes32)
2. setSendLibrary / setReceiveLibrary (ULN302)
3. setConfig — ExecutorConfig (type 1) on send lib; UlnConfig (type 2) on send + receive libs
4. setEnforcedOptions — e.g. lzReceive gas for msgType 1 (token send)

Verify with peers(remoteEid) on both chains before sending.

Critical: Hedera HTS Connector Semantics

On Hedera, do not use a plain ERC-20 OFT as the primary path. Use an HTS-backed connector:

• Constructor creates fungible HTS via precompile 0x167 (supply key = connector)
• _debit: transfer HTS in → burn
• _credit: mint → transfer HTS out
• Amounts must fit int64 for HTS mint/burn/transfer
• Associate the receiver account with the HTS token before EVM → Hedera receives

// Deploy with value so createFungibleToken fee is paid
new HTSConnectorOFT{ value: htsCreateValue }(name, symbol, lzEndpoint, owner);

Send Flow

Hedera → EVM note: forge fee simulation can disagree with Hedera JSON-RPC wei/tinybar scaling — often quote via cast + scaled native fee for that direction.

Deploy Checklist (generic)

1. Deploy EVM OFT (optional premint)
2. Deploy Hedera HTS connector OFT with HTS create value
3. Deploy workers (Labs DVN/executor or educational simple workers)
4. Wire both OApps (setPeer + libraries + config + enforced options)
5. Associate Hedera account with htsTokenAddress()
6. Sync frontend config if applicable; fund relay key if using UI auto-relay
7. Send small amount; track on LayerZero Scan (testnet/mainnet as appropriate)

Educational Relay

Some templates use simple DVN/executor mocks and an explicit lzReceive relay step. Treat that as a learning aid — production apps rely on LayerZero’s verification network, not a custom relayer key in the app server.

Checklist

• Peers set both ways with correct EIDs (not EVM chain IDs)
• Send/receive libraries + ULN/executor config applied
• Hedera side is HTS connector; create fee paid; supply key is connector
• Receiver associated with HTS token before inbound transfers
• quoteSend native fee attached to send
• Receiver address encoded as bytes32
• Educational disclaimer: not audited / not for mainnet funds

References

• references/examples.md — OFT, HTS connector, wire, send
• references/hedera-endpoints.md — EIDs vs chain IDs, where to source addresses
• LayerZero V2 docs
• LayerZero deployments metadata