Wallet EVM Hinkal Overview
Add Hinkal private sends and shielded-fund recovery to seed-based WDK EVM accounts.
Community modules are developed and maintained independently by third-party contributors.
Tether and the WDK Team do not endorse or assume responsibility for their code, security, or maintenance. Use your own judgment and proceed at your own risk.
Use @hinkal/wdk-wallet-evm-hinkal to add Hinkal private sends to a WDK EVM account. The module deposits funds on chain and schedules a later withdrawal to the recipient. It also exposes scheduled-send status and recovery of stuck shielded balances.
Hinkal maintains this module. These pages describe v0.0.7, which uses @tetherto/wdk-wallet-evm@1.0.0-beta.18 and @hinkal/common@0.3.13.
Choose This Module
Use Hinkal when your application needs private sends from a seed-derived EVM account, can track asynchronous settlement, and can reconcile interrupted deposits and recovery operations.
For ordinary EVM transfers, use Wallet EVM. Hinkal account creation does not accept hardware signers, private-key signers, or named signers. Address-only accounts cannot query Hinkal shielded balances or scheduled-send status through this module.
Account Capabilities
| Task | Method |
|---|---|
| Deposit tokens and schedule a private withdrawal | privateSend() |
| Read scheduled withdrawal status | getSendStatus() |
| Find stuck shielded balances | stuckUtxoBalances() |
| Recover a token to the account's own address | withdrawStuckUtxos() |
Accounts retain the inherited EVM operations, including ordinary balances, transfers, signing, and transaction tracking. Those operations do not become private sends.
Integration Requirements
- A BIP-39 mnemonic or seed bytes, handled by the host application's secret storage.
- An RPC provider on the selected chain, plus a token supported by Hinkal on that chain. An EVM RPC alone does not establish Hinkal support. Consult the Hinkal documentation and check current provider support before enabling a route.
- A runtime that resolves the Hinkal dependency correctly. Node applications need the bundling setup; v0.0.7 does not load directly as native Node ESM. The package also supplies a Bare conditional entrypoint.
- Application handling for deposits, scheduled withdrawals, approvals, fees, and interrupted operations. There is no private-send quote or maximum-fee option in this module.
Next Steps
Usage
Install the module and create a Hinkal-enabled account.
Send Private Tokens
Submit a private send and track its scheduled withdrawal.
Recover Shielded Funds
Inspect stuck balances and recover them to the account.
Configuration
Review providers, derivation paths, and fee limits.
API Reference
Review exact signatures, result shapes, and errors.