Glossary · Security

What is Hot wallet?

A hot wallet holds keys on a connected device: a browser extension, a phone, a server. Connectivity is the point, instant signing for everyday flow, and connectivity is the risk, anything the device can reach can reach the keys.

Hot wallets are for velocity, not value: payment float, trading balances, the gas tank. The discipline is replenishment from cold storage on a schedule, so a compromise costs a day's float instead of the treasury.

How Hot wallet works

A hot wallet holds keys on an internet-connected device: keys on a phone, a browser extension, a server. It is the reachable tier, whose defining property is availability: it can sign now, which every interactive payment depends on, and whose defining risk follows directly: anything that can sign now can be tricked into signing now.

The risk surface is the device and the software chain above it: malware reading clipboards, malicious transaction front-ends displaying one thing while signing another, compromised dependencies. The defenses are containment rather than elimination: keep the hot tier small, scope approvals narrowly, and verify what is being signed somewhere other than the screen that asked you to sign it.

In a tiered setup the hot wallet's job description is narrow: hold operational float, execute routine flows, and be worthless enough at any moment that its compromise is an inconvenience, not a catastrophe. That sizing discipline is the entire security model; a hot wallet is safe exactly to the degree that it matters less than it holds.

Hot wallet in practice

A checkout's receiving wallet pairs with a hot disbursement wallet holding two days of payout float. Malware on the operations machine, at worst, reaches the float; the reserve it cannot touch sits cold.

Hot wallet on U.CASH

Checkout wallets and swap wallets are hot by nature; U.CASH's non-custodial design keeps even those keys yours, so the exposure decision, hot float size, cold sweep cadence, stays with the holder.

Merchants live in this tier operationally: daily payouts, refunds, conversions all sign from hot wallets. The discipline is sizing and scoping, keeping the tier liquid for the day and unattractive to everyone, with U.CASH's approval scoping and destination validation doing part of the guarding. On rotation: turn hot keys over periodically. A rotation cadence bounds the value of any single compromise, and pairing rotation with the sweep schedule costs nothing extra in ceremony while resetting the attack clock on every cycle.

Related security terms

Address poisoningCold walletMultisig

See also

Cold walletNon-custodial

Hot wallet: FAQ

Can a hot wallet be safe enough for a business?
Yes, sized honestly: a hot wallet holding one day of float is a manageable risk; one holding the quarter's revenue is a target. The architecture supports the right split because custody is never forced.
What actually compromises hot wallets?
Almost always the human surface: malicious browser extensions, clipboard swappers, phishing seeds. The device is rarely broken; the operator is tricked.
How much belongs in a hot wallet?
Operational float only: enough that routine flows never stall, small enough that losing it is an operational incident rather than a business event. Reserves go cold.
What are the main hot wallet risks?
Device compromise and transaction-display manipulation: malware and deceptive front-ends. Containment, narrow approvals, and independent verification are the standard mitigations.
Can a hot wallet be made safe?
Safer, by scoping and sizing, never safe in the absolute. The security comes from the tiering: the hot wallet's compromise is survivable by design, which is the property that matters.
Keep reading

The glossary, A to Z

Every term behind the rails, the assets, and the settlement.