Introducing Hinkal Deposit Addresses. Until now, receiving funds into a private balance required the sender to interact with smart contracts. That made CEX withdrawals, PSP payouts, transfers from custodial wallets, and even simple payments from another person difficult to receive privately. That changes today. Your Hinkal Deposit Address works like a regular wallet address. Share it with anyone, withdraw to it from an exchange, or use it as the destination for payouts from a payment provider. For the sender, it’s a standard transfer. No Hinkal UI or smart contract integration is required. Every deposit is screened before it enters your private balance: • Eligible funds are shielded automatically, with no additional step required. • High-risk funds remain outside your private balance, where they can be returned or sent to another wallet. This separation matters. A single high-risk incoming transfer can compromise the risk profile of a public wallet, making otherwise clean funds harder to move. Hinkal screens funds at the point of entry, keeping flagged deposits separate from your eligible balance. Whether you’re receiving money from another person, withdrawing from an exchange, collecting customer payments, or settling payouts at scale, all the sender needs is your deposit address. A regular transfer for the sender. A private balance for the recipient. Try it out at pay.hinkal.io

Read a more detailed information in our blog here: hinkal.io/blog/robinhood-cha…

🤝

Another independent security review completed ✅ @Quantstamp assessed the core Hinkal protocol, including its smart contracts and Circom circuits. An important step in maintaining a rigorous security standard across Hinkal’s privacy infrastructure. See full report below.

Your treasury should not inherit the risk profile of every wallet that sends you money. On public blockchains, incoming transfers typically land directly in the same wallet you use for the rest of your activity. If one of those deposits comes from a high-risk source, that exposure now sits alongside the funds you actually want to operate with. Hinkal Deposit Addresses move the screening step to the point of entry. Every incoming transfer is screened before it reaches your private balance. Eligible funds are automatically moved into Hinkal and become available to use privately. High-risk funds remain outside the private balance, where they can be returned or sent to another wallet. This creates a clear separation between what gets sent to you and what actually enters your operating balance. No manual screening step. No need to receive everything into your public wallet first and sort it out afterward. Screen at the point of entry. Keep high-risk funds out of your operating balance with a Hinkal Deposit Address at pay.hinkal.io.

More merchants are getting paid in stablecoins. The problem is that those settlements usually land in a public wallet, exposing the merchant’s receiving address, balances, transaction history, and what happens to the funds next. Instead of giving your payment service provider your public operating wallet, you can use a Hinkal Deposit Address as the settlement destination. It works like a regular wallet address, so they send the payout exactly as they do today. Once it arrives, eligible funds are screened and automatically moved into your private balance inside Hinkal, so the settlement is not publicly tied to the wallet you actually use onchain. The payment provider does not need to integrate Hinkal, interact with a smart contract, or change how it sends payouts. For them, it is the same settlement flow. For you, the funds arrive privately. They settle as usual. You receive privately. Use a Hinkal Deposit Address for your next merchant settlement at pay.hinkal.io

A standard CEX withdrawal sends funds directly to a public wallet address, making the destination wallet, along with its balance and transaction history, visible onchain. With Hinkal, you can keep that financial activity confidential by withdrawing to a Deposit Address instead. Generate a Deposit Address at pay.hinkal.io, paste it into Coinbase, Kraken, Binance, or any other exchange as the withdrawal destination, and withdraw as usual. Once the funds arrive, they are automatically moved into your private balance inside Hinkal, where your activity is no longer publicly tied to the wallet you actually use. The exchange does not need to integrate Hinkal or change how withdrawals work. And you do not need to withdraw to a public wallet first and then make a separate transaction into Hinkal. You withdraw once, and the funds arrive directly in your private balance. Make your next CEX withdrawal private with a Hinkal Deposit Address at pay.hinkal.io. Available now across @ethereum, @solana, @trondao, @arbitrum, @BNBCHAIN, @tempo, @0xPolygon, @arc, and @base.

"Where do we see the biggest adoption? Not on private chains. We see it on public chains." That one observation is why Hinkal exists. If money moves on @solana and @ethereum , not on chains purpose-built for privacy, then privacy isn't a feature the chain ships. It's a problem the chain's customers have. And the need only grows. Dollars. Then FX. Then securities. Every asset that moves on-chain pushes privacy from preference to requirement, until it's non-negotiable. @gegelz bet on that four years ago, before anyone was asking. Hence the constraint: privacy by default, no rip-and-replace. Existing wallets, any asset, any form. Full episode with @catmcgee and @Maxwolfj here nitter.net/hinkal_protocol/status…

Deals of the Week · Aug 30 – Sep 5. 11 deals. Last month banks were lending against crypto. This week they started issuing on it. The big one: 21 banks - BofA, @Citi , @GoldmanSachs , @UBS , @DeutscheBank , @SantanderMx + more - are forming a joint company to issue a regulated USD stablecoin on public chains. And 7 US banks put $32.5M into Cari, an @ethereum L2 for tokenized commercial deposits. Banks aren't just using the rails. They're building them. Biggest check of the week: Félix - $200M ($87M equity + $113M credit) for WhatsApp remittances on USDC/Stellar. Rest of the board: @OpenReserveBank - $25M, digital bank + rUSD @DiameterPay - $10M, USD account APIs @Firelightfi - $8M, exploit cover @1096361BTC - $8M @aigaealabs - $3.6M @Plenti - $3M @ParlayXOfficial - $1.25M @PolarisProgram - $1M A tokenized deposit is a client's balance and payment flow - onchain. No bank puts that on a public explorer. Private settlement is the part that has to work first.

Stablecoins & payments, 31 Aug - 4 Sep. 22 stories, three that count: The BIS argued tokenised deposits will beat stablecoins in payments. TD finished Agorá testing, 21 banks (@BofA_News , @Citi , @GoldmanSachs ) named 2027. Tether's CEO fired back within a day. Yield is now the product. @MEXC : 10% cashback + 7% APY. @ethena Pay on @avax : 6% + 10%. @stripe hired an exec just for stablecoin cards. Everyone bought the map, not the ledger - Vietnam, the Philippines, South Africa, Korea, LatAm, plus EURC going crosschain via CCTP. Also: MAS opened its stablecoin framework to consultation. Full digest

Excited to join @PlugandPlayTC & @XDCNetwork accelerator alongside some great teams building the future of finance. Plug and Play has build the bridge between emerging technologies and traditional markets with the biggest companies in the world. Now we are part of this bridge where Hinkal will enable bank level privacy for actual banks and FIs. Exciting moment for Hinkal to enable privacy to the most sophisticated players in the world.