good idea

that’s the plan eu and us has priority

DriveKey USB pre-orders open this Friday. Our USB drives are manufactured by GOODRAM. Pay with crypto or debit car or use $DVK to receive a 20% discount on your order. Full pre-order details coming on the new website subdomain.

i did sorry for the delay

DriveKey USB pre-orders open this Friday. Here’s a closer look at the concept design—from the graphite enclosure to the electronics inside. Full pre-order details coming soon. #DriveKey

after we post the design i’ll update the website with the preorder

Drivekey Usb drives are in production the finalized design will be posted today it features a usb c and usb A connector and a oled screen in sturdy casing.

Privacy is one part of self-custody. Long-term control is the bigger mission. DriveKey’s roadmap goes beyond a new interface. Alongside our Hinkal integration and offline signing workflow, our separate post-quantum savings research already includes working code and local Ethereum experiments. The model combines classical ECDSA + hash-based SLH-DSA. Every approving signer must pass both checks over the same exact authorization. One signature family alone cannot authorize the action. For Strong savings, two distinct signer pairs out of three must approve. The contract then checks the recipient, amount, nonce, expiry and configuration before enforcing the withdrawal delay. Recovery and key changes have their own approval rules. The restricted savings design excludes arbitrary contract calls, token approvals and agents. Our recorded research includes: 167 passing reference tests 15 local Ethereum scenarios across 113 transactions, including expected rejections 76 bounded adapter mutation cases matching the reference implementation Independent OpenSSL cross-checks Next: hardware validation, performance and gas measurements, independent review, and turning that research into a practical savings experience. Private activity. Offline control. A stronger foundation for the threats ahead.

What would you like to see most in Drivekey comment your ideas below.

Privacy deserves its own OS. 🔐 DriveKey using Hinkal: building private swaps and payments around Hinkal’s SDK + API. Review offline. Sign offline. Generate proofs locally. Spending keys stay offline.

Signing happens offline; proof generation runs afterward on the connected device in a browser worker, keeping the UI responsive and spending keys offline. Our synthetic browser benchmark generated and verified both proofs in about 13 seconds. We haven’t benchmarked low-powered devices yet. Currently there’s a two-minute timeout, and the encrypted recovery file lets users move proving to a stronger computer without moving spending keys.

DriveKey new os is live The new web interface is live. Built with Hinkal’s SDK + API, bringing private ETH→USDC swaps and payments into an offline-first workflow. Offline signatures. Local proofs. Spending keys stay offline. drivekey.info/app/hinkal

DriveKey OS development, running in a VM. Vault management, offline transaction signing, and system checks are working. Encrypted vaults survive shutdown and reboot. Signed requests return to Windows without exposing spending keys.

that depends on the fomo team.

DriveKey preview went live Private Ethereum. Offline signing. A matching Windows companion. Black-and-white, built for clarity.

Today later during the day the new windows companion is dropping for older and current os models

DriveKey’s Windows companion Prepare online → approve offline → prove locally → submit explicitly. A focused workspace for swaps, private payments and recovery. Spending keys stay offline.

First look at DriveKey’s new UI. A monochrome workspace for private Ethereum: shield, swap, pay and withdraw, with offline approval and local proofs. Real mainnet transactions tested in a VM. Physical device testing continues.

a non ai edited pic with the details covered