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.
DataTwin reads your full transaction population, recovers the cash, tax and misstatements already lost, then keeps the same rules running forward as observability.
FinanceTypeScript · CSSGitHub @Logaprasanth-uiuxOnlineOwner 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
Loading the full README. The saved excerpt is shown below.
Marketing site for DataTwin, migrated from static HTML to Next.js 16 (App
Router, TypeScript). Styling is the original hand-written CSS in
app/globals.css — no Tailwind.
Deploy to Vercel with zero configuration (connect the repo, it just works).
See CLAUDE.md — it tracks which pages are ported, explains the
faithful-port approach (mechanical HTML→JSX, original vanilla JS moved into
useEffect), and lists what to refactor once the visual QA pass is signed off.
The original static site (../DataTwin-Website) is the reference for anything
not yet ported.Read the full README ↗Marketing site for DataTwin, migrated from static HTML to Next.js 16 (App
Router, TypeScript). Styling is the original hand-written CSS in
app/globals.css — no Tailwind.
npm install
npm run dev # http://localhost:3000
npm run build # production build
npm run start # serve the build
Deploy to Vercel with zero configuration (connect the repo, it just works).
| Path | What |
|---|---|
app/layout.tsx | root document, fonts (next/font), pre-paint theme script |
app/globals.css | all site CSS — design tokens + every component |
app/(site)/ | the marketing pages and their shared header/drawer/footer shell |
components/ | SiteHeader / SiteDrawer / SiteFooter / IconSprite, plus the *Scripts client components carrying the ported interactivity |
public/datatwin-logo.png | wordmark |
See CLAUDE.md — it tracks which pages are ported, explains the
faithful-port approach (mechanical HTML→JSX, original vanilla JS moved into
useEffect), and lists what to refactor once the visual QA pass is signed off.
The original static site (../DataTwin-Website) is the reference for anything
not yet ported.