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. Developers
  2. Integrate with MSafe (DAPP)

FAQ

PreviousIntegrate with MSafe (DAPP)NextMove Module Publish

Last updated 2 years ago

Why my application cannot detect MSafe environment / `MSafeWallet.inMSafeWallet` returns false?

MSafe wallet itself is a web application. You need to open your application within the MSafe App store. For example for partner endpoint, you may replace ${YOUR_URL} in the following link to access your application on Testnet.

https://testnet.m-safe.io/apps/0?url=${YOUR_URL}

Upon connecting the MSafe wallet, why application is redirected to MSafe?

To interact with MSafe wallet, application need to talk to the MSafe application in the parent frame. So MSafe wallet adapter will automatically redirect to the MSafe application page if MSafe environment is not detected. This is an automatic bahavior as expected.

Why my application cannot connect to MSafe wallet?

  1. Make sure you are using the latest MSafe wallet code, and follow the instructions using or .

  2. You are opening your application within the MSafe application. E.g. https://testnet.m-safe.io/apps/0?url=${YOUR_URL}.

  3. You have created at least one MSafe wallet.

Why my UI interface does not show up on MSafe page?

Please check whether you have created at least one MSafe wallet. We will add more prompt for better user experience later.

How to tell whether my application works with MSafe?

  1. Open your application in MSafe app store with your application's URL. (E.g. )

  2. Connect your wallet, and wallet is connected to MSafe address.

  3. Submit a transaction within your application, the transaction displays in the transaction queue page.

  4. After enough signatures are collected, the transaction is submitted on chain.

  5. If you have created multiple MSafe wallets, switching the address will result in connected wallet address change in your application. Please see for details.

Why `signAndSubmit` does not resolve the promise?

In multi-sig use case, signAndSubmit is the wallet manager submitting the transaction proposal for MSafe wallet. The transaction with the application's logic can only be executed after collecting enough signatures from the MSafe managers, which will take days to finish. Thus, in the current implementation, signAndSubmit transaction will not be resolved.

Is there any improvements for better user experience?

Yes.

We suggest automatically detect and connect MSafe wallet so that user does not need to connect wallet and select MSafe manually.

Please check out for example.

MSafe SDK
Aptos-wallet-adapter
https://testnet.m-safe.io/apps/0?url=${YOUR_URL}
onAccountChange
https://app.m-safe.io/apps/Tortuga