# Roadmap

#### **ULDM v3.5 with AI/ML**

* Integrate ML models to optimize trade routes in real time
* Predict slippage, gas costs, bridge risks, and trade reliability
* Use historical and live data to train routing optimizing AI models
* Begin transition toward partial automation (shadow mode → active)

#### Limit Orders

* Full limit order support with on-chain settlement
* Partial fill support
* Gas abstraction and relayer support for ease of use
* Modular architecture to plug into ULDM routing

#### Earn 2.0

* Incentivized liquidity provisioning with dual-purpose rewards
* LP token staking with IL-mitigating mechanics
* Designed for long-term depth and stickier liquidity
* Integrated analytics to track performance and rewards

#### Custom Liquidity Pools

* Deploy native Unizen pools for top-traded assets
* Ultra-efficient routing and deep liquidity pairing with ULDM
* Custom curves optimized for specific trade flows
* Built for ZCX, ETH, BTC, stablecoins, and other top performing assets

#### TWAP Orders

* Time-weighted average price orders for large trades
* Split execution across defined time windows
* Dynamic sizing based on liquidity depth and volatility
* Integrated fallback logic in case of sharp market moves

#### Unizen DAO (Powered by DEXE)

* Deployed governance layer using DEXE’s DAO framework
* Token holders can propose and vote on protocol changes

#### **Multi-Regional Kubernetes Deployment**

* Deploy and manage Kubernetes clusters in multiple regions (APAC, US, EU)
* Reduce response times for users in latency-sensitive regions
* Enable geo-based routing and failover
* Use cloud-native tools (e.g., GKE multi-cluster, AWS EKS, Cloudflare) to manage traffic

#### **Scalability Improvements**

* Auto-scaling based on traffic spikes and region-specific demand
* Isolate workloads per region to reduce cross-zone latency
* Optimize container scheduling and caching per region
* Shared global state where needed (e.g., Redis, DBs with read replicas)

#### **Reliability Enhancements**

* Active-active setup with health checks and failover
* Region-level fault isolation to reduce blast radius
* Real-time monitoring and observability using Prometheus + Grafana
* Log and trace aggregation for faster debugging

#### More (Not Yet Announced)

* Ongoing R\&D
* Tactical innovations aligned with protocol and ecosystem strategy\ <br>

### Ongoing Priorities

#### More Networks

* EVM-first: Monad, Linea, Scroll, Mode, ZetaChain, zkSync, Blast, Polygon zkEVM
* Consider high-TVL non-EVMs if safe bridging and aggregator support exists
* Native ZenChain routing once mainnet is live

#### More Interoperability Providers

* Expand bridge coverage: CCIP, Squid, Across and StargateV2
* Evaluate bridge risk dynamically with scoring models
* Integrate bridges deeper into ULDM for optimized cross-chain flow

#### More Solvers

* Deploy Unizen as solver on major intent-based architectures
* Follow developments in SUAVE, Anoma, Essential, etc.
* Build internal solver engine aligned with ULDM logic
* Focus on gas efficiency, bundling, and MEV resistance

#### More Liquidity

* Onboard more DEXs and PMMs per network weekly
* Partner with LPs, protocols, and treasuries to deepen liquidity
* Monitor and reroute around thin or volatile pools
* Use AI to detect anomalies and shift volume to safer paths

#### **Global Rollout of Performance-Critical Services**

* Gradual expansion of ULDM routing, analytics, and limit order services into regional clusters
* Shared memory/cache coordination for consistency across regions
* Prioritize services handling live routing, trade execution, and bridge interactions

#### **Improved Latency**

* Monitor regional response times and adjust routing rules
* Benchmark API latencies under real-world trade scenarios
* Optimize DNS and CDN config for faster edge resolution

<br>


---

# 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://docs.unizen.io/other/roadmap.md?ask=<question>
```

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.