Documentation
How POEOS is put together, how to use each module, and what the platform will never claim.
Quickstart
Connect a wallet in read-only mode, pick a network and run your first simulation in under five minutes.
Generate a contract
Configure an ERC-20 in the Developer Hub, review the trust assumptions and export a testing scaffold.
Simulate a route
Set a minimum net-profit floor, compare venues and read the confidence score correctly.
Wallet & permissions
How POEOS reads addresses, when it requests signatures and what it never asks for.
Architecture
Built so that demo adapters can be replaced by live ones module by module.
Presentation layer
Route-level pages compose shared primitives (glass cards, stat tiles, charts, state components). No page holds business logic.
Data adapters
Every dataset is a typed export shaped like its eventual live source. Swap one export at a time — indexer, aggregator, RPC, bot engine.
Network registry
One module defines chain IDs, RPC endpoints, cost models and family (EVM/SVM). Strategy modules read from it rather than hard-coding chains.
Wallet session
A context with a stable shape: status, address, network, credits. Replace the demo connector with wagmi/viem or wallet-adapter without touching consumers.
Server boundary
Live keys, provider secrets and aggregator credentials belong in server functions only. Nothing sensitive is ever read in the browser.
Jump to a module
Support