FUSHUMA BRIDGE

Security Model

A Cross-chain bridge allows users to move assets from one chain to another. It consists of a set of smart contracts on two different chains. One contract receives an asset on the origin chain, freezes it, and emits a signal for the second contract on the destination chain to create the same quantity of ‘wrapped’ tokens.

Fushuma Square Logo 180px

WHY SECURITY MATTERS?

Since smart contracts cannot communicate across chains, Fushuma bridge uses an independent network to relay the event from one chain to the other.

In this system, security is critical. If an attacker managed to gain control of the relay, they could mint unlimited tokens. Fushuma bridge prevents that risk with three safeguards:

  • Bridge authorities are given only minimal trust.

  • Owner actions are delayed by a waiting period.

  • Implementation of an emergency freeze switch.

Roles & Permissions

Authority Signers

  • At least 3 signatures are required for any transfer.
  • A designated ‘required authority’ must co‑sign every transfer.
  • Every authority can freeze the bridge at any time if a misbehaviour is detected.
  • Authorities have no extra privileges beyond ‘relay‘ and ‘freeze‘.

Owner Permissions

A special account is granted ‘Owner‘ permissions to debug the contract or punish malfunctioning authorities in the event of misbehavior.

A 4-wallet multisig controled by the Fushuma founders manage critical actions. Below is the list of the actions possible (any change needs a majority):

  • Unfreeze contracts after an incident.
  • Add or remove authorities and update the signature threshold.
  • Set the fee receiver address and the single required authority.
  • Exit setup mode once maintenance is complete.

Founders Multisig

A separate 4-wallet multisig can replace the ‘Owner multisig if the primary keys are compromised. Founders keys remain offline.

THREE Smart Contracts Modes

The Fushuma bridge smart contract system operates in three different modes:

1 · Setup Mode

Owner‘ can enable maintenance functions after a 24‑hour delay. The delay gives the community time to review the intent.

2 · Upgrading Mode

An upgrade request triggers a 72‑hour waiting period before the bridge migrates to the new contract.

3 · Frozen Mode

Any authority with a freeze key can halt swaps when an anomaly appears. Only ‘Owner‘ can resume normal operation.