Course 6 · Risk & margin
Wallet and venue risk literacy
On-chain options add signing and custody paths on top of market risk. Hardware wallets keep keys offline but still sign whatever you approve. Software wallets suit small hot balances. Phishing clones and malicious approvals move funds with your consent. Venue risk — custody, oracles, halts — sits beside wallet hygiene. The option's max loss is not the same as funds posted to a venue.
- Lesson
- 7 of 7
- Level
- Beginner
- {minutes} min read
- 16 minEST
- Prerequisites
- 1
Not a certificate. Progress stays on this device.
Before this: Liquidation risk
You'll be able to
- separate hardware and software wallet roles
- list phishing patterns that still beat cold keys
- name venue risks that research desks do not remove
- keep session or per-trade margin apart from funds you do not mean to post
TL;DR
On-chain options add signing and custody paths on top of market risk. Hardware wallets keep keys offline but still sign whatever you approve. Software wallets suit small hot balances. Phishing clones and malicious approvals move funds with your consent. Venue risk — custody, oracles, halts — sits beside wallet hygiene. The option's max loss is not the same as funds posted to a venue.
Learn
Centralized venues add custody and operational risk. On-chain venues add smart-contract, oracle, and wallet-signing risk. Both can halt or degrade in stress. Choosing where to trade is choosing a liquidation and credit regime, not only a book of marks. The [max loss](/edu/glossary/max-loss) of a structure is a property of the payoff. It does not measure what happens to funds sitting at a venue that pauses withdrawals, mis-prices an oracle, or fails. Those are venue risks, and they sit beside the market risk this course has already covered.
Hardware wallets keep private keys in a secure element. They shrink malware that scrapes seeds from disk. They do not tell you that a site is the real venue, that a contract is the one you meant, or that an unlimited allowance is a good idea. If you approve a wrong address or a malicious typed-data payload on the device screen, funds still move. The device signs what you confirm. Read the screen, not only the browser summary, and reject the prompt when the two disagree.
Software wallets (browser extensions, mobile apps) fit small hot balances for day-to-day venue UX. They are a wide attack surface for a large treasury. Separate hot [margin](/edu/glossary/margin) from cold storage. Fund the hot wallet with what you need for the session; withdraw size back to cold after. A lifetime balance left on a hot extension connected to experimental apps is not a session fund — it is the whole stack, exposed to every approval you click.
Phishing wins with urgency: clone domains, fake support that asks for a seed or "sync," clipboard rewrite of deposit addresses, and blind permit signatures. OptionsMatch is research only — it does not ask for seeds, private keys, or wallet connect to read Match profiles or education. Open venues from typed URLs or your own bookmarks. Reject on-device when the screen disagrees with the browser summary. Pasting a seed into any website for recovery or sync is a transfer of the keys, not a support step.
Venue risk is a second ledger. A centralized operator holds your posted margin as a credit at that operator (UNVERIFIED per venue how that credit is segregated). An on-chain venue holds it in a contract you have approved (UNVERIFIED per contract). Halts, oracle incidents, withdrawal queues, and insolvency are not in the option's payoff diagram. Two venues are two credit islands: a long on Venue A does not offset a short on Venue B, and a withdrawal from one does not fund the other until it actually arrives. Test a small deposit and a small withdrawal before you post a session's worth of margin. This lesson does not fetch any venue's withdrawal rules.
Worked example 1 · the 50,000 account and a 500 hot path · EXAMPLE
The sizing lesson used an EXAMPLE account of 50,000 and a 500 unit of risk per trade or session. That 500 was the budget for option max loss. The same split is a hygiene amount for what you post as day-to-day venue margin, not a claim that 500 is the right size for your account.
| Where the funds sit | What is exposed if that path fails | What is not automatically exposed |
|---|---|---|
| Hot path at the venue, 500 posted (EXAMPLE) | The 500 posted as margin (EXAMPLE), plus any open payoff already on that venue | The rest of the 50,000 account, if it was never deposited (EXAMPLE) |
| Whole 50,000 posted to one venue (EXAMPLE) | The 50,000 posted (EXAMPLE), not only the option's max loss | Nothing held off-venue; there is no leftover buffer at that operator |
| Two venues, each treated as its own island (UNVERIFIED rules) | Whatever you posted on the venue that fails | Funds on the other venue, and funds never deposited |
You have 50,000 (EXAMPLE) and a 500 session or per-trade limit (EXAMPLE). You mean to trade the 100/110 bull call, debit and max loss 2,500 (EXAMPLE). That 2,500 already exceeds the 500 risk unit, so the sizing lesson would have you skip or shrink the ticket — this page is not reopening that size. The custody question is separate: if you still post the whole 50,000 to the venue "so margin is handy," a halt, a withdrawal queue, or an operator failure can tie up or lose the 50,000, not only the 2,500 option max loss. Posting only the 500 hot-path amount (EXAMPLE) does not make the venue reliable; it only means the rest of the 50,000 was never handed over. Venue rules for how posted funds are held are UNVERIFIED. This split is a hygiene sketch, not a recommendation of those amounts.
Worked example 2 · a signed approval and a deposit typo · EXAMPLE
The same 500 hot balance (EXAMPLE) sits in a software wallet connected to a venue. A clone site, reached from a chat link rather than a bookmark, asks you to "approve" a contract so the official book will load. The hardware device, if you use one, still signs that approval if you confirm the prompt. Once signed, the 500 can leave without a second trade ticket. A hardware wallet would have stopped a seed scrape from disk; it would not have stopped a confirmed approval. The lesson is to read the device screen, reject unexpected allowances, and open the venue from a URL you typed or bookmarked yourself. A second path: you withdraw "the rest" of the 50,000 after a session and paste a deposit address from the clipboard. A clipboard rewrite can send that withdrawal to an address you did not write down. Test a small deposit and a small withdrawal first; confirm the address on a second channel you already trust. This page does not invent a fee or a minimum for that test (UNVERIFIED per venue and chain). OptionsMatch does not custody keys and does not ask for seeds.
Figure
The planned figure, for Nova to draw, splits the EXAMPLE 50,000 account: a 500 session or per-trade limit on the hot path, the rest not posted as day-to-day venue margin. Beside it, two boxes labelled Venue A and Venue B as separate margin and credit islands. Until that figure is drawn, treat the table and the two worked sketches as the record.
Not financial advice. The worked numbers on this page are EXAMPLE sheet prices and MODEL greeks, not live quotes and not a recommendation. Options can lose all the premium paid, and a short option can lose far more than the premium collected. Size every position to its max loss. Venue margin, settlement and fees are UNVERIFIED until you check them yourself.
Checklist · EXAMPLE hygiene amounts only
| Step | Habit |
|---|---|
| 1 | Research on OM; execute on a bookmarked official venue URL |
| 2 | Hot wallet holds only session margin (EXAMPLE: 500 of the 50,000 account) |
| 3 | Hardware confirm: address, asset, amount, contract |
| 4 | Reject unexpected allowances and seed requests |
| 5 | Test deposit and withdrawal before posting session margin |
Try it
Stay on research desks first. When you leave for a venue, use a bookmark you set yourself — not a link from chat. On a scratch pad, write the 50,000 / 500 split (EXAMPLE) and the 2,500 bull-call debit (EXAMPLE) in two columns: option max loss, and funds actually posted. The second column is the venue-risk number.
Common mistakes
Treating the option's max loss as the most you can lose once funds are posted. A 2,500 debit (EXAMPLE) is not the venue-risk number if you posted 50,000 (EXAMPLE). Pasting a seed into any website for recovery or sync. Leaving the whole 50,000 (EXAMPLE) on a hot extension connected to experimental apps. Approving device prompts without reading the screen, or trusting the browser summary when the device shows a different address or allowance. Assuming two venues offset each other, or that a withdrawal has arrived because you clicked send. Skipping a test deposit and withdrawal, then posting session margin to an address or network you have not used.
Crypto angle
On-chain venues inherit chain congestion, gas spikes, and oracle design; centralized venues inherit custody and withdrawal queues. Both are UNVERIFIED in detail per operator. A 24/7 book does not mean withdrawals are instant (UNVERIFIED). Unlimited token allowances and permit signatures are a recurring phishing path. Hardware wallets help only if you read the device. OptionsMatch does not custody keys, does not ask for seeds, and does not wallet-connect to show education or Match profiles.
In your market
Crypto: on-chain venues inherit chain congestion and oracle design; centralized venues inherit custody. Both are UNVERIFIED in detail per operator. Hardware and software wallet hygiene, and the 50,000 / 500 posted-margin split (EXAMPLE), apply here first.
Equities: broker custody and clearing replace self-custody, but account-takeover and phishing of login credentials remain real. Posted margin is still a credit at that broker (UNVERIFIED how it is segregated). The option max loss and the cash in the account are still two different numbers.
Index: same custody lesson as the parent market; settlement risk is still a venue rulebook topic, covered in the settlement lesson, and it is not removed by wallet hygiene.
Futures: FCM and clearinghouse paths differ from self-custodied wallets; read who holds margin (UNVERIFIED per product). A futures-margined leftover from assignment, covered in the settlement lesson, is a venue-margin bill, not a seed phrase.
FX: prime brokerage and margin-currency risk replace seed phrases; credential phishing still applies. Convert posted margin to one unit before you compare it with an option max loss in another currency.
Recap
Wallet risk and venue risk sit beside the option's payoff. Hardware wallets keep keys offline but still sign whatever you confirm. Software wallets fit a small hot balance, not a lifetime treasury. Phishing uses clone sites, fake support, clipboard rewrites, and blind approvals; OptionsMatch does not ask for seeds or wallet connect. On the EXAMPLE sheet, a 50,000 account with a 500 session or per-trade limit should not post the whole 50,000 as day-to-day venue margin. The 100/110 bull call's 2,500 debit and max loss (EXAMPLE) is the option number; funds posted to the venue are the venue-risk number. Two venues are two credit islands. Test a small deposit and withdrawal first. Venue segregation, withdrawal times, and contract details are UNVERIFIED per operator.
Check questions
1. Does a hardware wallet stop a confirmed malicious approval? 2. If you post the whole 50,000 (EXAMPLE) to trade a 2,500 debit (EXAMPLE), what is exposed to venue failure? 3. What is the point of posting only the 500 hot-path amount (EXAMPLE)? 4. Do two venues offset each other's credit risk? 5. Does OptionsMatch ask for seeds or wallet connect to read education? Answers: 1. No. It signs what you confirm on the device. 2. The 50,000 posted (EXAMPLE), not only the 2,500 option max loss. 3. The rest of the 50,000 was never handed to that venue; it does not make the venue itself reliable. 4. No. They are two credit islands. 5. No. OptionsMatch is research only and does not custody keys.
Key terms
[Margin](/edu/glossary/margin) · [Max loss](/edu/glossary/max-loss) · [Liquidation](/edu/glossary/liquidation) · [Premium](/edu/glossary/premium) · [Debit](/edu/glossary/debit)
Quiz
Not financial advice. This lesson is education only. It does not recommend any trade or say any approach will make money. Every number tagged EXAMPLE is made up to show the arithmetic; none of it is live data. MODEL numbers come from Black-76 with the stated inputs and will differ from any venue's quotes. Venue specs, settlement times, margin and fees are UNVERIFIED: check each venue yourself. Options can lose all the premium paid, and short options can lose far more than the premium collected. Size every position to its max loss.
Try it
BTC terminal →Quiz
1. Does a hardware wallet stop a confirmed malicious approval?
No. It signs what you confirm on the device.
2. If you post the whole 50,000 (EXAMPLE) to trade a 2,500 debit (EXAMPLE), what is exposed to venue failure?
The 50,000 posted (EXAMPLE), not only the 2,500 option max loss.
3. What is the point of posting only the 500 hot-path amount (EXAMPLE)?
The rest of the 50,000 was never handed to that venue; it does not make the venue itself reliable.
4. Do two venues offset each other's credit risk?
No. They are two credit islands.
5. Does OptionsMatch ask for seeds or wallet connect to read education?
No. OptionsMatch is research only and does not custody keys.
Key terms
Educational content only — not financial advice. Product rules vary by venue; verify on the exchange. OptionsMatch labels Snapshot / Partial / Last good on Match, and LIVE, Partial data, or EXAMPLE on Terminal desks.
FAQ
- Does a hardware wallet stop funds moving if I confirm a bad approval?
- No. A hardware wallet keeps keys in a secure element and shrinks malware that scrapes seeds from disk, but it still signs whatever you confirm on the device screen. A clone site, a wrong address, or a malicious typed-data payload can move the 500 hot-path balance (EXAMPLE) once you approve it. Read the device, not only the browser summary, and reject unexpected allowances. OptionsMatch does not ask for seeds, keys, or wallet connect.
- If I post the whole 50,000 account to trade a 2,500 debit, what is at venue risk?
- The 50,000 posted (EXAMPLE), not only the 2,500 bull-call debit and max loss (EXAMPLE). A halt, a withdrawal queue, or an operator failure can tie up or lose posted funds regardless of the option payoff. Posting only the 500 session or per-trade amount (EXAMPLE) does not make the venue reliable; it only means the rest of the 50,000 was never handed over. How posted funds are held is UNVERIFIED per operator.
- Do two venues offset each other's custody or credit risk?
- No. Two venues are two credit islands, just as they are two margin islands in the liquidation and multi-leg lessons. A long or a cash balance on Venue A does not offset a short or a failure on Venue B, and a withdrawal has not funded the other venue until it actually arrives. Test a small deposit and a small withdrawal before you post session margin. Withdrawal times and segregation rules are UNVERIFIED per operator.
- Does OptionsMatch custody keys or ask for a seed to read this lesson?
- No. OptionsMatch is research only. It does not custody keys, does not ask for seeds or private keys, and does not wallet-connect to show education or Match profiles. Open a venue from a URL you typed or bookmarked yourself, not from a chat link. Pasting a seed into any website for recovery or sync is a transfer of the keys, not a support step. Keep hot session margin apart from funds you do not mean to post.