Bridges and messaging layers built to fail safely.
BitAzure engineers cross-chain systems: token bridges, generalized message passing, cross-chain swaps and liquidity networks across EVM and non-EVM chains, with validator or MPC security models, relayer infrastructure and the monitoring and circuit breakers that bridges have historically lacked.
- EVM and non-EVM interoperability
- Token bridging and arbitrary message passing
- Relayer, validator and MPC architectures
- Rate limits, circuit breakers and replay protection
What is cross-chain development?
Cross-chain development is the engineering of systems that move assets and messages between independent blockchains: bridge contracts on each chain, relayers that transport proofs and events, a validator or MPC set that attests to them, and the monitoring and controls that limit damage when any of those components fails.
Bridges hold or mint value on behalf of users, which makes them among the most attacked components in the industry. A serious design specifies the trust model explicitly (external validators, MPC signers, light clients or optimistic verification), bounds the loss from any single failure with rate limits and circuit breakers, and makes every message unique and unreplayable.
BitAzure builds bridges and interoperability layers for EVM chains, Solana, Cosmos and Bitcoin, from lock-and-mint token bridges to generalized messaging and cross-chain swap routing. Delivery includes relayer and validator infrastructure, an operator console and the watchtower services that verify the bridge from the outside.
Cross-chain and bridge development services
Transport, attestation and control are built as separate systems with separate keys, so no single compromised component can move funds on its own.
Interoperability Scope
- EVM interoperability between Ethereum, Layer 2s and other EVM chains
- Non-EVM interoperability with Solana, Cosmos (IBC) and Bitcoin
- Canonical rollup bridges and native messaging integration
- Integration with third-party messaging protocols where appropriate
- Chain abstraction layers for multi-chain applications
Bridging & Messaging
- Token bridging: lock-and-mint, burn-and-mint and liquidity-pool models
- Generalized message passing with ordered or unordered delivery
- Cross-chain contract calls and remote execution
- NFT and data bridging with metadata integrity
- Replay protection with nonces, chain IDs and message hashes
Swaps & Liquidity
- Cross-chain swaps with atomic or intent-based settlement
- Cross-chain liquidity pools and rebalancing
- Solver and filler networks for intent fulfilment
- Fee models for relayers, liquidity providers and the protocol
- Slippage and route quoting across chains
Security Models
- Validator set architecture with staking, slashing and rotation
- MPC architecture with threshold signing and key resharing
- Multisig architecture with role separation and hardware-backed signers
- Light-client and proof-based verification where chains support it
- Optimistic verification with fraud-proof windows
Relayer & Operator Infrastructure
- Relayers with finality tracking, retries and gas management
- Event indexers per chain with reorg handling
- Operator console for limits, pauses and key rotation
- Deployment automation across chains and environments
- Multi-region, redundant relayer and validator operation
Monitoring & Controls
- Rate limits per asset, per chain and per time window
- Circuit breakers triggered by anomalous volume or invariant breaches
- Watchtower services verifying mint and unlock against source events
- Real-time monitoring, alerting and incident runbooks
- Supply reconciliation across all connected chains
Reference bridge architecture
The reference design keeps attestation separate from transport: relayers move data but cannot authorise anything, the validator or MPC set signs only finalized events, and an independent watchtower can halt the destination contract when invariants break.
Hover or focus a component to see its role in the architecture.
- User / dApp (Initiates transfer): Locks or burns tokens, or sends a message, through the source-chain bridge contract.
- Source Chain Contract (Lock / burn · emit): Escrows or burns assets and emits a uniquely identified message event.
- Relayers (Transport · retries): Fetch finalized events and proofs and submit them; hold no signing authority.
- Event Indexer (Finality tracking): Tracks source-chain events, reorgs and finality before anything is forwarded.
- Validator Set (Attestation quorum): Independently verifies each finalized event and votes toward the signing threshold.
- MPC Signing (Threshold signatures): Produces a single threshold signature once quorum is reached; keys are resharable and rotated.
- Watchtower (Invariants · circuit breaker): Independently re-verifies every mint against source events and can trigger a pause.
- Destination Contract (Mint / unlock · replay guard): Verifies the signature, checks nonce and rate limits, then mints or unlocks.
- Operator Console (Limits · pause · rotation): Multisig-gated controls for limits, pauses, key rotation and upgrades.
- Monitoring & Alerts (Supply · latency · anomalies): Cross-chain supply reconciliation, transfer latency and anomaly alerting.
Source
- Lock / burn contract
- Event emission
- Finality tracking
Transport
- Relayers
- Event indexers
- Retry & gas management
Attestation
- Validator set
- MPC threshold signing
- Proof verification
Destination & control
- Mint / unlock contract
- Rate limits & circuit breakers
- Watchtower & console
Cross-chain systems we build
Native bridge for a new chain
Canonical bridge connecting an app-chain or rollup to Ethereum and other ecosystems.
Multi-chain stablecoin or asset
Burn-and-mint bridging with canonical supply tracking across every chain.
Cross-chain DEX or aggregator
Swap routing that sources liquidity on one chain and settles on another.
Cross-chain governance
Voting on one chain executing parameter changes on many.
Enterprise chain connectivity
Messaging between a permissioned network and public chains for settlement.
Bitcoin and Solana connectivity
Bringing non-EVM assets into EVM DeFi with verifiable custody models.
Why teams build bridges with BitAzure
Explicit trust model
Who can authorise a message, and what bounds their power, is documented before code is written.
Bounded loss
Rate limits and circuit breakers cap the damage from any single compromise.
Separation of duties
Relayers, signers and watchtowers are distinct systems run under different keys.
Chain breadth
EVM, Solana, Cosmos and Bitcoin adapters behind a consistent message format.
Operational tooling
Operator console, dashboards and rehearsed runbooks for pauses and key rotation.
Reviewed and rehearsed
Adversarial testing, audit coordination and incident drills before mainnet.
Technologies we use for cross-chain development
Solidity
BlockchainEVM smart contracts: tokens, DeFi protocols, governance, vesting.
Rust
BackendMemory-safe, low-latency engines, on-chain programs and tooling.
Go
BackendConcurrent network services, relayers and infrastructure daemons.
TypeScript
FrontendStrict typing across the entire stack, client to contracts tooling.
EVM
BlockchainEthereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche.
Ethereum
BlockchainMainnet and L2 deployments, account abstraction, indexing.
Solana
BlockchainRust programs with Anchor, SPL tokens and high-throughput dApps.
Cosmos SDK
BlockchainApp-chains, IBC and custom consensus modules.
Bitcoin
BlockchainUTXO wallets, PSBT signing, Lightning integrations.
Kafka
DatabaseDurable event streaming between engines and services.
PostgreSQL
DatabaseTransactional ledgers, ledgers-of-record and analytical workloads.
Kubernetes
InfrastructureAutoscaling, rolling deployments and workload isolation.
How we deliver a bridge
Every engagement follows a documented, milestone-driven path from discovery to continuous development.
- 01
Trust model & threat analysis
Chains, asset flows, attacker models and the verification approach are decided and documented.
- 02
Protocol & contract design
Message format, replay protection, limits, upgrade path and emergency controls are specified.
- 03
Contract implementation
Source and destination contracts are built with unit, fuzz and invariant tests, including malicious-message cases.
- 04
Relayer, signer & watchtower build
Off-chain infrastructure is developed with redundancy, finality handling and independent verification.
- 05
Adversarial testing & review
Testnet deployment, chaos and attack simulations, and coordination of independent audits.
- 06
Guarded launch & operations
Low limits at launch, progressive increases, continuous monitoring and rehearsed incident procedures.
Security practices in bridge development
Replay protection
Every message carries a unique nonce, source chain ID and hash; processed messages are recorded on the destination.
Finality discipline
Attestation waits for chain-specific finality to prevent reorg-based double spends.
Threshold signing
MPC or multisig quorums with key resharing, rotation and hardware-backed signers.
Rate limits and circuit breakers
Per-asset and per-window caps with automatic pause on anomalies.
Independent watchtower
A separate service verifies every mint against source events and can halt the bridge.
External review
Adversarial testing and third-party audit coordination; audited status is stated only when a report exists.
We coordinate independent third-party audits on request and never claim an audit, certification or compliance status unless it has actually been obtained.
What to decide before building a bridge
Trust assumptions
External validator sets, MPC and light clients differ in trust and cost; choose knowingly and disclose it to users.
Finality differences
Chains finalize at different speeds and with different guarantees; the bridge must respect the slowest relevant one.
Liquidity versus lock-and-mint
Liquidity bridges settle faster but need capital and rebalancing; lock-and-mint concentrates value in one contract.
Upgrade control
Bridge upgrades are high risk; timelocks, multisig and public notice are essential.
Operational burden
Validators, relayers and watchtowers must run continuously; plan the team and the on-call rota.
Third-party messaging
Using an existing messaging protocol reduces build time but inherits its trust model and fees.
Cross-Chain & Bridge Development questions
A token bridge moves value by locking or burning on one chain and unlocking or minting on another. Cross-chain messaging transports arbitrary data and contract calls, of which token transfers are one use. We build both, and token bridges are usually implemented on top of a messaging layer.
Connecting chains or building a bridge?
Describe the chains, assets and trust requirements. We will propose a security model, architecture and phased rollout.