Skip to main content

Real-Time On-Chain Sync & Transparency

Prizee Raffle features an automated blockchain synchronization and event indexing engine that guarantees zero-drop transaction reliability and real-time state tracking across the Arc Network.

Why On-Chain Synchronization Matters​

In decentralized gaming and financial applications, transactions happen asynchronously across blockchain nodes. When users buy tickets, swap tokens, or creators seed escrow on-chain, instant and dependable state updates are critical.

The synchronization engine ensures:

  1. Zero-Drop Ticket Guarantee: Even if a user closes their browser or loses internet connection immediately after confirming a transaction, the protocol independently verifies the receipt on the blockchain and credits the ticket to their inventory.
  2. Autonomous Round State Progression: Verifies deposit logs from the CircleSmartEscrow contract and automatically transitions campaigns from funding to live without manual human intervention.
  3. Double-Spend & Replay Protection: Validates transaction hashes, block numbers, and token transfer event topics against Arc Network consensus.

Synchronization Architecture​

Reliability Invariants​

The protocol incorporates multiple layers of resilience:

  • Automatic Network Reconnection: If public RPC nodes experience temporary latency, the sync engine applies automated retry schedules to guarantee continuous tracking.
  • Pending Transaction Reconciliation: Unconfirmed transactions are continuously tracked until final cryptographic confirmation on Arc Network is achieved.
  • Public Auditability: Every indexed event links directly to the immutable transaction hash on the ArcScan Explorer.
  • Activity list: GET /api/me/activity returns Mongo immediately and syncs Arcscan in the background (TTL ~8s). App send/swap/bridge rows are written on success. Inbound receives from Arcscan also create inbox notices.
  • Inbox: Polls about every 4s; opening the bell refetches. Balance inbound poll is ~3s. Telegram getUpdates 502 / fetch failed are Telegram/network blips, not lost Prizee data.