br-verify

1. Payload from DETAILS

In the Authorization App, open the request, go to DETAILS, copy the whole payload, and paste it here.

Nothing pasted yet.

From the Linear ticket. Leave a box empty if you don't have the value: it is then listed as "not compared".

Paste expected JSON (expected fields, metaData or a bundle)

Chain ID Nonce

To Not entered Contract creation Address

Value (wei) Gas limit Max fee per gas (wei) Max priority fee per gas (wei) Access list

Default: empty. The signing flow never sets an access list, so a payload with one gives MISMATCH.

Data Init-code hash, keccak256(data) Function signature Arguments (a JSON list, or one per line) Data, as hex

Not part of the payload From (the sending key's address)

As entered, not part of the payload: check that the key named in DETAILS (signKeyName) has this address.

Expected contract address (creations)

Waiting for a payload

For chain ID 1: the fork isn't reachable from a phone. Compare the nonce with the pre-flight posted on the ticket.

br-verify sends nothing unless you type an RPC URL and press the button. It then sends three read-only requests to that URL.

RPC URL