Blanksquare Integration: First Privacy Solution on HyperEVM with ZK Proofs
We integrated Blanksquare's privacy protocol into HyperBloom ($286M+ volume), delivering anonymous token transfers through ZK proofs and TEE technology. First comprehensive privacy solution on HyperEVM enabling untraceable transactions for DeFi users.
One application that allows many
CONTEXTTLDR
23stud.io integrated Blanksquare's privacy protocol into HyperBloom, creating the first comprehensive privacy solution on HyperEVM. Users can now send tokens anonymously using Silent Transfer - combining zero-knowledge proofs with Trusted Execution Environments. The system is 100% non-custodial with configurable privacy delays, serving HyperBloom's $286M+ trading volume.
The Privacy Problem in DeFi
Every on-chain transaction creates a permanent record linking wallet addresses to trading activity. With Hyperbloom processing over $286 million in volume, thousands of users faced the same problem as everyone else in crypto - complete transaction transparency that lives on-chain forever.
Key fact: Every wallet-to-wallet transfer is permanently traceable by anyone, creating privacy risks for traders, institutions, and regular users.
Our Privacy Solution
We integrated Blanksquare's shielder directly into Hyperbloom, delivering the first comprehensive privacy solution on HyperEVM. The Silent Transfer feature allows users to send tokens between addresses while making those transfers cryptographically unlinkable.
Instead of direct wallet-to-wallet transactions that anyone can trace, funds route through Blanksquare's shielded pool with configurable time delays. This breaks the on-chain link between sender and receiver.
How the Technology Works
The implementation combines zero-knowledge proofs with Trusted Execution Environments (TEE). When users make a private send, tokens deposit into a shielded pool and a unique withdrawal key gets created and encrypted within the TEE.
Security guarantee: Data remains confidential and in user custody. Even if infrastructure were completely compromised, funds remain safe and recoverable.
The TEE holds the key only for the delay period and can execute only that specific withdrawal action. Every transaction also includes an expiration time slightly longer than the selected privacy level.
User protection: If the transfer doesn't complete and the destination address doesn't receive funds, users can manually reclaim their tokens after expiration. Funds are never permanently trapped.
Simple User Experience
Users interact with the same familiar Hyperbloom interface they already know. The privacy feature adds just three steps: connect wallet, specify amount and privacy level, enter destination address, click send.
That's it. The transaction executes after the set delay with randomized timing to better blend with other protocol activity. All the complexity - proof generation, pool management, timing randomization - happens entirely in the background.
Key fact: First privacy solution on HyperEVM integrated directly into a major DEX aggregator interface, requiring zero additional tools or wallets.
We solve minor and major problems
CHALLENGESNon-custodial architecture with cryptographic guarantees
Privacy solutions often require trusting a third party with your funds. Users rightfully demand better.
We implemented a fully non-custodial system where the TEE holds withdrawal keys only temporarily and can execute only predefined actions. Zero-knowledge proofs validate every transaction, proving withdrawal requests are legitimate without revealing identity or linking sender to receiver. Even with complete infrastructure compromise, user data and funds remain protected.
Seamless UX for complex cryptographic operations
ZK proofs, TEEs, shielded pools - powerful technology that means nothing if users can't actually use it.
We built Silent Transfer as a one-click process requiring minimal user intervention. Users specify three parameters and click send. The complexity of proof generation, pool management, and timed execution happens entirely in the background. Privacy options integrate as an additional feature within the existing Hyperbloom interface users already know.
Optimizing privacy through timing randomization
Fixed delay times create patterns that sophisticated blockchain analysis could potentially exploit.
We implemented randomized transaction execution within user-specified privacy windows. Users set their desired privacy level, and actual execution timing falls within a randomized window - between half and full duration. This randomization allows transactions to blend with other protocol activity naturally. Longer privacy levels produce stronger guarantees by allowing transactions to mix with more pool activity.
Ready when you are
Let's build something that matters in Web3. Whether you need a prototype next week or a full product launch, we've got the skills to make it happen.
