Glossary
Signing a transaction is the moment your private key approves a transfer or contract call. It is irreversible once broadcast, which is why reading what you sign matters more than the wallet you sign it on.
Transaction signing is the cryptographic act of using your private key to approve exactly one transfer or contract call. The signature is unique to that transaction: change the recipient, the amount, or the data, and the signature no longer matches. The network verifies the signature without ever seeing the private key, which is the asymmetry that makes public-key cryptography work. Once a signed transaction is broadcast, it is irreversible - there is no recall function and no support queue that can unwind it.
Signing covers more than sends. A contract call is a signature too, and its data field encodes what the contract will do with your funds - swap tokens, mint an NFT, or grant an ongoing allowance. Modern standards such as EIP-712 render those messages in human-readable structure, so the request can be read rather than squinted at. The gap between what a request claims and what its data field does is where most signature-based losses live.
Blind signing is the failure mode: approving a request you have not read, on any wallet, at any price point. Hardware wallets help because their screens show the actual request, which makes the device the source of truth rather than the website. The habit that matters is reading the full request every time, including contract calls, not just the amount.
A signing request arrives with the transaction's full contents: the sending address, the recipient, the amount, the fee, and any data. Your wallet passes those contents to your private key, which produces a signature unique to them. The signature is appended to the transaction and broadcast to the network. Every node verifies the signature against the transaction's contents in microseconds, and the transaction is mined into a block.
On a hardware wallet, the flow includes a screen. The device displays the actual request, and you compare it with what the website or app claims before approving; the screen is the source of truth because it reads from the key itself. A malicious front-end can display one request while constructing another, and the hardware screen is where the discrepancy becomes visible. This is why hardware wallets are recommended for anything beyond small spending balances, and why the screen should be read every time.
Contract calls are where the stakes rise. The data field encodes the function being called and its parameters, and drainer kits are off-the-shelf scam software that presents a benign surface - 'Claim reward', 'Free mint' - with a hostile data field granting token allowances underneath. EIP-712 structured signing exists to close that gap by rendering the request in readable fields: what site, what action, what parameters. Reading the full request takes ten seconds and defeats most of the scam class.
Signing is the only moment in crypto where your consent is the product, and it is the last checkpoint before an irreversible action. The private key entry covers the key that produces the signature; this entry covers the moment it is used. Once broadcast, the transaction is on the chain, and the chain does not do refunds.
A colleague named Brent (yes, that Brent) signed a 'free mint' request from a link in a group chat, which turned out to contain a token approval granting a contract access to his funds. The mint was free; the approval was the product, and the token approval scam entry covers what happened next. He had read the title, approved on the website's word, and skipped the device screen where the actual request was printed.
The highest-leverage thing most Australians can do is read every signing request in full and treat the hardware wallet's screen as the source of truth. The phishing entry covers the fake front-ends that produce hostile requests. Ten seconds of reading is the entire defence, and it scales to every wallet and every price point.
You send 0.05 BTC to a friend, and the signing request lists the recipient, the amount, and the network fee. Your private key produces a signature unique to those exact contents, and the signed transaction is broadcast. Every node verifies the signature in microseconds, and the transaction is mined into a block within the hour. The fee shown is the fee paid; the recipient shown is the recipient paid. The signature approved one transfer, once, forever - which is the point.
A website titled 'Claim your reward' asks for one signature, and the front-end describes it as a free mint. The actual request's data field calls approve, granting a contract permission to move your tokens without limit. Brent approved on the website's word alone, and the hardware screen showing the true request went unread. The reward never arrived; the allowance did, and the drain came later. The request would have been visible on any hardware wallet screen, and readable in the wallet app's details panel - the ten seconds he skipped was the entire security model.
A structured signing request renders the message in plain fields: the site's name, the action being taken, and the parameters. Reading it takes ten seconds, and the discrepancy between the described action and the actual fields is immediately visible. Drainer kits rely on unread requests, which is why readable standards close most of their attack surface. The habit is universal: read the fields, not the title, on every wallet you own.
Mistake: Signing requests without reading them.
Why it bites you: The request's data field is the actual instruction, and hostile fields hide under benign titles. Brent's free mint was an approval in costume.
Mistake: Trusting the website's description over the device screen.
Why it bites you: A malicious front-end can display one request while constructing another. The hardware wallet's screen reads from the key and shows the truth.
Mistake: Signing requests from links in chat messages.
Why it bites you: Phishing front-ends are engineered to harvest signatures and approvals from group-chat traffic. The link you clicked is the delivery mechanism; the signature is the price.
Mistake: Assuming a signed transaction can be reversed.
Why it bites you: Broadcast transactions are irreversible; there is no recall function and no support queue that unwinds them. The chain confirms in minutes and does not do sympathy.
I spent an evening collecting malicious signing requests from scam reports so you do not have to, and the pattern is that the title is always friendly and the data field is always the crime. 'Claim reward' means approve. 'Free mint' means approve. The hostility is never in the headline, which is why the headline is the worst possible thing to read.
The useful version is one rule: read the fields, not the title. I walked Brent through the details panel of the request he signed so you do not have to, and the approval was printed there in plain sight the whole time. The hardware screen showed it too, which is the part I find hardest to forgive. Signing is consent; read the receipt before the network cashes it.
No. Once broadcast, the transaction is irreversible; the only lever is fee-based replacement before mining, which is a different transaction, not a recall.
No. The signature is produced by the key and verified by the network without the key ever being shared; that asymmetry is the entire design.
The hardware screen reads the actual request from your key, while the website displays whatever it wants. The screen is the source of truth, and any discrepancy is the red flag.
It is approving a request you have not read in full, on any wallet. The data field is the instruction, and unread requests are where most signature losses live.
Read the full request in your wallet's details panel, including the data field and parameters. Structured standards such as EIP-712 render it in readable fields rather than a wall of characters.
Disclaimer: This information is general in nature and does not constitute financial or legal advice. Always consult a qualified professional for your specific situation.

Financial Chaos Analyst
Ivy Sinclair-Wren is a Financial Chaos Analyst covering crypto markets, investing behaviour, and the Australian habit of checking prices during family dinners. Based in Melbourne, she reviews AUD Crypto Tracker's coin guides for accuracy, ATO alignment, and ruthless utility — no hype, no predictions, just what the data says.