← ALL WORK
Data & analytics

Crypto Prediction

Market signals with a risk-aware perspective.

A multi-wallet prediction-market platform with a Rust execution engine, risk controls, replay and a Nuxt dashboard.

Vue.jsNuxtRustTypeScriptPostgreSQL
MY ROLE

Product & Full-Stack Engineering

BUILT FOR

Users exploring market information and analytical signals

01 / THE CONTEXT

Market signals with a risk-aware perspective.

Market analysis depends on aligning incoming data, derived signals and risk context. A useful interface needs more than a stream of prices: it needs a coherent way to inspect signals, account exposure and execution state.

What I built

I built a Nuxt dashboard over an Axum REST and WebSocket API, a Tokio actor-based execution engine and PostgreSQL/TimescaleDB storage. Venue adapters, deterministic strategy components, wallet actors and replay tools have distinct responsibilities.

02 / PRODUCT CAPABILITIES
01

Market-data workflows

Order-book and fair-value components feed a deterministic strategy core. Live and replay sources share clock and event abstractions for investigation and backtesting.

02

Risk-oriented views

Account, user, venue and global kill controls govern wallet actors. Routing applies allocation weights and cross-account self-match checks before venue execution.

03

Typed system boundaries

Wallet actors own account lifecycle state and reconcile after reconnection. An Axum API exposes application state to the Nuxt dashboard through REST and WebSocket interfaces.

Under the surface.

Follow a real product workflow through its application boundaries. Select any step to explore the implementation.

ENGINEERING IN MOTION

Market events become controlled execution intents.

A Rust actor-based engine separates deterministic strategy, risk admission and venue-specific order handling.

STEP 01 / LIVE / REPLAY

Market source

LiveSource and ReplaySource sit behind a common source abstraction. LiveClock and SimClock allow the engine to operate against real or simulated time.

WHY IT MATTERS

Identical source and clock seams make replay meaningful. Risk controls and wallet ownership remain explicit even when multiple venues and accounts share one engine.

Conceptual flow based on the implementation. Animated connections illustrate data movement, not live traffic.

04 / ENGINEERING JUDGMENT

Built around the constraints.

Separate data processing from visualization. Present analytical information with its risk context, without implying guaranteed trading performance.

Discuss the engineering ↗

Keep exploring.

Next project ↗