Mimir
  • Product Introduction
    • 💡Mimir Introduction
    • 💰Multisig Introduction
    • Proxy Introduction
  • 🪢Omni UX
    • 🔙Switch to Solo mode
    • 💬Address Format And Identity
  • Basic
    • 💳Accounts
      • Advanced - Nested Multisig
      • Advanced - Time Delayed Proxy
    • 📍Dapps
    • 🏧Transaction
  • Advanced
    • 👀Watchlist
    • 💼Batch
    • 🗣️Proposer
    • Call Template
    • 🏛️Multi-Sig Governance in Polkadot
    • 💹Participate Polkadot Native Staking
  • 📶Customize RPC
  • Step by step
    • 🟢Create Multisig
      • Create Nested Multisig
    • 🟢Create Proxy
      • Create Pure Proxy
    • 📥Import Multisig
    • 🛠️Initiate Transactions
    • ⚖️Manage Transactions
      • ⏳Manage Delayed Proxy Transactions
  • Safety
    • 🔍Call Data Verification
    • 🚛Transaction Simulation
  • 🛠️Developer
    • Batch API
    • 🖥️Mimir SDK
      • PolkadotJS App
      • Polkadot API(PAPI)
      • ReactiveDOT/DOTConnect
  • FAQs
    • ❓FAQs
Powered by GitBook
On this page
  1. Safety

Call Data Verification

PreviousManage Delayed Proxy TransactionsNextTransaction Simulation

Last updated 2 months ago

Polkadot & parachains use Polkadot-SDK, ensuring all transactions have on-chain metadata—no unreadable 0xbytes. If you don’t fully trust calldata during execution, Mimir also provides additional verification tools to help you ensure transaction security.

Click View Detail next to Call Data to open a detailed view displaying the full Call Data JSON file.

You can compare all parameters, method names, and other details to ensure they match the expected transaction. If anything is incorrect or unexpected, DO NOT approve the transaction.

🔍