Bridge Status Monitor

Ethereum

ETH → PLS 0

0 ETH ← PLS

PulseChain

0 PLS ← BSC

PLS → BSC 0

BSC

ETH ↔ PLS Validators

BSC ↔ PLS Validators

Indexer Health

Loading indexer status...

Pending Bridges 0

Loading pending bridges...

Completed (24h) 0

Loading completed bridges...

Documentation

Welcome to the Bridge Status Monitor documentation. Choose a section below to explore the public API, the detailed reference, or step-by-step bridge instructions.

🔌

API Documentation

Endpoints, parameters, examples, and event types for consuming the public REST API.

Open API docs →

📚

Reference

Contract addresses, event topics, correlation rules, database tables, and status definitions.

Open reference →

🌉

How To Bridge

Step-by-step instructions for bridging tokens safely using the monitored bridges.

Open how-to →

The Bridge Status Monitor exposes a public REST API for querying bridge events, transaction details, validator status, and aggregate statistics. All endpoints return JSON and support CORS.

Base URL

https://bridge-status.g4mm4.io/api

Bridge Types

Replace <type> with one of the supported bridge identifiers.

pls-eth Official Ethereum ↔ PulseChain bridge

pls-bsc TokenX BSC ↔ PulseChain bridge

Legacy aliases official (pls-eth) and tokensex (pls-bsc) are still accepted for backward compatibility.

Endpoints

GET /api/health

Health check. Returns API status and current timestamp.

GET /api/health/indexer

Indexer health and lag. Returns the latest scanned block per chain and detailed indexer_state rows.

GET /api/stats

Overall statistics across all monitored bridges, including total pending, completed, and average completion time.

GET /api/tx/<hash>

Full transaction details for a given transaction hash, including all indexed events, signatures, and lifecycle status.

GET /api/transaction/<hash>

Raw RPC details for any transaction hash on PulseChain, Ethereum, or BSC. Useful when a transaction is not yet indexed as a bridge event.

GET /api/address/<address>

All bridge activity for a wallet address, grouped by transaction.

GET /api/validator/<address>

Find a validator across all bridges and return its metadata, balance, and signature history.

GET /api/bridge/<type>/status

Bridge statistics: pending count, total requests, total bridged, total signatures, and last indexed block.

GET /api/bridge/<type>/last-success

The most recently completed bridge transaction for the bridge.

GET /api/bridge/<type>/recent

Recent bridge events. Optional query parameters:

limit — number of events to return (default 100, max 1000)
event_type — filter by event type (e.g. user_request_signature, user_request_affirmation, tokens_bridging_initiated, signed_for_user_request, tokens_bridged, affirmation_completed)

GET /api/bridge/<type>/pending

Pending bridge requests that have not yet completed.

GET /api/bridge/<type>/validators

Validator set and observed online/offline status for the bridge.

GET /api/bridge/<type>/validator/<address>/history

Signature history for a specific validator on a specific bridge.

GET /api/bridge/<type>/avg-completion-time

24-hour rolling average completion time for the bridge.

Example

curl https://bridge-status.g4mm4.io/api/bridge/pls-eth/status

                        {
  "bridge_type": "pls-eth",
  "pending": 42,
  "total_requests": 1234,
  "total_bridged": 1192,
  "total_signatures": 0,
  "last_block": 26812000
}
                    

Event Types

user_request_signature AMB home-side user request

user_request_affirmation AMB foreign-side user request

tokens_bridging_initiated OmniBridge token lock/burn (amount-bearing)

signed_for_user_request Validator signature on outgoing request

signed_for_affirmation Validator affirmation on incoming message

collected_signatures Enough signatures collected to relay

tokens_bridged OmniBridge token mint/unlock completion

affirmation_completed AMB incoming message executed

relayed_message AMB foreign-side incoming message executed

fee_distributed OmniBridge fee distribution

This reference documents every contract, event topic, configuration variable, and data field the Bridge Status Monitor uses to track the PulseChain Ethereum and BSC bridges. All values are verified against on-chain data.

Bridge Contracts

TokenX Bridge (pls-bsc)

PulseChain AMB proxy0xa3177000d645c599e45f946240f9c2f46d26718b

PulseChain OmniBridge mediator0xf1DFc63e10fF01b8c3d307529b47AefaD2154C0e

BSC AMB foreign proxy0x8c0db248e87f53e53f7d19a8bd1cfab16f5b69e7

BSC OmniBridge mediator0xb4005881e81a6ecd2c1f75d58e8e41f28d59c6b1

Official Bridge (pls-eth)

PulseChain AMB home proxy0x6ef79FD6f9f840264332884240539Ed7A2dA8b2b

Ethereum AMB foreign proxy0xd0764fae29e0a6a96ff685f71cfc685456d5636c

Ethereum OmniBridge mediator (current)0xe20e337db2a00b1c37139c873b92a0aad3f468bf

Ethereum OmniBridge mediator (legacy)0x1715a3e4a142d8b698131108995174f37aeba10d

PulseChain OmniBridge mediator0x4fd0aaa7506f3d9cb8274bdb946ec42a1b8751ef

PulseChain OmniBridge mediator (additional)0x0e18d0d556b652794ef12bf68b2dc857ef5f3996

Validator Topology

Validator sidePulseChain (home) for both bridges

pls-eth required signatures5 of 8

pls-bsc required signatures3 of 9

Gas tokenPLS on PulseChain

Online thresholdSigned within the last 24 hours

Minimum balance10,000,000 PLS

AMB Event Topics

UserRequestForSignature(bytes32,bytes)0x520d2afde79cbd5db58755ac9480f81bc658e5c517fcae7365a3d832590b0183

SignedForUserRequest(address,bytes32)0xbf06885f40778f5ccfb64497d3f92ce568ddaedb7e2fb4487f72690418cf8e4c

SignedForAffirmation(address,bytes32)0x5df9cc3eb93d8a9a481857a3b70a8ca966e6b80b25cf0ee2cce180ec5afa80a1

CollectedSignatures(address,bytes32,uint256)0x415557404d88a0c0b8e3b16967cafffc511213fd9c465c16832ee17ed57d7237

AffirmationCompleted(address,address,bytes32,bool)0xe194ef610f9150a2db4110b3db5116fd623175dca3528d7ae7046a1042f84fe7

UserRequestForAffirmation(bytes32,bytes)0x482515ce3d9494a37ce83f18b72b363449458435fafdd7a53ddea7460fe01b58

RelayedMessage(address,address,bytes32,bool)0x27333edb8bdcd40a0ae944fb121b5e2d62ea782683946654a0f5e607a908d578

OmniBridge Mediator Event Topics

TokensBridgingInitiated(address,address,uint256,bytes32,address)0xa7fdf47001202976d8892b5eb740c3344c0806be7b29037bfc0ed36535c6c4ce

TokensBridged(address,address,uint256,bytes32)0x9afd47907e25028cdaca89d193518c302bbb128617d5a992c5abd45815526593

FeeDistributed(uint256,address,bytes32)0xd560a522f77cfb4924d6fe51be1615e540a48a8931c48fe0349c7f47ebabe747

Correlation Rules

Cross-chain linkmessage_id from event topics

Signature linkmessage_hash = keccak256(request encodedData)

Amount eventtokens_bridging_initiated on source chain

Completion eventtokens_bridged / affirmation_completed / relayed_message

Database Tables

bridge_eventsEvery indexed bridge event across all chains

indexer_statePer-contract progress and last indexed block

bridge_validator_setsCurrent validator set, balances, and metadata per bridge

bridge_validator_sets_historyHistorical snapshots of validator sets by block range

transaction_detailsCached RPC transaction data and decoded inputs

token_pricesUSD price snapshots used for value estimates

token_registryToken metadata and icon mappings

Launch Blocks

The indexer scans from conservative lower bounds and discovers the exact first event for each contract automatically.

PulseChain17,233,000 (fork block)

BSC pls-bsc requests/initiations28,994,474

BSC pls-bsc completions29,000,133

Ethereum pls-eth~25,341,899

Status Definitions

PendingRequest emitted, no signatures yet

ProcessingAt least one validator signature observed

Validators signedRequired signatures collected, claim not yet executed

CompleteDestination claim executed and tokens delivered

This guide walks through bridging tokens safely. Always verify you are on the official bridge URL before signing any transaction.

Before You Start

Verify the URL — Only use URLs from official, verified sources. Never click bridge links from search engines or unsolicited messages.
Have gas on both chains — You need gas on the source chain to initiate the bridge and gas on the destination chain to claim tokens (for PulseChain → Ethereum/BSC directions).

Check token support — Not every token is bridgeable on every bridge. Confirm the token contract is listed by the bridge interface.

Step-by-Step: Ethereum → PulseChain (pls-eth)

Go to the official PulseChain ETH bridge UI.

Connect your wallet and make sure it is set to the Ethereum network.

Select the token you want to bridge and enter the amount.

Approve token spending if prompted.

Confirm the bridge transaction on Ethereum.

Wait for validators to sign the request on PulseChain.

Once enough signatures are collected, the bridge UI will let you claim the tokens on PulseChain. Confirm the claim transaction.

Your tokens are now on PulseChain.

Step-by-Step: PulseChain → Ethereum (pls-eth)

Go to the official PulseChain ETH bridge UI.

Connect your wallet and make sure it is set to the PulseChain network.

Select the token and amount to bridge out of PulseChain.

Approve token spending if prompted.

Confirm the bridge transaction on PulseChain.

Validators sign on PulseChain. When enough signatures are collected, the UI shows a claim button.

Switch your wallet to Ethereum and confirm the claim transaction.

Your tokens are now on Ethereum.

Step-by-Step: BSC ↔ PulseChain (pls-bsc)

Go to the TokenX BSC bridge UI.

Connect your wallet and select the source chain (BSC or PulseChain).

Select the token and amount to bridge.

Approve token spending if prompted.

Confirm the bridge transaction on the source chain.

Wait for validator signatures on PulseChain.

When the UI shows the claim is ready, switch to the destination chain and confirm the claim transaction.

Your tokens are now on the destination chain.

Safety Tips

Double-check the recipient address. If you bridge to the wrong address, the funds may be unrecoverable.

Bridge small amounts first to confirm the process works for your token.

Use this Bridge Status Monitor to track your transaction status, signature progress, and claim execution.

If a transaction is stuck at “Validators signed,” you can execute the claim yourself from the official bridge UI as long as you are the recipient.

Bridge Status Monitor

ETH ↔ PLS Validators

BSC ↔ PLS Validators

Indexer Health

Pending Bridges 0

Completed (24h) 0

Bridge Details

Transaction Details

Validator Details

Documentation

API Documentation

Reference

How To Bridge

Base URL

Bridge Types

Endpoints

Example

Event Types

Bridge Contracts

TokenX Bridge (pls-bsc)

Official Bridge (pls-eth)

Validator Topology

AMB Event Topics

OmniBridge Mediator Event Topics

Correlation Rules

Database Tables

Launch Blocks

Status Definitions

Before You Start

Step-by-Step: Ethereum → PulseChain (pls-eth)

Step-by-Step: PulseChain → Ethereum (pls-eth)

Step-by-Step: BSC ↔ PulseChain (pls-bsc)

Safety Tips

ETH ↔ PLS Validators

BSC ↔ PLS Validators

Indexer Health

Pending Bridges 0

Completed (24h) 0

Bridge Details

Transaction Details

Validator Details

Documentation

API Documentation

Reference

How To Bridge

Base URL

Bridge Types

Endpoints

Example

Event Types

Bridge Contracts

TokenX Bridge (pls-bsc)

Official Bridge (pls-eth)

Validator Topology

AMB Event Topics

OmniBridge Mediator Event Topics

Correlation Rules

Database Tables

Launch Blocks

Status Definitions

Before You Start

Step-by-Step: Ethereum → PulseChain (pls-eth)

Step-by-Step: PulseChain → Ethereum (pls-eth)

Step-by-Step: BSC ↔ PulseChain (pls-bsc)

Safety Tips

Pending Bridge Breakdown

USD Value Distribution

Value Known vs Unknown

Top Tokens

Pending Age