03 / Signing authority6 min read

Review authority before action

A decision framework for checking transaction scope before a configured signing flow is used.

Reading outcome

After this guide, you can:

Distinguish preparation from approval
Review the full effect of an action
Keep signing authority with the operator

01 / Boundary

Know where authority begins

An interface can prepare an action, but authority comes from the configured signing method. Operators should be able to identify the exact moment when a proposal becomes an authorized transaction.

Keep private keys and signing decisions in the operator-controlled flow. A non-custodial workflow is strongest when the boundary is not only technically present, but also obvious to the person reviewing the action.

02 / Effect

Review effect, not just intent

A familiar button label is not enough evidence. Confirm the network, source wallet, destination, token, amount, fees and any permissions the action may grant.

Read the action from the perspective of its on-chain effect. If the displayed summary does not make that effect clear, do not compensate with guesswork.

Operator check

The active network matches the plan
Source and destination are expected
Token, amount and limits are correct
Fees and permissions are understood

03 / Sign

Make deliberate signing the fastest safe path

Operational speed comes from preparation, not from removing review. Pre-label wallets, agree limits and define approval roles so the final decision can be both quick and informed.

If the live context differs from the prepared context, return to review. A small delay is cheaper than authorizing an action whose scope is no longer understood.

Next guide

04 / Launch planningWrite a launch-day runbook