Quick Start

Deploy your first FDC Verifier Node and attest to a sovereign data source.

STAGE 1.1

The Sovereign Source Integration

The first step is to configure your verifier node to listen to trusted institutional data sources. In this example, we will target the Federal Register API and SEC.gov to fetch high-impact regulatory filings.

1. Start the Backend Service

Ensure the ObsiFlow backend is running on port 8000. The backend provides all API endpoints.

# Navigate to backend directory
cd obsiflow-backend/python-service
# Install dependencies
pip install -r requirements.txt
# Run the service
uvicorn app.main:app --reload --port 8000

2. Add a User Wallet

POST http://localhost:8000/api/v1/users/user123/wallets Content-Type: application/json { "wallet_address": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb", "metadata": { "label": "My Trading Wallet" } }

warningMainnet Reality

Mainnet FDC requires whitelisted URLs. For this demo, we deploy a custom FDC Verifier Node on Coston2 Testnet that permits these specific URL patterns.

STAGE 1.2

The Web2Json Attestation Cycle

Once data is detected, the node constructs an Attestation Request using the IWeb2JsonVerifier interface. This process respects the ~90s Voting Round (Epoch) of the Flare Network.

3. Generate a Signal

Generate a trading signal with automatic FDC verification for wallet addresses.

POST http://localhost:8000/api/v1/signal/generate Content-Type: application/json { "user_id": "user123", "event_id": "whale_tx_001", "event_data": { "type": "whale_transaction", "wallet_address": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb", "amount": "1000000", "token": "ETH", "value_usd": 2500000 }, "triggering_wallet_address": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb" } # Response includes: # - Immediate signal (Phase 1) with strategy # - FDC verification status (pending) # - Pub/sub channels for real-time updates

4. Connect via WebSocket

Receive real-time signal notifications via WebSocket.

// JavaScript example const ws = new WebSocket('ws://localhost:8000/ws/user123'); ws.onmessage = (event) => { const signal = JSON.parse(event.data); console.log('New signal:', signal); // Handle signal: immediate, verified, etc. };

infoLatency Note

We do not claim "High Frequency Trading" speeds for fetching. We claim "Macro-Event Verification". A 90-second delay is negligible for a regulatory shift that impacts the market for months.