Oracle3
Open-source trading engine and MCP server for prediction markets. Fee-aware no-arbitrage trading across related contracts, live on Kalshi, Polymarket and Solana or on paper.
منصة تداول اجتماعي لمتابعة أفضل المتداولين ونسخ صفقاتهم تلقائيًا.
Translation pending
FinancePLpgSQL · TypeScriptGitHub @moamen27248100r-sudoOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗This is a Next.js project bootstrapped with create-next-app.
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
To learn more about Next.js, take a look at the following resources:
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.
Network settings (deposit address, minimums, confirmations, fees, limits, on/off) are edited in the
admin panel at /admin/crypto-networks. Deposits are verified on-chain by TxID (src/lib/crypto);
withdrawals are executed by the back office at /admin/withdrawals. Migration:
supabase/migrations/0233_crypto_wallet.sql (rollback in supabase/rollback/).
Environment variables (Vercel → Project → Settings → Environment Variables):
| Variable | Required | Purpose |
|---|---|---|
ETHERSCAN_API_KEY | yes | Etherscan API V2 key, verifies BEP20 (chain 56) and ERC20 (chain 1) deposits |
TRONGRID_API_KEY | recommended | TronGrid key for TRC20 (works without one at a lower rate limit) |
CRON_SECRET | yes | Secret for /api/cron/crypto-deposits (re-checks deposits awaiting confirmations) |
BSC_RPC_URL / ETH_RPC_URL | optional | JSON-RPC endpoint used instead of Etherscan for that network |
ALLOW_SEARCH_INDEXING | at launch | true lets search engines index the site; unset = noindex everywhere |
The database calls the cron route every minute (pg_cron + pg_net). It reads the URL and secret
from Supabase Vault; run once in the Supabase SQL editor with the same secret as CRON_SECRET:
select vault.create_secret('https://<your-domain>/api/cron/crypto-deposits', 'crypto_cron_url');
select vault.create_secret('<CRON_SECRET value>', 'crypto_cron_secret');