Events List

​

Bridge/bridge+swap events

• BRIDGE_PENDING - sent when the bridge quote is committed
• BRIDGE_ACCEPTED - sent when the deposit transaction was received and validated
• BRIDGE_EXECUTED - sent when the bridge is completed and received on the destination chain
• BRIDGE_REFUNDED - when a swap is involved, the bridge might get refunded if the token price moved too much since the quote was emitted
• BRIDGE_CANCELLED - sent when a committed bridge is CANCELLED (note that that cancelled bridges can still be actioned if a matching deposit is detected on-chain, subsequent bridge events will be sent)

​

Smart Deposit Addresses events

• DEPOSIT_ADDRESS_CREATED - sent when a new Smart Deposit Address is generated Event structure:

{
  _tag: "DEPOSIT_ADDRESS_CREATED",
  depositChain: string
  depositAddress: string
  destinationChain: string
  destinationAddress: string
  tokenOut?: string
  postBridgeData?: PostBridgeData
  addressNote?: string
}

• BRIDGE_* - the same BRIDGE_PENDING, BRIDGE_ACCEPTED and BRIDGE_EXECUTED events as described above will be sent for Smart Deposit Address related activity.
• DEPOSIT_ADDRESS_BRIDGE_REJECTED - sent when a Smart Deposit Address bridge is rejected. Event structure:

{
  _tag: "DEPOSIT_ADDRESS_BRIDGE_REJECTED",
  _id: string, // bridge ID
  tokenSymbol: string
  tokenAddress: string
  amount: string
  amountUsd: string
  amountWei: string
  sender: string // depositor address
  txHash: string // deposit transaction hash
  reason: string // reason why it was rejected, e.g "UNDER_MIN"
  createdAt: string
  depositAddress: { // associated deposit address parameters
    depositChain: string
    depositAddress: string
    destinationChain: string
    destinationAddress: string
  }
}

• DEPOSIT_ADDRESS_BRIDGE_REJECTED - UNSUPPORTED_TOKEN - sent when a Smart Deposit Address bridge is rejected as the token sent is not supported by Rhino.fi. The full list of supported chains and assets can be found here: rhino.fi - Docs**Supported Chains - **rhino.fi - Docs. N.B Rhino.fi monitors for a selection of unsupported tokens per chain however this does not cover all scenarios where an unsupported token may be sent to an Smart Deposit Address. The event structure is:
  {
    _tag: "DEPOSIT_ADDRESS_BRIDGE_REJECTED - UNSUPPORTED_TOKEN",
    _id: string, // bridge ID
    tokenSymbol: string
    tokenAddress: string
    amount: string
    amountUsd: string
    amountWei: string
    sender: string // depositor address
    txHash: string // deposit transaction hash
    reason: string // reason why it was rejected, e.g "UNDER_MIN"
    createdAt: string
    depositAddress: { // associated deposit address parameters
      depositChain: string
      depositAddress: string
      destinationChain: string
      destinationAddress: string
    }
  }
  
• DEPOSIT_ADDRESS_BRIDGE_DELAYED - sent when a bridged transaction is taking longer than expected. This may be due to onchain congestion. The bridge transaction will be re-tried, there is no action required of the user. The event structure is:

{
  _tag: "DEPOSIT_ADDRESS_BRIDGE_DELAYED",
  _id: string, // bridge ID
  tokenSymbol: string
  tokenAddress: string
  amount: string
  amountUsd: string
  amountWei: string
  sender: string // depositor address
  txHash: string // deposit transaction hash
  originalErrorTag: string // reason why the bridge is delayed
  depositAddress: { // associated deposit address parameters
    depositChain: string
    depositAddress: string
    destinationChain: string
    destinationAddress: string
  }
}

• SDA_REFUND_COMPLETED sent when a a refund is issued from an SDA.

{
  _tag: "SDA_REFUND_COMPLETED"
  refundId: string,
  depositAddress: string,
  depositChain: string,
  recipient: string, // recipient of the refund
  trigger: {
    _tag: "REJECTED_BRIDGE" | "UNSUPPORTED_TOKEN",
    rejectedDepositAddressBridgeId: string | undefined,
    nativeToken: boolean, // If this is true, tokenAddress will be undefined as native tokens don't have an address
    amountWei: string,
    amount: string | undefined, // Human readable refund amount
    amountUsd: string | undefined,
    tokenAddress: string | undefined,
    tokenSymbol: string | undefined,
  },
  "originalDepositTxHash": string | undefined, // hash of the deposit transaction that is refunded
  txHash: string, // hash of the refund transaction
  txTimestamp: string, // timestamp of the refund transaction
}

• REJECTED_BRIDGE: Reason is a deposit we detected but rejected. originalDepositTxHash will contain the hash of the original deposit transaction and the amount and tokenSymbol fields will have values.
• UNSUPPORTED_TOKEN: Reason is a deposit with an unsupported token. originalDepositTxHash will not be available for this as we did not detect the transaction in our system.

​

Webhook Event Flows