Node & Client Communication

Juno follows a client-first architecture. The frontend handles all rendering and state logic. The backend (Node or FastAPI) exposes minimal endpoints for signal generation, transaction tracing, and token risk evaluation.

There is no persistent socket layer. All communication is request-response over HTTP.

Standard Flow

• Client connects wallet

• Local session state is populated (tokens, filters, memory)

• On refresh or user action, client hits /analyze, /wallet, or /risk endpoints

• Backend parses address, fetches relevant data, returns scoped JSON

• Client stores result in memory and updates UI or prompts

No data is stored server-side. No auth is required beyond wallet signature (optional). Payloads are lightweight — compressed token lists, reduced transaction logs, and flattened risk flags.

Performance Notes

• All calls are stateless

• Timeout threshold is low (2–5s max)

• Retry logic handled on client if enabled

• No streaming, polling, or live socket feeds, updates are manual or event-driven

The client initiates all logic. The node processes data and returns a static payload. No orchestration layer, no event bus, no cache unless explicitly configured.

Clean, portable, easy to reason about.