BNB Chain Safe Multi-Sig Wallet ServiceBNB Chain deployed a multi-sig wallet service based on the Gnosis Safe protocol on both BSC and opBNB. It provides users with a secure and convenient way to manage their digital assets and transactions.How to Use the BNB Chain Multi-Sig Wallet ServiceTo use the BNB Chain multi-sig wallet service, users will first need to create a Safe. This can be done by visiting the following link:https://safe.bnbchain.org/new-safe/createWhat is Safe?Everything you need to know to start building on Safe.​ brings digital ownership of accounts to everyone by building universal and open contract standards for the custody of digital assets, data, and identity.Safe is at the forefront of modular smart account infrastructure, paving the way for developers to create various applications and wallets.Safe{Core} consists of three components:Safe{Core} ProtocolThe is an open, modular framework to make smart accounts secure, portable, and composable.This section in the documentation has information and relevant links about the Safe{Core} Protocol and the different elements involved.Safe{Core} AA SDKThe is a set of developer kits that help integrate Safe with different external service providers. The SDK offers developers the ability to abstract the complexity that comes with operating a smart contract account.This section in the documentation has relevant information and tutorials on the SDK kits and how to integrate them.Safe{Core} APIThe makes reference to all the Safe infrastructure needed to power interfaces with all Safe account related information. This includes the Safe Transaction Service, Safe Events Service, etc.This section in the documentation has information related to the services architecture.The vision for Safe Smart Accounts is to become the standard core used in all smart contract-based wallets. It also aims to make the benefits of Account Abstraction accessible to users and developers.The architectural design of Safe Smart Account keeps the following principles in mind:Secure defaultUses a multi-signature logic where a threshold of owners must confirm a transaction before execution to provide a secure default without trusting any additional contract. For example, a module, guard, or fallback handler (explained below).Minimal gas costsOptimises gas costs by storing the transaction data that should be executed and the confirmations off-chain.Uses a proxy pattern to reduce setup costs.Maximum flexibilitySupport Modules are contracts that can use alternative access patterns (instead of multi-signature) to execute transactions.Supports the delegatecall function, which introduces complex execution logic by loading instructions from other contracts and executing via a Safe Smart Account.Here are some core components of a Safe Smart Account that you will learn about:Safe ModulesSafe Modules are smart contracts that extend Safe's functionality with added custom features while the module logic remains separate from Safe's core contracts.Safe GuardsSafe Guards make checks before and after a Safe transaction.SignaturesSafe contracts support alternative signature schemes such as EIP-1271 and EIP-712 and relaying by making the confirmation/verification logic independent of msg.sender.$BNB #safe