Symbiosis Documentation
Symbiosis NestDeveloper ToolsGo to Bridge & Swap
  • Getting Started with Symbiosis
  • Symbiosis: Frequently Asked Questions
  • Main concepts
    • Glossary
    • Symbiosis SIS Token
    • Symbiosis sTokens
    • Symbiosis: Cross-Chain Swaps
      • Symbiosis: To/From BTC
      • Symbiosis: To/From TON
    • Cross-Chain Zaps
    • Symbiosis as Interchain Communication Protocol
    • Symbiosis & Fees
    • Security Audits
    • Bug Bounty Program
  • Governance
    • 🚩Governing Symbiosis
  • User Guide (WebApp)
    • Symbiosis WebApp
    • Bridge with Symbiosis: sUSDC, sWETH, sWBTC
    • Swap & Bridge with Symbiosis
    • Swap & Bridge To and From Bitcoin
    • Swap & Bridge To and From Tron
    • Stuck Transactions
    • Bridging SIS Token
    • Symbiosis Liquidity Pools
    • Withdrawing from Symbiosis Octopool
    • Cross-Chain Zaps
    • Common Issues and Solutions
    • Where are My Tokens?
    • Symbiosis Explorer
    • More about Slippage Tolerance
  • Reward Programs
    • Symbiosis Reward Programs
    • Farming on Octopools
    • SIS LP Farming
    • veSIS
  • Cross-chain liquidity engine
    • Symbiosis Core Smart Contracts
    • Symbiosis Mint-Burn Process
    • Symbiosis BridgeV2 Contract
    • Symbiosis Routing Contracts
    • Symbiosis & Emergencies
    • Symbiosis Octopools
  • Relayers network
    • Symbiosis Relayers Network
    • Symbiosis PoS Staking & Symbiotic Staking
      • Symbiosis X Symbiotic: SIS Restaking Vault User Guide
    • Relayers Network: Architecture and Operations
    • Symbiosis Relayer Node
    • Symbiosis Relayers Network: Emergencies
  • Developer Tools
    • Symbiosis Developer Tools
    • Symbiosis API
    • Symbiosis JS SDK
      • JS SDK Types
      • JS SDK Configuration
  • Miscellaneous
    • Symbiosis on Testnet
    • Symbiosis Multisig Address on Scroll
    • Symbiosis v1 vs. v2
    • Gasless Crypto Exchanges
  • Follow Us
  • Symbiosis | X
  • Symbiosis | Telegram
  • Symbiosis | Blog
  • Symbiosis | Publish0x
  • Symbiosis | Discord
  • Symbiosis | Linkedin
  • Symbiosis | Github
Powered by GitBook
On this page
  • MPC Group Inefficiency
  • Epoch Change Failure
  • New MPC group formation failure
  • Epoch change failure in the Staking contract
  • MPC address change failure in the BridgeV2 contract(s)

Was this helpful?

  1. Relayers network

Symbiosis Relayers Network: Emergencies

Symbiosis Relayers Network: Detection and resolution of operational failures.

MPC Group Inefficiency

Q
A

What does it look like?

The relayers network stops to proceed oracle requests for all blockchains.

How do we notice it?

Alerts

What may be a cause?

  • There are not enough relayers to compose TSS signatures.

  • The leader of the MPC group is offline.

How do we solve this?

  1. Ban offline relayers in the Staking contract,

  2. Initiate epoch change.

Epoch Change Failure

Once epoch change is triggered, the following stages should be completed:

  1. Epoch change preparation. This stage includes:

    1. Formation of a new MPC group,

    2. Generation of a new MPC key,

    3. Approval of the epoch change by holders of 2/3 of the total stake.

  2. Epoch change in the Staking contract.

  3. Epoch change in BridgeV2 contracts.

On each stage an emergency can happen.

New MPC group formation failure

Q
A

What does it look like?

Relayers cannot generate a new MPC key.

What may be a cause?

  • Many relayers are offline, and the rest are not enough to form a new MPC group.

  • The leader of the MPC group is offline.

How do we solve this?

  1. Ban offline relayers in the Staking contract,

  2. Set the MPC group size to a smaller value,

  3. Initiate epoch change one more time.

Epoch change failure in the Staking contract

Q
A

What does it look like?

Relayers cannot save a new MPC address in the Staking contract.

What may be a cause?

Many relayers are offline, and the rest cannot provide enough signatures for epoch change.

How do we solve this?

Save the new MPC address manually.

MPC address change failure in the BridgeV2 contract(s)

Q
A

What does it look like?

The relayers network does not proceed oracle requests for a particular blockchain.

How do we notice it?

Alerts

What may be a cause?

There are not enough relayers to compose a proper TSS signature to change the MPC address.

How do we solve this?

Replace the MPC address with a new one manually.

PreviousSymbiosis Relayer NodeNextSymbiosis Developer Tools

Last updated 4 months ago

Was this helpful?