Pheasant Network
HomeProductLinks
  • πŸͺΊWelcome
  • βˆ’ Bridge βˆ’
    • πŸŒ‰Protocol
      • Network Participants
      • L2 > L1 and L2 > L2
      • L1 > L2
      • CCTP
      • Fees
    • πŸ§‘β€πŸ’»Contracts
      • Overview
      • Technical Details
      • Audit
    • 🌐Network Code and Address
  • βˆ’ Swap βˆ’
    • πŸ”„Protocol
      • Architecture
      • Fees
    • πŸ§‘β€πŸ’»Contracts
  • 🌐Supported Networks
  • βˆ’ Ecosystem βˆ’
    • 🐦Pheasant Points
      • Pheasant Points Terms of Use
      • Snapshot History
    • ❓FAQ
    • πŸ“—Release Notes
    • ⏫Development Status
    • πŸ™ŒSupported by
    • 🎨Brand Assets
    • πŸ’šCollaboration Requests
    • πŸ”—Links
Powered by GitBook
On this page
  • Default
  • In the event of fraud
  • Sequence Diagram
  1. βˆ’ Bridge βˆ’
  2. Protocol

L1 > L2

PreviousL2 > L1 and L2 > L2NextCCTP

Last updated 6 months ago

Pheasant Network has chosen a different mechanism for L1-to-L2 transfers from the L2-to-L1 design, which comes with a tradeoff of minor complexity because the L2-to-L1 model is not cost-effective enough for token transfers from Layer 1 to Layer 2 from the users’ perspective as it requires an escrow contract on Layer 1.

Default

  1. A relayer deposits liquidity to the BondManager contract (Layer2 Bridge Contract).

  2. A user sends assets directly to relayer’s EOA on Layer 1, which triggers the bridging process.

  3. The relayer generates proof of the transaction made in 1 from its transactional hash and registers it and send asset through the PheasantNetworkBridgeChild contract.

In the event of fraud

Unlike processing from Layer 2 to Layer 1, in the case of processing from Layer 1 to Layer 2, if the relayer does not send assets to the user on Layer 2 after a certain period of time has elapsed since the user sent assets to the relayer, it is possible to execute a slash.

Sequence Diagram

πŸŒ‰