MiroShark 🦈

Polymarket trades are public. Position sizes leak. Copy-traders front-run. Mirofish fork for confidential prediction markets.

A serious desk with real conviction cannot trade meaningful size without telegraphing exactly how much it believes in a market.

MiroShark fixes that.

It combines encrypted sizing through a Fhenix CoFHE Uniswap v4 hook, fresh per-position burner EOAs, Circle Gateway cross-chain settlement, and Polymarket CLOB execution — all coordinated by a Gensyn AXL multi-node LLM swarm.

Every position is pinned to 0G Storage with a daily verifiable PnL pack that anyone can audit.

Multi-tenant out of the box: fork the kit and run your own confidential fund on the same rails.

MiroShark is a Turborepo monorepo built with Next.js 16 and Bun, deployed on Vercel. It includes a Python execution router and a meridian_signal swarm gateway exposed through a Cloudflare tunnel on miro-shark.com.

Authentication is handled by Clerk through a passkey-based treasury onboarding flow with ENS provisioning. Persistence uses Neon Postgres as a projection layer over JSONL journals and 0G Storage pins.

The agent layer runs on Pinata Cloud through agent xt1sgi73, paired with @miro_shark_bot on Telegram. Reasoning is powered by a Gensyn AXL multi-node swarm with persona specialization across superforecaster, contrarian, and market-microstructure agents. Each run uses disagreement-aware aggregation, then gets journaled and pinned to 0G with a content-addressed root. The operator terminal renders this as a verifiable provenance pill in the header.

Capital flow is fund-native. Each fund receives its own ENS subname under miroshark.eth on Sepolia, such as fund-a.miroshark.eth, alongside an agent subname like xt1sgi73.miroshark.eth. Both carry text records describing agent skills and permissions.

Treasury wallets are Circle Developer-Controlled Wallets. Capital is transferred into per-position burner EOAs, while size payloads are encrypted through a Fhenix CoFHE hook on Uniswap v4. This is the wedge: the public CLOB sees the order, but neither the true position size nor the originating signer leaks.

Settlement crosses Polygon, where Polymarket’s CLOB is native, through Circle Gateway. Non-USDC inflows, including MoonPay ETH and agent profits in random tokens, are converted through the Uniswap Trading API. Bearer-gated /api/uniswap/quote and /api/uniswap/calldata routes feed into the same approval gate, audit log, and Telegram notification flow used by every treasury movement.

KeeperHub Direct Execution handles bridge and hook transactions where managed gas, nonce coordination, and per-transaction executionId tracking matter for post-hoc auditability. Cron and automation rails poll Polymarket for resolved positions and trigger close-out without keeping the agent in the hot path.

Observability is end-to-end. Every swarm tick, transfer, swap, and bridge call lands in Postgres, JSONL, 0G, and a Telegram channel the operator can pin to their phone.

The system is multi-tenant from day one. A fund operator can run bun run dev, choose a fund name and ENS alias during signup, and receive their own subname, Circle wallet, and audit projection without touching the codebase.