Sidiora stewards liquidity as a shared network resource. Rather than wiring capital into one exchange or pool at a time, Paxeer’s community funding planes are projected into AMMs, orderbooks, and structured surfaces as dynamic liquidity envelopes.
Builders and protocols do not hire a desk; they connect to Paxeer. Once integrated, their markets become eligible for protocol-governed liquidity sourced from ETH/OP-backed pools and collateralized PAX, sized and rebalanced by the network’s risk engine instead of manual seats on a trading floor.
Step 1 · Network liquidity pools
Paxeer maintains pooled liquidity denominated in ETH, OP, and PAX-backed reserves. Sidiora operates these as network-level capital planes rather than per-venue accounts, exposing a single fungible reservoir for all Paxeer-connected markets.
Step 2 · Liquidity risk envelopes
The risk plane wraps pools in utilization caps, venue-specific loss limits, and drawdown tolerances. These envelopes determine how much depth Paxeer will project into any venue or market before capital is throttled or redirected.
Step 3 · Routing into venues
A routing layer projects envelopes into AMMs, orderbooks, and structured payoff surfaces. Allocation respects venue quality, slippage, and utilization, ensuring Paxeer-owned liquidity shows up where it drives the most network utility.
Step 4 · Dynamic rebalancing
Utilization, realized pnl, and venue health signals continuously rebalance allocations across markets and venues. Underperforming deployments are pulled back toward the reservoir; high-utility deployments are scaled within their envelope.
Step 5 · Surfaces that see the liquidity
Protocols, wallets, and agents integrated with Paxeer experience deep, protocol-governed liquidity without negotiating bilateral LP deals. Sidiora operates the projection layer internally; the ecosystem just sees deterministic depth and tight execution.