# FAQ ## FAQ #### **Who is the team behind LayerAkira?** * LayerAkira is built by a team who have expertise in building robust and ultra-low latency systems #### **What is your roadmap?** * We are currently developing LayerAkira as an infrastructure layer and a basic spot DEX. * V1 will: * allow users to trade spot assets via a simple swap DEX interface * allow dApps and consumer facing products to plug into our orderbook and access our liquidity via our sdk which interacts with our backend. * After V1: * We will develop the UI to include a full view of our order books and include better trading UI * Cover assets * Create taker and maker programs to promote more activity on LayerAkira * Immediate roadmap: * launch LayerAkira v1 DEX for instant simple swaps * work to secure integrations with existing dApps on Starknet * 6-12 month roadmap: launch LayerAkira v2 with: * more asset pairs * full visibility of the order book with candle charts * limit orders * deposits + withdrawals for better fees; and * a CEX like trading experience * 12+ month * incentivse products to build on top of LayerAkira * expand to cover perpetuals markets * build our own L3 to allow for a fully onchain order book model #### **How do CLOBs compare to Uniswap v3 and v4?** * The AMM v3 and v4 models are iterations to the original AMM model that addresses the issues of slippage and capital efficiency issues in the traditional AMM model. V3 allowed LPs to choose specific price ranges within which their assets could be used and introduced multiple fee tiers to better accommodate different risk levels and trading volumes and V4 will allow for greater customisation, more efficient transaction routing and reduce gas costs * AMMs are ideal for trading assets with lower liquidity as it allows for flexible price discovery. However, CLOBS are still superior in terms of being able to trade at very specific price points. As liquidity on the order book is made up of buy and sell limit orders, the price is concentrated around certain ranges, meaning narrower spreads. This is ideal for fat-tail assets --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://layer-akira.gitbook.io/layerakira-documentation/about/faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.