crypto technology partners

onchain
Joined March 2024
We’re thrilled to build Portfolio Manager alongside @1inch. Aqua lets liquidity providers put capital across multiple strategies. Keeping that inventory balanced is the hard part. Portfolio Manager holds your target exposure as price and flow move - no liquidity migration every time the book shifts. Built on Aqua. More soon.
2
6
228
DAOs still run critical ops completely in the open. Hiding token balances isn’t enough. The real challenge is executing business logic on confidential state without moving execution off-chain. We’re using @zama’s FHEVM to build a suite of confidential DAO products. Fully homomorphic encryption allows smart contracts to process private inputs directly on-chain, shielding treasury operations without sacrificing verifiability. If DAOs are going to manage real balance sheets, privacy needs to be native to their architecture. Stay tuned!
8
261
cowpy is the Python SDK for @CoWSwap interactions. It gives builders native tools for MEV protected trading, order book management, smart contract execution, subgraph queries, and multi-chain support. Usage across the last six months: • $18M in volume • 27K PyPI downloads • 8.8K orders across 6 chains Get started with: pip install cowdao-cowpy Explore the codebase and documentation: github.com/cowdao-grants/cow…
5
23
686
One of CoW's best features is now available to everyone 🐮 TWAP order discovery on @CoWSwap is powered by the Programmatic Orders API we built and open-sourced to handle programmatic order flows and conditional execution. Great to see core infrastructure we shipped running in production.
For years, one of DeFi's best-kept secrets sat behind a locked door. 🔒 TWAP orders. Advanced traders swore by them. Everyone else needed a Safe, a custom fallback handler, and an afternoon to spare. Today, the door comes off its hinges. TWAP is open to every wallet. 🧵
5
9
35
1,444
Did you know you can run the entire @CoWSwap stack locally offline? Until now, testing autopilot or driver changes meant relying on remote testnets, live RPCs, or mocked assumptions. The CoW Playground Offline Development Mode packages the full environment: • Local Anvil node with deterministic CREATE2 contract deployments • Pre-seeded Uniswap V2 liquidity, test tokens, and periphery contracts • Local CoW Swap UI wired directly to Anvil for end-to-end testing One-command startup. Zero external RPC dependencies. Real settlement execution on local state. Build and test locally: github.com/cowdao-grants/off…
1
10
402
Querying EVM history has always been painful. @typedarray and the @ponder_sh team proposed a real fix at the protocol level with five new JSON-RPC query methods: • eth_queryBlocks • eth_queryLogs • eth_queryTraces • eth_queryTransfers • eth_queryTransactions Instead of dumping raw blocks and stitching state client-side, the spec adds server-side filtering, field projection, and relation joins in a single call. We rely heavily on Ponder across our infrastructure. They’ve consistently pushed EVM indexing forward, and moving these primitives directly into the RPC standard fixes the problem where it actually belongs. Hope to see other EVM chains look closely into this.
1
1
8
213
Seeing @fomo users getting sandwiched on L2s brings back memories. One of the first things we built for @CoWSwap was the "Have I Been MEV'd?" bot. We built @mevscanner so users could measure how much they lost to MEV bots instead of wondering where their slippage went. Unfortunately, some things in crypto never change: route through batch auctions or keep paying the searcher taxes.
3
14
288
🥉 We scored 3rd place in the @zama developer program with our dark pool! Started with buybacks, now designing production infrastructure for confidential DAO ops: payments, vesting, and treasury execution on FHEVM. xitter.cf/i/status/2074573272033…
DeFi buybacks leak everything: budget, schedule, every fill, all public. TradFi fixed this in the 80s with dark pools. We spent the last few days on our first FHE project, a dark pool for protocol buybacks, built on @zama FHEVM. 🧵
1
16
762
Becoming a full @CoWSwap solver comes with legal, capital, and infra hurdles only well-resourced teams can clear today. CoW BYOS changes that. We're building a meta-solver so teams can plug routing strategies straight into batch auctions without the overhead.
1
7
20
577
Project after project, @CoWSwap trusts us with bigger challenges. Honored to execute BYOS and keep innovating batch auction infrastructure snapshot.org/#/s:cowgrants.e…
2
7
577
DeFi buybacks leak everything: budget, schedule, every fill, all public. TradFi fixed this in the 80s with dark pools. We spent the last few days on our first FHE project, a dark pool for protocol buybacks, built on @zama FHEVM. 🧵
1
1
2
8
3,091
5/ It's a PoC for now: fills are FCFS not pro-rata, treasury solvency isn't onchain, the payment leg is a mock USDT. Next up: pro-rata, encrypted limit prices, real stablecoins. We're excited to keep building on FHE and take this from PoC to a real product
1
3
156
6/ Live on Sepolia: 🖥️ Demo: confidential-buybacks.vercel… 📜 Code: github.com/bleu/confidential… Built with @zama FHEVM + @OpenZeppelin ERC-7984 confidential tokens. Our first FHE experiment, but definitely not the last. #ZamaDeveloperProgram
2
152
3/ ConfidentialBuybacks is that dark pool. The treasury buys straight from holders in sealed epochs, with budget, offers, and fills encrypted onchain. The whole match happens on encrypted data, no decryption at any point. An encrypted budget draws down first come first served, and once it's gone, later offers silently fill zero.
1
46
4/ Confidential can't mean unaccountable. 5 min after an epoch closes, anyone can trigger public disclosure of the total. Private during execution, public afterwards. The surprising part of building on FHEVM: it's basically Solidity. The hard stuff (input proofs, threshold KMS, relayer) is infra you inherit, not code you write.
35