Given recent events, I think now might be a good time for someone to launch a dark pool perp DEX. I have always been puzzled with the fact that everyone can see your orders in real-time on a DEX. The problem is worse on a perp DEX where there are liquidations. Even with a CEX order book, where orders aren't linked to a specific individual, if you're looking to purchase $1 billion worth of a coin, you generally wouldn't want others to notice your order until it's completed. Otherwise, people might try to buy before you, effectively front-running you. In the case of a DEX, this can lead to MEV attacks. This results in increased slippage, worse prices, and higher costs for you. For this reason, the large traders in TradFi use dark pools, which are often 10 times bigger than the “lit pools" (ie, normal orderbooks). For perps (or futures), it is even more important to not let others know/see your orders. If others can see your liquidation point, they could try to push the market to liquidate you. Even if you got a billion dollars, others can gang up on you. This was possibly what we have seen recently. The counter argument I have seen is that being more transparent allows market makers to absorb your large orders. This is possibly true. I won’t get into an argument on which is right or wrong. Different traders may prefer different types of markets. Now might be a good opportunity for someone to launch an on-chain dark pool style DEX perps, either by not showing the orderbook, or even better not showing deposits into smart contracts at all, or until much later. This should be doable with ZK or similar encryptions. Just a Sunday idea. If you are building such a project, feel free to reach me on reachme.io/@cz_binance. No guarantees I will invest, or even reply. 🙏

Just open sourced QED's WebGPU accelerated poseidon2 merkle hashing library for the browser. It's over 27x faster than CPU 🎉 Code Live Benchmark Link: github.com/QEDProtocol/posei…

We are happy to announce that Dapen IDE now supports compiling #TypeScript Smart Contracts to Miden VM assembly 🎉 Dapen is the first high level language compiler to support @0xPolygonMiden, and we hope to see more projects take advantage of the STARK prover from the Miden team!

QED's team is hard at work optimizing our winterfell verifier, and is excited to start on our verifier for @StarkWareLtd Stone proofs state integration with Cairo via #Dapen! Done: -✅ JavaScript/TypeScript -✅ Python -✅ Miden VM Roadmap: -⌛️Solidity -⌛️Cairo -⌛️Rust -⌛️C

Check out the latest post on the QED blog where we design a horizontally scalable blockchain from scratch: qedprotocol.com/blog/posts/a… It's an epic deep dive, so get your popcorn ready 🍿!

QED #WordOfTheDay: Covenant Covenants are used on QED for cross user interactions, token transfers, order books and more! With covenants, smart contracts can require that an additional transaction is executed before a transaction chain proof can be submitted to the network.

🏠 Day 10 @ W3BxSui Hackerhouse: Buckle up students! 🎓 Meet CEO and Founder Carter Jack Feldman @cmpeq , the brain behind @QEDProtocol . 🌟 Discover Local Proving & PARTH: Pioneering scalable blockchains for a trustless internet. 🌐 Join us in person or on Zoom for this insightful adventure! 🚀 #Hackerhouse #Web3 #QEDprotocol