DRIVEKEY_Security / FAQ

DRIVEKEY / TERMINAL 02

Offline transfer

Prepare. Sign on USB. Return to send.

ROBINHOOD CHAINETH / 4663—
Current UTC (this computer):

Website and USB use UTC only. Z means UTC; your local timezone does not change the deadline. On the USB, use menu 9 if its clock is wrong and enter the actual current UTC from an independent clock—not the deadline below. An offline clock cannot sync automatically.

01 / public walletWAITING

Load your public wallet

The public file created on your offline USB. Follow the Setup guide if you have not created one yet.

Public metadata only. Never upload vault-encrypted.json or enter your vault passphrase here.

02 / prepare & exportINPUT

Where is it going?

ETH
Native ETH onlyTransfer cap / 0.005 ETH
03 / offline approvalON YOUR USB

Take it offline.

  1. 01
    Save the request in the USB’s DriveKey folder.
  2. 02
    Boot the USB with networking disconnected. Check UTC, then review and sign locally.
  3. 03
    Shut down fully. Return to this exact URL in the same Windows browser.
Using the older command-line signer?

Run sudo drivekey-offline sign and enter your passphrase only there. Finish with sudo poweroff. A VM is for unfunded tests, not your real wallet.

04 / verify & submitAWAITING FILE

Bring back the signature.

The signed response is checked against the exact request above.

Submission is locked for this preview. You can still prepare and verify.