Pricing Engine

Vorepo's pricing engine continuously checks whether each ticker's price reflects its underlying GitHub activity (stars, commits, contributors, buzz). When a ticker drifts too far from its GitHub-implied fair value, the engine takes a small position through the same bonding curve users use — buying undervalued tickers, selling overvalued ones. Every trade is fully public.

• Trades randomly (Poisson-distributed timing, randomized size) — no predictable pattern
• Skips tickers whose GitHub momentum is collapsing (>10% drop in 7 days)
• Skips tickers with stale data (no metric refresh in 24h)
• Hard per-ticker stop-loss: stops engaging if cumulative P&L drops below threshold
• Trades through the same bonding curve as everyone — no special access, no priority

Every engine trade appears in the public trades table with buyer_id IS NULL (when engine bought) or seller_id IS NULL (when engine sold), plus an entry in the table below. Users always have priority — engine activity is rate-limited, randomized, and bounded.

User trades never go through the engine — they execute against the bonding curve directly. The engine is just another participant in the same curve. Users who spot GitHub trends earlier than the engine simply earn from the price catch-up.