A stablecoin payouts product uses Openfort. A user signs in with an email address and has a wallet a moment later, with no seed phrase to write down and no extension to install. Then the first batch of payouts goes out, and every recipient and every amount sits on a block explorer with one address attached to them.

The same happens to a consumer payments app with its user balances, and to a business moving volume through embedded wallets on behalf of its customers. Openfort did its job completely: the user got a wallet without touching a seed phrase, and the key stayed protected. What no wallet layer can change on its own is that a public chain publishes what the wallet does next - the balance it holds, the addresses it interacts with, and the size of every transaction.

For a payment product, a stablecoin application, or a business moving meaningful volume, that is a structural problem rather than a privacy preference.

What changes

Products built on Openfort can now add privacy through the Hinkal API, without changing their existing wallet infrastructure.

The user's balance stops being readable. Transfers, swaps, withdrawals and payouts stop naming the sender. What the public record holds is that an address deposited into Hinkal once, and nothing that ties that address to what follows.

For a payout run, that is the difference between publishing a recipient list and publishing one deposit.

What does not change

Openfort authenticates the user, creates and secures the wallet, and produces the signature. Hinkal touches none of it.

What Hinkal needs is that signature, and an Openfort wallet already produces one. That is the whole integration surface. There is no second wallet for the user to fund, no custody handoff, no new key for anyone to manage, and no change to how the application signs users in. The user logs in the same way and keeps the same wallet.

How it works

The user's own signature authorizes every operation. Each private action is authorized by a signature from the user's Openfort wallet, committing to that specific operation: the chain, the token, the amount, the recipient. Hinkal can execute the operation the user signed and nothing else.

Hinkal accesses the user's private balance and generates the zero-knowledge proof inside a secure enclave, then builds the transaction. The wallet's private key never reaches it. The only thing Openfort hands Hinkal is a signature.

Once a user deposits funds, every operation after that goes out through a relayer rather than the user's wallet. The user's address never appears as the sender, and a withdrawal cannot later be tied back to the deposit that funded it.

Every deposit is screened by Chainalysis KYT before funds enter the contract. Sanctioned and high-risk addresses are blocked at the protocol layer, in the path of the transaction, rather than flagged after the fact. 

Explore the Integration>