Filecoin Docs
BasicsStorage providersNodesNetworksSmart contractsReference
  • Welcome to Filecoin Docs
  • Basics
    • What is Filecoin
      • Crypto-economics
      • Blockchain
      • Storage model
      • Storage market
      • Retrieval market
      • Programming on Filecoin
      • Networks
    • The blockchain
      • Actors
      • Addresses
      • Blocks and tipsets
      • Consensus
      • Drand
      • Proofs
    • Assets
      • The FIL token
      • Wallets
      • Metamask setup
      • Get FIL
      • Transfer FIL
    • Interplanetary consensus
    • How storage works
      • Filecoin plus
      • Storage onramps
      • Filecoin and IPFS
    • How retrieval works
      • Basic retrieval
      • Serving retrievals
      • Saturn
    • Project and community
      • Forums and FIPs
      • Filecoin compared to
      • Filecoin FAQs
      • Related projects
      • Social media
      • The Filecoin project
      • Ways to contribute
  • Storage providers
    • Basics
      • Quickstart guide
    • Filecoin economics
      • Storage proving
      • FIL collateral
      • Block rewards
      • Slashing
      • Committed capacity
    • Filecoin deals
      • Storage deals
      • Verified deals
      • Filecoin programs and tools
      • Snap deals
      • Charging for data
      • Auxiliary services
      • Return-on-investment
    • Architecture
      • Software components
      • Storage provider automation
      • Sealing pipeline
      • Sealing rate
      • Sealing-as-a-service
      • Network indexer
    • Infrastructure
      • Storage
      • Network
      • Backup and disaster recovery
      • Reference architectures
    • Skills
      • Linux
      • Network
      • Security
      • Storage
      • Sales
      • Industry
    • PDP
      • Prerequisites
      • Install & Run Lotus
      • Install & Run YugabyteDB
      • Install & Run Curio
      • Enable PDP
      • Use PDP
  • Nodes
    • Implementations
      • Lotus
      • Venus
    • Full-nodes
      • Pre-requisites
      • Basic setup
      • Node providers
    • Lite-nodes
      • Spin up a lite-node
  • Smart contracts
    • Fundamentals
      • The Filecoin Virtual Machine
      • Filecoin EVM runtime
      • ERC-20 quickstart
      • Roadmap
      • Support
      • FAQs
    • Filecoin EVM-runtime
      • Actor types
      • Address types
      • FILForwarder
      • Difference with Ethereum
      • How gas works
      • Precompiles
    • Programmatic storage
      • Aggregated deal-making
      • Direct deal-making
      • Cross-Chain Data Bridge(CCDB)
      • Data replication, renewal and repair (RaaS)
      • RaaS interfaces
    • Developing contracts
      • Get test tokens
      • Remix
      • Hardhat
      • Foundry
      • Solidity libraries
      • Call built-in actors
      • Filecoin.sol
      • Direct deal-making with Client contract
      • Using RaaS
      • Verify a contract
      • Best practices
    • Advanced
      • Wrapped FIL
      • Oracles
      • Multicall
      • Multisig
      • FEVM Indexers
      • Cross-chain bridges
      • Aggregated deal-making
      • Contract automation
      • Relay
  • Networks
    • Mainnet
      • Explorers
      • RPCs
      • Network performance
    • Calibration
      • Explorers
      • RPCs
    • Local testnet
      • Get test tokens
    • Deprecated networks
  • Reference
    • General
      • Glossary
      • Specifications
      • Tools
    • Exchanges
      • Exchange integration
    • Built-in actors
      • Protocol API
      • Filecoin.sol
    • JSON-RPC
      • Auth
      • Chain
      • Client
      • Create
      • Eth
      • Gas
      • I
      • Log
      • Market
      • Miner
      • Mpool
      • Msig
      • Net
      • Node
      • Paych
      • Raft
      • Start
      • State
      • Sync
      • Wallet
      • Web3
  • Builder Cookbook
    • Overview
    • Table of Contents
    • Data Storage
      • Store Data
      • Retrieve Data
      • Privacy & Access Control
    • dApps
      • Chain-Data Query
      • Oracles
      • Cross-Chain Bridges
      • Decentralized Database
Powered by GitBook
LogoLogo

Basics

  • Overview
  • Crypto-economics
  • Storage model
  • Reference

Developers

  • The FVM
  • EVM-runtime
  • Quickstart
  • Transfer FIL

Contact

  • GitHub
  • Slack
  • Twitter
On this page
  • Available multisig wallet implementations
  • Filecoin Native Multisig
  • Safe multisig

Was this helpful?

Edit on GitHub
Export as PDF
  1. Smart contracts
  2. Advanced

Multisig

Multisig wallets enhance security and decentralization by requiring multiple signatures for transactions, distributing control among multiple participants.

PreviousMulticallNextFEVM Indexers

Last updated 1 month ago

Was this helpful?

In the Filecoin network, multisig wallets allow multiple parties to jointly manage a wallet by requiring a predefined number of signatures (approvals) for a transaction to be executed. This enhances security and decentralization by distributing control among multiple participants.

Multisig wallets are an essential component of many blockchain applications, as they enable collaborative management of funds and application state. Users initiate a transaction to be signed by fellow collaborators. Once the required number of approvals is met, the transaction is executed.

Multisig wallets enable builders to integrate the following features into their projects:

  • Decentralized Governance: Parties asynchronously approve transactions initiated by its members.

  • Security: Distributing control among multiple participants ensures that no single party has full control over the wallet.

  • Collaborative fund management: Multiple parties can jointly manage a wallet by requiring a predefined number of signatures (approvals) for a transaction to be executed.

Available multisig wallet implementations

There are several multisig wallet implementations on Filecoin. Builders can integrate these multisig wallets into their applications today.

Filecoin Native Multisig

The Filecoin Native is a built-in actor that does not interact directly with the Filecoin EVM. Like other Filecoin actors, native multisig addresses begin with f2 and represent a group of transaction signers with a maximum of 256 signers. Signers may be external users or the MultisigActor itself and can include f1 and f3 .

Filecoin Native Multisig UIs

  • is a non-custodial web UI for the Filecoin Native Multisig wallet

  • can also be used and is available from the Lotus CLI

Safe multisig

is a popular smart EVM multisig account infrastructure provider that allows users to manage their digital assets securely and can be used with many popular EVM wallets. It is non-custodial, formally verified, secures over $100B in assets, and is used by more than 200 projects. Safe has been deployed to the Filecoin EVM.

Safe UI

A web UI for the Safe multisig on Filecoin is available at:

Safe Troubleshooting

  • Signing a transaction from an account with no previous activity on the Filecoin blockchain will fail. You can send a transaction to this account with zero funds to initiate its on-chain activity to work around this issue.

  • Executing a transaction can produce gas estimation issues for accounts that have a very small amount of funds (that would not or would barely cover the transaction).

  • Transaction confirmation times may lead to prolonged "processing" status in the UI.

  • Safe addresses from other networks can sometimes be used but require additional technical steps.

    • Confirm complete creation (not just as a Placeholder) of the Safe multisig as an EVM contract on Filecoin prior to sending major funds.

    • If the previous address and chain use the L1 implementation of Safe Proxy, more complex technical migration steps will be required to map to the L2 version on Filecoin. Contact Safe-related support for more info.

  • Safe-related support can be found in the "Need Help?" section of the Safe web UI.

Safe Transaction Service

  • Note:

Safe Smart Contracts

Safe’s multisig smart contracts are live on the Filecoin Mainnet and Calibration testnet.

Name
Address
Mainnet
Calibration

0x3d4BA2E0884aa488718476ca2FB8Efc291A46199

✔️

✔️

0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67

✔️

✔️

0xeDCF620325E82e3B9836eaaeFdc4283E99Dd7562

✔️

✔️

0xfd0732Dc9E303f09fCEf3a7388Ad10A83459Ec99

✔️

✔️

0x9b35Af71d77eaf8d7e40252370304687390A1A52

✔️

✔️

0x38869bf66a61cF6bDB996A6aE40D5853Fd43B526

✔️

✔️

0x9641d764fc13c8B624c04430C7356C1C7C8102e2

✔️

✔️

0xd53cd0aB83D845Ac265BE939c57F53AD838012c9

✔️

✔️

0x29fcB43b46531BcA003ddC8FCB67FFE91900C762

✔️

✔️

0x41675C099F32341bf84BFc5382aF534df5C7461a

✔️

✔️

Further Safe resources

- the default network is set to

FilecoinSafeUI

In some cases the same Safe address and owner structure is not possible, learn more in .

Instructions for deploying a Safe at the same address on another chain are available in . Note that a compatible version of the Safe Proxy on the original chain must exist on Filecoin. Contact Safe-related support for help.

The on Filecoin is available at:

on

on

Faster finality is coming to Filecoin soon. For now, the Filecoin Safe transaction service sets ETH_REORG_BLOCKS to 60 blocks (i.e. Filecoin epochs) (30min) based on but users may want to wait 900 epochs (~7.5h) for full finality.

MultisigActor
addresses
Glif Multisig
MultisigActor CLI
Safe
https://safe.filecoin.io
Filecoin Mainnet
this article
this video
Safe transaction service
https://transaction.safe.filecoin.io
Filecoin Mainnet
https://transaction-testnet.safe.filecoin.io
Filecoin Calibration testnet
FRC-0089
Safe Docs
Was this page helpful?
SimulateTxAccessor
SafeProxyFactory
TokenCallbackHandler
CompatibilityFallbackHandler
CreateCall
MultiSend
MultiSendCallOnly
SignMessageLib
SafeL2
Safe