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
  1. − Bridge −
  2. Protocol

Network Participants

Pheasant Network consists of three participants - user, relayer and disputer.

  • User: a participant who wishes to transfer tokens from one network to another through the bridge (e.g. send ETH on Optimism to Arbitrum)

  • Relayer: an actor who accommodates users' requests to transfer assets from an origin chain to a destination chain (e.g. send ETH on Arbitrum to a user and receive their ETH on Optimism)

  • Disputer: a party who flags the system when noticing a suspicious action on the network and challenges the transaction's validity. Anyone can be a disputer including users. They need to object to the relayer within a dispute period of about 51 min when they catch a dubious transaction since Ethereum's BLOCKHASH opcode limitation only allows verification for transactions in the last 256 blocks at this time, and they might fail to spot invalid transactions. (e.g. question a relayer when a user has yet to receive their asset on a destination chain after a certain period, detect an invalid transactional data registered with BridgeChildContract)

PreviousProtocolNextL2 > L1 and L2 > L2

Last updated 7 months ago

🌉