Security

How Bridgeless keeps your assets safe across chains.

Security Model

ASSET CUSTODY

Your funds sit in chain-native contracts or TSS-controlled addresses, not in a custodial wallet. Contract upgrades go through on-chain governance voting.

DEPOSIT VALIDATION

Every deposit is verified directly against the source chain before processing. Each chain has its own confirmation threshold based on finality time, so nothing moves until the deposit is fully settled.

WITHDRAWAL SIGNING

Withdrawals require a threshold of validators to co-sign before any funds move. Each chain runs its own isolated signing sessions, and replay attacks are blocked by tracking transaction hashes and nonces.

NETWORK SECURITY

Secret shares are isolated per validator and can be reshared when the validator set changes, without ever exposing the private key. Session IDs are unique per round, preventing cross-session replay.

Proven Guarantees

An independent academic team formally proved that the Bridgeless protocol satisfies both safety and liveness under Byzantine conditions.

Safety

Every withdrawal on the target chain corresponds to a verified deposit on the source chain. Funds cannot be created, duplicated, or redirected.

Formally proven

Liveness

Every valid deposit will eventually be processed and settled on the target chain. Transactions cannot be censored or stalled indefinitely.

Formally proven

Security Audit

Independent Academic Review

Formalization and Security Analysis of the Bridgeless Protocol

Orestis Alpos, Oleg Fomenko, Dimitris Karakostas, Oleksandr Kurbatov, Andrey Sabelnikov

Whitepaper Read audit

Bug Bounty

Coming Soon

Bug Bounty Program

A public bug bounty program for security researchers is in preparation. Details on scope, severity tiers, and rewards will be announced soon.