A fresh look for DriveKey on Mac We’re redesigning the companion with cleaner navigation, clearer swap details, and a simpler path through offline review.

That's approximately how you will verify your wallet you would need to send 1000-10000 drivekey tokens to a provided private wallet in a strict time window to authenticate the link. They will get refunded immediately after a successful link.

Agentic wallets, with the owner in control. DriveKey’s Agent Inbox: a 0.001 ETH payment proposal awaiting approval. Agents can propose; signing and submission stay with the owner.

A fresh look for DriveKey the companion app is ready. Simpler navigation. Colorful token icons. Clearer swap options. Organized settings and notifications—all built around our offline-signing workflow. I recorded a walkthrough of the new desktop UI

We’re building $DVK holder benefits around the services people use in DriveKey: wallet management, transaction preparation, agent workflows and developer infrastructure. Four planned tiers, based on the percentage of total DVK supply held. Each tier includes the benefits below it: 🔵 MEMBER — 0.25% Simulation and monitoring credits, a managed wallet workspace and eligibility for hardware discounts. 🔵 OPERATOR — 0.5% Larger service allowances, multiple wallet workspaces, scheduled transaction proposals, notifications and one inbox for reviewing agent requests. 🔵 BUILDER — 1% Developer API allowances, webhooks, agent integrations, team proposal workflows and exportable execution reports. Tools for people building applications and running operations through DriveKey. 🔵 PARTNER — 2.5% The highest service allowances, multiple team workspaces, integration support and eligibility for hardware bundles under published terms. For the offline USB workflow, agents prepare proposals. You review and approve them. Holding DVK will never give an agent permission to spend from your wallet. Verification is being designed around a separate holder wallet and a refundable DVK deposit, returned automatically after successful verification. Network gas is separate. This mechanism is still under development, and on-chain transfers are public. Core sending, recovery, essential security, accessibility and transaction-history exports will remain available to everyone. Non-holders will also be able to purchase paid services. We’re also evaluating transparent, profit-funded buybacks alongside hardware and service revenue. No allocation is committed yet, and refundable deposits would never fund buybacks. These are planned capabilities, not live entitlements. Exact service quotas, hardware offers and refund terms will be published before activation. The aim is to make DVK useful across the full DriveKey experience—from an individual wallet to a team building with agents.

Don’t forget to export your public wallet after making a vault otherwise it won’t appear in your partition on the usb.

DriveKey OS: sending and swapping, reviewed offline. on Github today. development captures of USDC transfers and WETH USDC swaps—amounts, fees and minimum output visible before signing. Unaudited beta.

DriveKey’s offline signing flow in action Review on USB → approve → save the signed response → shut down → return online to submit. Signing doesn’t send funds. You control the next step.

DriveKey OS keeps moving forward Offline Uniswap signing + restart recovery passed local tests without duplicate sends. SOL/SPL cancellation and Across validation added in source. 250 checks passed. Next: exact-image testing and security review.