CHANGELOG

What's new

Every release that's shipped to production, in plain language.

Earnqo v1.0.0 — Public launch

v1.0.0 · May 4, 2026

Earnqo v1.0.0 — Public launch

The first public release of Earnqo. Sign in, complete partner offers or surveys, enter raffles or scratch cards, and cash out in PayPal, USDT, or 200+ gift cards. Every micro-transaction lands in a double-entry ledger you can audit; every random draw is verifiable via a published seed-chain.

What ships at launch

Earning

  • Offer wall — partner offers, surveys, app trials. Credits land on completion, reversals are explicit when a provider rolls back.
  • Raffles — pay points for tickets in a tamper-evident hash chain; winners drawn against a beacon-seeded RNG. Past results stay publicly verifiable forever.
  • Scratch cards — server-authoritative odds; results decided before the cosmetic reveal animates.
  • Daily bonus + streak — claim once per UTC day, multiplier rises through the week, resets at 7.
  • Coin drops — admin-broadcast windows; first claimers split a capped pool with Redis-atomic claim.

Cashing out

  • 8 payout methods at launch — PayPal, USDT-TRC20, Skrill, Payeer, Perfect Money, M-Pesa, MTN Mobile Money, and 200+ retailer gift cards via Tremendous.
  • 3-step withdrawal — pick method → enter amount → confirm. Funds reserve to a per-user pending account before any provider call, then release on confirmation.
  • KYC gate — automatic above the per-method threshold, manual review for unusually large requests, audit log on every state change.

Account + safety

  • Email-and-password signup with optional magic link, email OTP, and OAuth providers (Google, Apple, Discord). 30-second flow; KYC is deferred until you want to withdraw above the small-amount threshold.
  • Two-factor authentication — TOTP via any authenticator app; 10 single-use backup codes; trusted-device support keeps the challenge to once per device.
  • Session management — see every active sign-in, revoke individually or all-at-once, with reuse detection on rotated tokens that kills the whole device family on replay.
  • Account deletion — request once, 30-day cancellation window, finalised by a nightly worker. Cashable balance must be withdrawn before the date — the danger-zone copy is explicit about it.
  • Data export — GDPR/CCPA-compliant download of every personal field we hold, fanned out as a JSON bundle.

Compliance + transparency

  • Six locales — English, Arabic, Russian, Spanish, Portuguese, Turkish. The interface flips to RTL for Arabic. Email templates follow the user's chosen language.
  • Versioned legal documents — Terms, Privacy, Cookie Policy, Responsible Play, Refund Policy. Admin can publish a new version; users see a re-accept prompt on the next sign-in if it bumps.
  • Cookie consent banner — EU/UK-aware. Choices land in an audited consent_log for compliance review.
  • Age gate — 18+ minimum at signup, validated server-side against the dynamic auth.signup_min_age_years setting.
  • Public status page at /status — operational state and admin-authored message, locale-resolved.

Trust signals

  • Provably-fair raffles — winner picked from a published seed chain that anyone can replay against the beacon source.
  • Double-entry ledger — every microcent has matching debits + credits. Internal accounts (asset_user_balance, asset_pending_payout, revenue_fees, expense_giveaways, …) reconcile to zero across the platform.
  • Idempotency-keyed write paths — withdrawals, raffle ticket buys, and claims accept a client-supplied UUID so a sincere retry returns the same response instead of double-debiting.

Performance + reliability

  • Hot-path read caching — payout-methods config, dynamic settings, and other admin-toggleable surfaces serve from a 60-second in-process + Redis cache. Admin writes invalidate immediately, not after the TTL.
  • Composite + partial DB indexes — inbox feed, support thread, and per-raffle ownership counts all use indexes that match the WHERE+ORDER BY exactly.
  • Backpressure-aware queues — every BullMQ queue has a per-workload concurrency setting, retention caps to keep Redis bounded, and a monitor worker that pages on >100 failed jobs or

    5,000 waiting jobs.

Coming next

  • Mobile apps (iOS + Android, sharing the i18n message store)
  • VIP cashback expansion + leaderboard prize pool growth
  • Direct fiat methods (Stripe ACH, SEPA) under provider review
  • ru/es/pt/tr translations promoted past machine-translation drafts once the first translator pass lands

The platform code, schema migrations, and worker pipelines are all versioned and audit-traceable. If you spot a discrepancy between what your account shows and what you expect — open a support ticket on /help and we'll trace it down to the ledger row.