Drivekey @DriveKeyyy

@miguelmusk1 we won’t ever stop just we don’t want to tweet about things that aren’t true development milestones and making the new os isn’t a one day process we will tweet more often.

a completely new vault creation and transaction signing method using ZK proofs will be present in the new update the whole system and its capabilities will be on a new level compared to the last version it will be our first flagship model.

We are sorry for the lack of updates we are working on a very important integration crucial to the development of the system more info when we finish. The whole system is currently under a makeover.

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.

keyboard_arrow_left Previous keyboard_arrow_right Next

today a updated mac companion ui drops stay tuned for the download link

The SDK that is made by Hinkal allows wallets, dApps, and payment platforms to integrate protocol-level privacy on Ethereum, Solana, Tron, Polygon, Base, Arbitrum, and Optimism. It hides transaction history, wallet relationships, and asset flows on-chain while preserving public-chain finality and compliance. It will greatly benefit Drivekey expanding its capability across other chains.

Big things ahead for DriveKey Our interview with Hinkal went great! We’re integrating private swaps and transfers, with ZK proofs adding cryptographic verification while protecting sensitive transaction details. Stronger privacy. Easier use. Big news this week.

Fewer DriveKey updates today—we’re focusing on our interview with Hinkal to explore private balances and ETH → USDC swaps with offline approval. Compatibility is still being assessed. We’ll share what we learn.

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.

@CharlesDin1521 for any collaboration or development help please message me privately

fomo.family/r/Drivekey We made a official fomo account soon we will receive the dev tag.

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

The fomo account will be the one to receive buyback funds aswell.

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.

@0xjkrpt we will post a update soon.

the companion app will receive a completely new ui that will be integrated into our website and os next along with that holder only benefits that you will receive after proving your wallet authenticity with token transactions that you will need to make in a certain time window. That will allow you to receive benefits without linking your wallet.

@0xjkrpt If someone misses the transaction window they can try again not only the time will go into the verification you will need to send exact token amounts.