Hinkal is now integrated in Tether's WDK

Hinkal is now integrated in the Wallet Development Kit (WDK) by Tether. If you're building a self-custodial wallet or app on WDK, you can now give your users private sends, straight from the stack you already use.
‍

What is WDK

WDK is Tether's open-source SDK for building multi-chain wallets. It's self-custodial, so users hold their own keys and developers never touch them. Teams use it for everything from consumer apps and payment services to enterprise products, connected devices and AI agents. It's also modular: pick the networks, providers and features you need, and skip the rest.

Hinkal now ships as one of those modules: @hinkal/wdk-wallet-evm-hinkal.
‍

What private send does

Onchain transfers are public by default. That works for plenty of payments. But once someone links a wallet to you, every payment you've sent or received can be traced back to you.

Private send gives your users another option:

• The sender deposits stablecoins or other assets into Hinkal.

• Hinkal schedules a private withdrawal to the recipient.

• The funds arrive at the recipient's address, with no onchain link back to the sender.

The sender, the recipient and the amount stay private, and nothing onchain ties who paid to who got paid. The recipient can be any address, and they don't need a Hinkal account, a special wallet or any extra steps.

Settlement is asynchronous, so apps can track each send with getSendStatus() and keep users posted.
‍

What it enables

Payrolls
You can pay your team in stablecoins from one wallet and anyone who looks up that address can see every salary. With private sends, who you pay and how much stays between you and your team.

Suppliers and partners
A public payment shows your counterparties to each other and to your competitors. Private sends let you settle onchain without publishing your vendor list or your pricing.

Treasury
Moving funds between wallets can signal a strategy before you've acted on it. Private sends keep those moves out of view until you're ready.

Personal payments
Splitting a bill shouldn't give someone a window into your whole wallet. The payment lands, and your balance and history stay yours.

For wallet teams
Many users  ask for privacy, and some need it for work. On WDK, it's a module you add, so you do not need to spend months building it.

‍

For developers

Getting started:

• Install @hinkal/wdk-wallet-evm-hinkal
• Create a Hinkal-enabled account from a BIP-39 mnemonic or seed
• Point it at an RPC on a chain Hinkal supports
• Call privateSend() to send and getSendStatus() to track it

There's also a recovery path: stuckUtxoBalances() finds shielded funds that didn't settle, and withdrawStuckUtxos() returns them to the account's own address.

‍

Two things to know before you build:

Seed-based EVM accounts

The module works with seed-based WDK EVM accounts, created from a BIP-39 mnemonic or seed bytes. Hardware signers, private-key signers and named signers aren't supported.

Supported chains

‍The module runs on the EVM chains Hinkal supports, not on any EVM RPC. Check Hinkal's current network list before enabling a route.
‍

The code is available on GitHub, the package is on npm as @hinkal/wdk-wallet-evm-hinkal, and full setup, bundling notes and API reference are in the WDK docs.

‍

Why it matters

Self-custody gave people control of their keys. It didn't give them control over who sees what they do with those keys. Every payment on a public chain leaves a record that anyone can follow, and once a wallet is tied to a name, that record tells a story: who you pay, how often, how much, and what's left.

For individuals, that means a friend, landlord or stranger can see far more than the one payment they were part of. For businesses, it means salaries, vendor relationships and treasury activity are all open to competitors. That's a big reason many teams still hesitate to run real operations onchain.

Private sends close that gap without taking anything away. Public transfers still work, and users choose privacy when a payment calls for it. With Hinkal in WDK, any wallet built on it can offer that choice from day one, with no need to build privacy infrastructure from scratch.