Clover

Clover OS $CLOVER is now live on @base! Official Contract Address: 0x9ddc881d1ecdfcfe01a62c4a2531903dbbf1ab07 Clover OS brings private finance to Base, Ethereum, and Solana. Private execution that never hits public mempools, shielded transfers via on-chain notes, encrypted FHE vaults on Ethereum Mainnet, identity-aware policy controls, and offline device-to-device transfers on iPhone (IOS) first, via the upcoming mobile app. The private operating system for digital finance.

12/ If you're building in private DeFi, agentic finance, or sealed-state systems, we'd love to compare notes.

11/ Things we're still working through: - Scheduler reliability under chain reorgs. How to retry a private DCA across a reorg boundary without revealing that we re-tried, and how to expire stale plans when prices have moved beyond simulated tolerance. - FHE proof generation costs at scale. Comparisons under Clover FHE are non-trivial today; batching predicate evaluation across users and pipelining proof gen against the sealed-state gateway so watcher latency stays inside the trigger window is open work. - The policy DSL itself. A small, statically typed, FHE-friendly grammar (predicates need to compile to FHE-evaluable circuits) that the LLM can target reliably and that we can audit by hand. - The threshold decryption topology. v1 runs against an external FHE coprocessor and its threshold network; the trust delegation is explicit. Scoping a Clover-operated MPC layer with user-held shares is on the v2 roadmap.

1/ We're currently developing the Clover Strategist Agent. An AI agent that designs, simulates, and executes private DeFi strategies on a user's behalf, on top of Clover's existing privacy stack. A thread on what v1 will handle, and how it stays private. ↓

Clover's shielded pool never stores who received a transfer. The only things recorded on-chain: - A commitment (hash of amount + randomness + owner-key) - A nullifier (when something gets spent) - A Merkle root (a fingerprint of all current commitments) The recipient's wallet address never appears in storage. Never appears in events. Never appears in the proof verification. Why? Because privacy is not selective. If the recipient's address shows up anywhere, the entire flow can be traced. Every "show this only to me" exception becomes a vulnerability over a long enough timeline. Total absence is the only design that survives sustained adversarial scanning. cloveros.io/dashboard/shie…

Clover's FHE Vault stores balances as euint64 (64-bit encrypted integers), not the uint256 every standard Ethereum contract uses. First reaction: "that is a hard cap on how much I can hold." It is not. euint64 holds up to 1.84 × 10^19 of any unit - 18.4 ETH expressed in wei. Plenty for any real treasury operation. The real reason is performance. FHE operations scale with bit-width, non-linearly. A euint256 multiplication is dramatically slower than euint64. For balance accounting in a sensible range, euint64 hits the optimal point on the speed-vs-range curve. Engineering is choosing the constant that maximizes the use case, not the constant that looks impressive.

Why does Clover's shielded pool only accept 0.01, 0.1, or 1 ETH deposits? Privacy depends on uniformity. If users could deposit any amount, every deposit would be a fingerprint. 0.04713 ETH is Alice. 0.62 ETH is Bob. Withdrawing your exact deposit amount reveals which one you made. Fixed tiers force every deposit into the same shape. No distinguisher. No leak. The cost is UX. The benefit is anonymity that actually works at scale. Every serious shielded pool ships this way - and most people do not realize why.

Why does Clover use Poseidon hash and not keccak256 like every other Ethereum contract? Because Poseidon was designed to be efficient inside zk-SNARK circuits. A keccak256 call inside a circuit costs ~150,000 constraints. Poseidon costs ~250. That is a ~600x performance difference. Without Poseidon, every shielded transfer would take 10+ seconds to generate a proof on a phone. With it, under a second. Privacy is only useful if it is fast enough to actually use. The choice of hash function is a UX decision disguised as a cryptography decision.

Fact most people miss: Every wallet you have ever sent crypto from is now in a public database that AI companies are training on. Your timing patterns. Your protocols. Your counterparties. All of it. The data is already collected. It is being modeled right now. Privacy stops the next decade of this. Did you know: Public mempools leak your transaction to bots ~12 seconds before it settles. They can copy it, front-run it, sandwich it, or simply file it for later analysis. $1.5B was extracted from retail this way last year. Clover routes you off the public mempool by default.

The wait ends tonight at 11pm UTC. Clover OS Mobile v1.0.0 ships - the first time in crypto history that you can pay someone with no internet, no middleman, and no metadata leak. Sign and seal the transfer on your iPhone. Hand it off over QR. Settle on Base, Ethereum, or HyperEVM whenever either device reconnects. Months of building. A final week of intense testing. Zero shortcuts. 11pm UTC. Set your alarm. The countdown is on. cloveros.io/clover-setup-g…

First deposit just settled into the Clover Shielded Pool on HyperEVM. What the chain sees: a 0.01 HYPE tier, a commitment hash, a new Merkle root. What the chain does not see: who owns the note, who will spend it, where it will go. Real privacy on $HYPE, verifiable in 60 seconds: #events" target="_blank" rel="nofollow noopener">hyperevmscan.io/address/0xb541…

Clover x HyperLiquid The Clover Shielded Pool is now live on HyperEVM Mainnet. The same zk-SNARK privacy stack already running on Base and Ethereum - PoseidonT3 Merkle library, Groth16 verifier, shielded verifier wrapper, and the pool itself - to HyperLiquid's EVM execution layer. All four contracts are verified on hyperevmscan.io and deployed from the same admin wallet that owns our Mainnet and Base pools. Why HyperEVM? The HyperLiquid ecosystem has earned its momentum. $HYPE is one of the rare new L1 economies where adoption is real, the order book is deep, the community is engaged, and the technical bar is high. The team has built something that genuinely works at scale. Privacy belongs there. Traders moving size on HyperLiquid have the most to gain from on-chain privacy primitives - sealed amounts, untraceable transfers, no leaked treasury. We are bringing the same fail-closed shielded pool we run on Base and Ethereum to that surface. Verified contracts on HyperEVM: Pool: hyperevmscan.io/address/0xb541… Verifier: hyperevmscan.io/address/0xd771… Groth16: hyperevmscan.io/address/0x7a72… Poseidon: hyperevmscan.io/address/0xe4e2… Live now in the Clover dashboard: cloveros.io/dashboard/shie… The Clover Shielded Pool now operates on three chains - Base, Ethereum, and HyperEVM. Same architecture. Same owner. Same privacy guarantees.