Blanksquare x HyperBloom: private token transfers on HyperEVM
We added Blanksquare's privacy protocol to HyperBloom ($300M+ volume). Users send tokens privately with ZK proofs and a TEE, a first on HyperEVM.
Get an estimate- Client
- HyperBloom / Blanksquare
- Team size
- 4
- Year
- 2025

What we built for HyperBloom / Blanksquare
ContextIn short
We integrated Blanksquare's privacy protocol into HyperBloom, creating the first privacy solution on HyperEVM. With Silent Transfer, users send tokens privately using zero-knowledge proofs and a Trusted Execution Environment (TEE). The system is fully non-custodial, has configurable privacy delays and is available to everyone trading on HyperBloom, which has done $300M+ in volume.
The problem
Every on-chain transaction leaves a permanent record that links wallet addresses to trading activity. HyperBloom has processed over $300M in volume, and its thousands of users had the same problem as everyone else in crypto: anyone can trace every wallet-to-wallet transfer, forever. That is a risk for traders, institutions and regular users alike.
What we built
We integrated Blanksquare's shielder directly into HyperBloom. Silent Transfer lets users send tokens between addresses so that the two addresses cannot be linked on-chain.
Funds do not go straight from one wallet to the other. They pass through Blanksquare's shielded pool with a delay the user picks, which breaks the on-chain link between sender and receiver.
How it works
A private send deposits the tokens into the shielded pool. A unique withdrawal key is created and encrypted inside the TEE, and zero-knowledge proofs validate the transaction.
The TEE holds the key only for the delay period and can only execute that one withdrawal. Data stays confidential and in the user's custody. Even if the infrastructure were fully compromised, funds would stay safe and recoverable.
Each transaction also has an expiry time slightly longer than the chosen privacy level. If the transfer does not complete and the destination address never receives the funds, the user can reclaim the tokens after expiry. Funds are never trapped for good.
The user flow
Users stay in the HyperBloom interface they already know. They connect a wallet, enter the amount, privacy level and destination address, and click send.
The transfer executes after the delay, at a randomized time so it blends in with other protocol activity. Proof generation, pool management and timing all happen in the background. It is the first privacy solution on HyperEVM built directly into a major DEX aggregator, and it needs no extra tools or wallets.

Challenges and how we solved them
ChallengesNon-custodial by design
Most privacy tools ask users to trust a third party with their funds.
We made the system fully non-custodial. The TEE holds a withdrawal key only temporarily and can only carry out predefined actions. Zero-knowledge proofs validate every transaction. They prove a withdrawal request is legitimate without revealing who made it or linking sender to receiver. Even if the infrastructure were fully compromised, user data and funds stay protected.
Private transfers in one click
ZK proofs, TEEs and shielded pools are no help if people cannot use them.
We built Silent Transfer as a one-click flow. Users set three things and press send. Proof generation, pool management and timed execution all happen in the background. The feature sits inside the HyperBloom interface users already know.
Randomized timing
A fixed delay creates a pattern that chain analysis could pick up.
Users choose a privacy level, and the transfer executes at a random time between half and the full length of that window. This lets it blend in with other activity in the protocol. A longer privacy level gives stronger privacy, because the transfer mixes with more pool activity.

Building something similar?
The team that built Blanksquare x HyperBloom can scope your project. Send a few lines about what you are building. We reply within 24 hours, usually the same business day.
Ready when you are
Tell us what you are building and where you are stuck. You get a reply from an engineer and a scoped estimate for a PoC, MVP or full launch. We reply within 24 hours, usually the same business day.