A request appears in the wallet. Explain exactly what is being authorised.
Design a signature journey that presents the message, domain, account and expected consequence before requesting consent.
The wallet displays a readable request that the user may approve or reject; a signature is not necessarily a network transaction.
Read before signing. Reject without losing the journey.
A signature expresses agreement to specific content; it is not automatically a transaction and must not be presented as one.
For products using proof of control, consent or a signed authorisation.
A visible account. An explained request.
Present the content
Show a human explanation, the requested account and the technical information needed for verification.
Collect consent
Open the wallet after a deliberate action and distinguish pending, rejection and completed signature.
Verify the proof
Check message, domain, freshness, nonce and address on the server before granting the next step.
The journey. And the guidance to control it.
- 01
Consent journey and message format
- 02
Signature verification for the agreed use case
- 03
Rejection, expiry and replay cases with documentation
A signature replaces neither business authorisation, contract audit nor confirmed transaction; no private key is collected.
Your contracts set the context.
Verified networks, addresses and ABI, target wallets, test accounts and business rules define the authorised starting point.
- 01
Map
Wallets, networks, contracts, sources and actors.
- 02
Explain
The request, consent, rejection and possible states.
- 03
Verify
Signatures, reads and confirmations against agreed criteria.
- 04
Hand over
Scenarios, limits, sources and recovery instructions.
A journey to replay. States to recognise.
Agreed cases are replayed with test accounts and networks. Connection, rejection, signature, error and confirmation remain distinct, without equating a connected wallet with authenticated identity.
Useful questions.
What is the difference between a signature and a transaction?+
A signature approves a defined message or authorisation. A transaction targets a network change, with its own fees, statuses and confirmation.
What do you need from us to start?+
We begin with verified addresses and ABI, target networks, business rules, test accounts and authorised access. Missing items are recorded before integration.
How do we limit confusing requests?+
We keep the first scope to named actions, explain them before the wallet, show their states and provide recovery for rejection or error.
Every authorisation deserves a readable context.
Describe the expected action, network, verified contracts and states the user must recognise.
Describe my Web3 need