Frequently asked questions

Is it free?

Yes. The current product has no account, sign-up, or paywall.

Do I connect a wallet?

No. The application does not include a wallet connector and never requests signing keys.

Does it store Safe data?

Configuration snapshots are stored locally in browser IndexedDB for drift comparison. The application has no report database. Network requests still occur for RPC reads and optional or import features described in the security model.

Does a matching hash mean it is safe to sign?

No. It confirms that the reviewed transaction fingerprint matches the signing fingerprint. You must also verify that every decoded action is authorized and intended.

Does a clean Safe report prove the Safe is secure?

No. It reports known configuration risks. It cannot know whether owners are the right people, whether keys are stored safely, or whether governance procedures are being followed.

Which networks are supported?

Eight mainnets and two testnets are currently configured. See Networks and privacy for the exact list. Arbitrary custom RPC networks are not currently supported by the UI.

Can I inspect a transaction before it is proposed?

Yes. Use Transaction Builder JSON or Manual Input. An unproposed local draft cannot be discovered from a Safe address.

Can I export results?

Safe Inspector exports final reports as Markdown and JSON. Transaction Inspector provides its own analysis export from the result view where available.

How is this different from the Safe interface?

It is a separate, read-only review surface. It focuses on direct configuration reads, independent transaction decoding and hash recomputation, local risk analysis, and an explicit human comparison before signing.

When is a full audit appropriate?

Use a full audit when you need transaction-history review, operational-control assessment, signer key-management review, governance analysis, or a signed professional report. The product includes a contact path to QuillAudits for this broader scope.

How do I verify a SafeTxHash before signing?

Paste the Safe transaction hash into Transaction Inspector. The tool loads the raw transaction, recomputes the SafeTxHash from the to/value/data/operation, safeTxGas, gasPrice, gasToken, refundReceiver, nonce, and signatures, and shows it next to the decoded calldata. Compare that value with the hash shown on your signing device or the official Safe app. If they match, the transaction you are about to sign is the one you reviewed.

What is configuration drift in a Safe?

Configuration drift is any change in a multisig’s on-chain state that weakens security or departs from the originally intended policy: owners added or removed, threshold lowered, an unexpected module enabled, or the singleton/guard/fallback handler swapped to an unaudited implementation. Safe Inspector records snapshots in IndexedDB and highlights drift between scans.

Can a Safe module drain funds without owner signatures?

Yes. A module is allowed to execute transactions against the Safe without reaching the owner threshold. If a module is malicious, compromised, or buggy, it can move assets or change state. Safe Inspector lists every enabled module and its address so signers can verify whether it is expected.

Does Multisig Inspector need my private key or a wallet connection?

No. The tool is read-only and does not request private keys, seed phrases, or a wallet connection. It reads data from public RPC endpoints and decodes transaction data locally.

Is my Safe address sent to any server?

No QuillAudits server records the addresses you scan. Queries are sent to the public RPC or Safe Transaction Service provider you select; those providers may log traffic under their own privacy policies. Configuration snapshots are stored locally in your browser.