Bridges

Purpose

Lists cross-chain bridges.

Storage path

networks/<network_name>/bridge.csv

When to add

• Bridge has live routes to/from this chain.
• Exclude CEX transfers and inactive/beta-only bridges.

Example

slug,provider,actionButtons,chain,technology,txSpeedSla,throughputSla,openSource,starred,availableApis,monitoringAndAnalytics,additionalFeatures,assetTypes,price,economicalSecurity,economicalSecurityNote,auditsPerformed,decentralizationModel,sdk,support,supportedChains
axelar-mainnet,!provider:axelar,"[""[Bridge](https://app.squidrouter.com/?chains=314)"",""[Filecoin Cross-Chain Docs](https://docs.filecoin.io/smart-contracts/advanced/cross-chain-bridges)""]",mainnet,,,,,FALSE,,,,,,,,,,,,
chainsafe-filecoin-bridge,ChainSafe Systems,"[""[GitHub](https://github.com/ChainSafe/filecoindot)""]",testnet,Substrate-Based Bridge,null,null,TRUE,FALSE,"[""REST"",""SDK""]","[""Partial – dev dashboards""]","[""Filecoin ↔ Substrate chains (experimental)""]","[""FIL"",""wFIL""]",[Gas fee](https://blog.chainsafe.io/transaction-fee-mechanism-design/),TRUE,Open-source bridge/relayer framework built by ChainSafe; auditing for full Filecoin bridge not publicly final.,,Semi-decentralized,"[""Rust"",""JavaScript""]","[""Discord"",""Telegram""]","[""Polkadot Substrate-based chains, potentially Filecoin""]"

Columns

slug

Refer to Common Columns.

provider

Refer to Common Columns.

actionButtons

See Common Columns.

chain

Refer to Common Columns.

technology

Bridge mechanism/family.

Blank: Yes

Format: text

Examples: Liquidity Network, Hyperlane, custom.

Tips:

• Use short, standard terms.
• Avoid marketing language.
• Can match provider name.
• Use custom if no standard tech exists.

txSpeedSla

Target transfer time.

Blank: Yes

Format: text

Examples: Instant, <10 min, ~15–60 min

Tips:

• Use clear qualifiers (Instant/<N min).

throughputSla

Throughput/capacity.

Blank: Yes

Format: text

Examples: 100 tx/s, 10k transfers/day

Tips:

• Include unit + period.

openSource

Whether core implementation is open source.

Blank: No

Format: TRUE/FALSE

Tips:

• TRUE only if all core components are public.

support

Official support channels.

Blank: Yes

Format: JSON list

Examples: ["email","helpdesk","discord"]

Tips:

• Lowercase names.
• Include only official channels.
• Markdown links allowed.

supportedChains

Chains the bridge connects to/from (exclude the chain column value).

Blank: Yes

Format: JSON list

Examples: ["mainnet","arbitrum","optimism"]

Tips:

• Use common aliases (e.g., mainnet, sepolia).

availableApis

Public APIs/endpoints.

Blank: Yes

Format: JSON list

Examples: ["REST","GraphQL","WebSocket"]

Tips:

• List official/recommended APIs only.

monitoringAndAnalytics

Built‑in observability.

Blank: Yes

Format: JSON list

Examples: ["Bridge status","Transfer tracker","TVL dashboard"]

Tips:

• Use recognizable feature names.

additionalFeatures

Extras beyond core bridging.

Blank: Yes

Format: JSON list

Examples: ["Fast exits","Gasless claims","Refunds"]

Tips:

• Don’t duplicate other columns.

assetTypes

Supported asset categories.

Blank: Yes

Format: JSON list

Examples: ["ETH","ERC-20","ERC-721"]

Tips:

• Use canonical names.

price

See Common Columns.

economicalSecurity

Economic security present (e.g., insurance).

Blank: No

Format: TRUE/FALSE

Examples: TRUE, FALSE

economicalSecurityNote

How economic security works.

Blank: Yes

Format: text

Examples: Slashing, Insurance for paid users

Tips:

• Keep concise and factual.

auditsPerformed

Security audits.

Blank: Yes

Format: JSON list

Examples: ["Trail of Bits (Jul 2024)","OpenZeppelin (Sep 2024)"]

Tips:

• Prefer Auditor (Mon YYYY).

decentralizationModel

Transfer model.

Blank: Yes

Format: text

Examples: Decentralized, Hybrid, Centralized

sdk

Official SDK languages.

Blank: Yes

Format: JSON list

Examples: ["JavaScript","TypeScript","Solidity","Python"]

Tips:

• List language names, not package names.
• Include official/maintained SDKs only.

starred

See Common Columns.