MSafe | Aptos
  • Overview
    • MSafe Overview
    • What can you do with MSafe wallet?
      • Why Multi-Sig & Non-Custodial
      • MSafe Wallet Key Benefits
    • Use Cases
      • Treasury Management
      • Smart Contract Deployment & Update
      • Protocol Admin Control
      • dApp Store Integration
    • Security
  • Users
    • Glossary
    • Launch App
    • Connect Wallet
    • Navigation Bar
    • Address Book
    • Create an Account
      • Initiate Creation
      • Co-Managers to Accept
    • Switch btw Accounts
    • Deposit / Receive
    • View Assets
    • View Pending Txn
    • View Txn History
    • Propose Transaction (Enable NFT, Send, Register Coin)
      • Enable NFT
      • Send
      • Add Coin
    • Approve Transaction
      • Co-Managers to Approve Enable NFT
      • Co-Managers to Approve Send
      • Co-Manager to Approve Add Coin
    • Change Vote
    • Reject Transaction
      • Co-Managers to Reject
    • Execute Transaction
      • Execute Approval
      • Execute Rejection
    • App Store
      • Use dApps
    • MSafe 1.0 User guide
      • Connect Wallet
      • First time registration
      • Create an MSafe Account
      • Receive Coin
      • Coin Transfer (APT)
      • DAPP Store
      • Add a new coin
      • Address Book
      • Permissions
      • Wallet FAQs
  • Developers
    • Overview
    • System
      • Auth-key & Multi-Ed25519
      • Backend Walk Through
      • MSafe Contracts
    • Interactive CLI
      • Installation
      • CLI arguments
      • Register and View
      • Create a MSafe Wallet
      • Approve / execute a transaction
      • Transfer Coin
      • Smart Contract | Module Publish
      • Entry Function
      • Reject a transaction
      • Migration from MSafe 1.0 to MSafe 2.0
    • SDK
      • Smart Contract | Deploy a MOVE Module
      • Call An Entry Function
    • Integrate with MSafe (DAPP)
      • FAQ
    • Move Module Publish
  • Product updates
    • 2022 Q4
Powered by GitBook
On this page
  1. Overview
  2. Use Cases

Smart Contract Deployment & Update

PreviousTreasury ManagementNextProtocol Admin Control

Last updated 2 years ago

By leveraging MSafe’s full on-chain interoperability, developers can use MSafe Wallet as the contract deployer or admin role to decentralize the ownership of the protocol.

MOVE Module Publishing

First of all, the Aptos MOVE module is totally different from an Ethereum account model. The deployer address will always have the permission to upgrade the smart contract to an arbitrary logic. Thus it is very important to have a multi-sig wallet like MSafe Wallet to deploy the smart contract, so that there will be multiple people, who own the permission, responsible for the Move module upgrade. This will decrease the risk of rug pulls by the project developer.

How to deploy smart contract with MSafe multi-sig developer tools:

  • (Recommended) Publish a Move module with script: Smart Contract | Deploy a MOVE Module.

  • Publish a Move module with interactive CLI tool: Smart Contract | Module Publish.