Quick update from the @dango team. We have recently focused effort on two fronts: onboarding liquidity, and improving the infrastructure. Growing liquidity is genuinely difficult in today's market. Without it, it's difficult to ship new features, such as advanced order types and new asset listings. We have made solid progress on this front, reaching preliminary agreements with multiple top-tier market makers, who will bring their own liquidity to Dango, as well as managing the DLP vault. As we are speaking, the deals are going through the lawyers and the compliance departments, which is out of our control and can take a frustratingly long time. However, we believe we're seeing the light at the end of the tunnel, and will have good news to share soon. On the infrastructure front, we have shipped two changes: 1. A reduction of block time from ~350 ms to ~225 ms, thanks to a number of efficiency improvements in the code. We can go even lower, with the eventual goal of sub-100 ms, matching the industry leader (Hyperliquid), but we take it step-by-step. With this, expect a more responsive webapp, and lower latency for algo trading. 2. An improved API. We have split the API into two: a "Live API" that serve most up-to-date, continunously streaming data, with low latency, suitable for bot trading; an "Archive API" that serves historical data and statistics, suitable for block explorer and data analysis. Additionally, we're switching the API protocol from GraphQL to REST (for one-time requests) and WebSocket (for streaming and interactive sessions), which most algo traders find easier to work with. The GraphQL API may be deprecated in the future. Check the latest API docs here: docs.dango.exchange/perps/8-….