Blockchain Tools 0.30.1 / Security
Blockchain Tools security and privacy
Understand the controls separating public reads, simulation, confirmation, and wallet signing.
Public reads and transaction writes have separate authority. A successful lookup, approved contract, or callable schema does not authorize sending.
Guarded writes require Pro, the administrator switch, exact capability, supported adapter, trusted identity, simulation, immutable preview, explicit confirmation, current account and chain, idempotency protection, and the provider wallet prompt.
Tools never requests a private key or seed phrase. Safe status output omits RPC credentials, complete wallet addresses, calldata, raw provider errors, and receipt payloads. Use Core’s opt-in redacted journal for cross-session status rather than creating a second transaction log.
Protected builds are immutable signed releases. The version, folder, byte size, and SHA-256 digest must match the authority record. Changed bytes require a new version; an earlier signed release must never be overwritten.