Crypto trading involves substantial risk. PoeOS does not guarantee profits. PoeOS is research tooling: it reports on-chain data and never predicts prices or guarantees outcomes.

Documentation

How PoeOS is put together, how to use each module, and what the platform will never claim.

5 min

Quickstart

Connect a wallet in read-only mode, pick a network and run your first simulation in under five minutes.

10 min

Generate a contract

Configure an ERC-20 in the Developer Hub, review the trust assumptions and export a testing scaffold.

8 min

Simulate a route

Set a minimum net-profit floor, compare venues and read the confidence score correctly.

4 min

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

Token IntelligenceNetwork HealthAI ResearchDeveloper & APIService statusPlans & usage

Support

Documentation gaps and integration questions go through the support channel listed on the Security page. Support will never ask for keys, seed phrases or remote access to your machine.

Alchemy wallet setup (operators)

PoeOS reads chain data through your own Alchemy account. Every step below runs on a machine you control or in your deployment settings — never in this browser tab. PoeOS never runs your login, never reads your CLI session, and never asks for a private key or seed phrase.

  1. 1. Install the Alchemy CLI on a trusted machine: npm i -g @alchemy/cli@latest
  2. 2. Authenticate the CLI: alchemy auth. On a remote box or over SSH — where no browser can open — use alchemy auth login --device-code and complete the device-code prompt from a machine you trust. The session is stored on that machine only.
  3. 3. Connect an Agent Wallet when you want automated signing: alchemy wallet connect --mode session issues a scoped session for the agent, while alchemy wallet connect --mode local keeps signing on your local machine. Agent Wallet private keys are never exposed to the agent or the CLI; wallets are created and revoked from the Alchemy dashboard.
  4. 4. Configure the server secrets in Project Settings → Secrets: ALCHEMY_API_KEY (required — RPC and data reads), ALCHEMY_WALLET_API_KEY (optional — Smart Wallets) and ALCHEMY_GAS_POLICY_ID (optional — gas sponsorship). Secrets are server-only; they are never bundled into the client and never logged.
  5. 5. Restart PoeOS so the server process picks up the new secrets. On Lovable Cloud this happens automatically after a secret is saved; self-hosted deployments need a redeploy or process restart.
  6. 6. Verify the connection — open Wallets & treasury → Setup & security and press Verify connection. PoeOS makes a real authenticated call to Alchemy and reports whether the key was accepted, plus live latency and block height for Ethereum mainnet, Base, Arbitrum One, Optimism and Solana mainnet. A rejected key is reported as such instead of silently falling back.
  7. 7. Create or connect a wallet — on the EVM tab, connect a browser wallet and sign the ownership challenge to link it, or provision an Alchemy-custodied smart account from the managed-wallet card (requires ALCHEMY_WALLET_API_KEY and POEOS_MANAGED_WALLETS_ENABLED=true). Once linked, balances and transfer activity are read live through your Alchemy endpoints.

Live transaction execution stays disabled by default. Managed Solana signing is marked integration-required until a supported Solana signer is configured; Solana remains read-only.

FAQ