Superform v1
  • Introduction
  • Components
    • Protocol
    • Keepers
    • API
    • App
  • E2E Flows
    • Same-chain Deposit
    • Cross-chain Deposit
    • Same-chain Withdrawal
    • Cross-chain Withdrawal
  • Periphery Contracts
    • SuperformRouter
      • SuperformRouterPlus
      • SuperformRouterPlusAsync
    • PayMaster
    • PaymentHelper
    • EmergencyQueue
    • SuperformFactory
    • Forms
      • ERC4626Form
      • ERC5115Form
      • ERC7540Form
    • SuperPositions
      • ERC1155A
    • RewardsDistributor
  • Core Contracts
    • State Registries
      • CoreStateRegistry
      • AsyncStateRegistry
      • PayloadHelper
    • AMB Implementations
      • LayerzeroImplementation
      • LayerzeroV2Implementation
      • WormholeARImplementation
      • HyperlaneImplementation
      • AxelarImplementation
    • Broadcasting
      • BroadcastRegistry
      • WormholeSRImplementation
    • Bridge Validators
      • LiFiValidator
      • SocketValidator
      • SocketOneInchValidator
      • DebridgeValidator (and forwarder)
      • OneInchValidator
    • DstSwapper
    • Settings
      • SuperRBAC
      • SuperRegistry
  • SuperVaults
    • SuperVaults
  • Resources
    • Deployment Addresses
    • Subgraphs
      • Protocol Level Entities
      • Form Related Entities
      • Deposits and Withdrawals
      • SuperPosition Events
      • External Entities
    • Infrastructure Integrations
    • Security & Audits
    • Protocol License
    • Glossary
    • Protocol Multisig
    • Superform Labs Socials
Powered by GitBook
On this page
  • CCTP
  • DepositRequest
  • Message Received

Was this helpful?

  1. Resources
  2. Subgraphs

External Entities

CCTP

DepositRequest

Cross chain deposit requests sent in CCTP that initiate transfer of tokens using CCTP

{
  cctpdepositRequests(where:{
    transactionHash_contains_nocase: "0xb7a005b76fd06cda34f8ad0f2a99dc86d614110d3b3d3e2b8741c111816597f5"
  }) {
    nonce
    destinationDomain
    mintRecipient
    transactionHash
  }
}

The fields of cctpdepositRequest are as follows-

  1. nonce- An unique ID used by CCTP to track token transfers, this is unique for each payload from each chain

  2. destinationDomain- Destination chain DomainID

  3. mintRecipient- Destination for the tokens

Message Received

These represent the processing of a payload followed by mintAndWithdraw which mints the tokens to the receiver

{
  cctpmessageReceived(id: "135-10"){
    amount
    receiver
    token
    transactionHash
  }
}

The fields of TransferBatch are as follows-

  1. id- The id is in the format nonce-source_domain

  2. amount- Amount of tokens received by the receiver

  3. receiver- Receiver of the tokens

  4. token- received token

  5. transactionHash- it is the transaction hash lol

Last updated 6 months ago

Was this helpful?