Across is now live on Lens Chain!
Bridge Now
Across Documentation
V2 Developer Docs
V2 Developer Docs
  • How Across Works
    • Overview
      • Roles within Across
      • Fee Model
      • Validating Root Bundles
      • Disputing Root Bundles
  • Developers
    • Across API
    • Across SDK
    • Contract Addresses
      • Mainnet (Chain ID: 1)
      • Arbitrum (Chain ID: 42161)
      • Optimism (Chain ID: 10)
      • Base (Chain ID: 8453)
      • zkSync (Chain ID: 324)
      • Polygon (Chain ID: 137)
    • Selected Contract Functions
    • Running a Relayer
    • Integrating Across into your application
    • Composable Bridging
    • Developer notes
    • Migration from V2 to V3
  • ADDITIONAL INFO
    • Support Links
    • Bug Bounty
    • Audits
Powered by GitBook
LogoLogo
On this page
  • ETH/WETH Behavior
  • More questions?
  1. Developers

Developer notes

PreviousComposable BridgingNextMigration from V2 to V3

Last updated 2 years ago

This page includes a running list of Across behaviors that developers who are using Across should be aware of:

ETH/WETH Behavior

Across liquidity pools are filled using WETH but, depending on the context, Across will sometimes send a user ETH and sometimes send a user WETH.

  • If a bridge transfer is being sent to an EOA, the EOA will receive ETH (not WETH)

  • If a bridge transfer is being sent to a contract, the contract will receive WETH (not ETH)

More questions?

If you are a developer working on integrating your project with Across, please reach out to us on !

We look forward to helping you integrate with the best bridge around!

Discord