Documentação

English

Português
Español

English

Português
Español

Appearance

Bridge Transactions (Journal) ​

Access Prerequisites

  • Permission (module): viewBridgeJournal
  • License/Feature: None
  • Menu container: GENERAL → group Transaction Journals → Bridge Transactions (/bridge-journal)

What it is / when to use ​

The bridge moves assets between different blockchain networks (e.g.: token on Ethereum → token on Polygon). This journal lists each bridge transaction with the source and destination network, the input and output asset, the amounts, and the current routing status. The operator uses this screen to track a user's cross-chain transfer, diagnose pending/expired bridges, and open the technical detail for support.

Prerequisites ​

  • Permission: viewBridgeJournal registered for the role (dual permission — CPM enum + dynamic module in the DB).
  • License/Feature: none.
  • Dependencies on other screens: None. The available networks and tokens are loaded from the backend itself when the screen is opened.

Step by step ​

  1. Go to Transaction Journals → Bridge Transactions.
  2. The screen loads the list of networks (except the INTERNAL network) and the tokens, and immediately fetches the first transactions.
  3. Search by user ID in the search field (typing has a 500 ms debounce).
  4. Filter by network and by status using the selectors. The "All" value removes the network filter.
  5. Click the view icon (eye) to open the technical detail of the bridge.

Filters and columns ​

Filter / ColumnWhat it shows / doesData source
Search by user IDFilters by the bridges of a customerId. 500 ms debounce.customerId parameter sent to BridgeService.
Network filterRestricts by network; sends the chain_id of the selected network. "All" does not filter.CollectionsService.getNetworks() (excludes INTERNAL).
Status filterALL, FILLED, PENDING, PLANNED, REFUNDED, EXPIRED, SLOW_FILL_REQUESTED.BridgeTransactionStatus.
Date (createdAt)When the bridge was created.createdAt.
IdBridge transaction identifier.id.
User (userId)Owner of the transaction.userId.
Input amount (inputAmount)Amount sent on the source network.inputAmount (formatted via BigNumber).
Output amount (outputAmount)Amount received on the destination network.outputAmount (formatted via BigNumber).
Source / destination networkNetwork name resolved from the chainId.originChainId / destinationChainId.
Input / output tokenSymbols of the transacted assets.inputTokenSymbol / outputTokenSymbol.
StatusRouting state; green for FILLED, red for EXPIRED/REFUNDED.status.
Details (action)Opens the bridge's technical modal.openDetailsComponent(id).

Pagination is server-side: the paginator uses the total_count returned by the backend.

Actions and modals ​

  • View (eye): opens BridgeDetailsModalComponent in full screen, with the complete bridge transaction data (read-only).

Business rules / considerations ​

Attention

  • The difference between input amount and output amount reflects the bridge's costs/routing (gas, provider fees, slippage). Do not interpret the difference as an error.
  • EXPIRED and REFUNDED indicate that the asset did not reach the destination — in REFUNDED the user receives the amount back at the source. Use the detail to confirm the outcome before guiding the customer.
  • SLOW_FILL_REQUESTED is an intermediate state of slow fill — the bridge may still complete; do not treat it as a definitive failure.
  • Financial amounts: input and output are treated as BigNumber — no rounding at the source; the display uses 2 decimal places for reading only.