Why this project exists

Decentralised finance was built on assumptions that work fine when the average user trades $200 of an ERC-20. Every assumption breaks at scale. A $10M order on a public AMM moves the reference price; an MEV bot sandwiches it; a competitor in the same Discord watches the wallet and replicates the position by lunchtime. The cost is measured in basis points and reputations.

We started writing Moby Market because the question "how do you trade your real size on-chain without losing money?" did not have a satisfying answer. The closest answers — Hashflow RFQ, CoW solvers, Renegade dark pools, Jupiter aggregation — solved fragments of the problem on different chains with different trade-offs. None of them combined OTC matching, randomised execution algos, on-chain zero-knowledge privacy, and intent-based solver competition into a single Solana-native stack. So we wrote it.

Design principles

Open by default. The Rust workspace is MIT-licensed. The on-chain programs are auditable by anyone. We will never run a closed-source matcher in front of a public protocol.

Adversarial assumptions. Every system is built assuming the rest of the market is a worst-case actor. Commit-reveal everywhere. Pedersen commitments on amounts. Stealth addresses on both sides. Randomised child-order timing as a default, not an opt-in.

Privacy without surveillance compromise. Compliance is a constraint, not an excuse to publish positions. Selective disclosure lets a desk prove jurisdiction and accreditation without revealing identity or strategy. Auditors get a verifiable trail; competitors get nothing.

Solana-first, cross-chain-ready. Solana gives us the throughput and latency profile institutional execution actually needs. Wormhole and LayerZero adapters make settlement extensible to Ethereum, Arbitrum, and Base without abandoning the Solana execution layer.

Small surface, deep semantics. The workspace is intentionally a handful of crates with clear single responsibilities — math, oracle, types, trading, privacy, bridge. Adding a feature should mean adding a struct, not a subsystem.

Who is behind it

Moby Market is built inside cryptuon, a small studio of systems engineers and quants. The current contributors include former Solana program engineers, a ZK protocol researcher, and operators who ran execution desks at funds where size was a daily problem. The team is intentionally small. Decisions are made in the open via GitHub issues and recorded design notes.

Status

The protocol is at v0.1.0. Programs compile against Anchor 0.29 and solana-program 1.16, with release profiles enforcing overflow checks, link-time optimisation, and single-codegen-unit deterministic builds. The OTC and TWAP modules are feature-complete in the workspace; the ZK privacy pools are in active integration; cross-chain settlement primitives ship through the moby-bridge crate. Independent smart-contract audits are scheduled before mainnet flow.

How to engage

If you trade institutional size and want to try Moby Market on devnet, clone the workspace and run it. If you would like the team's help integrating it into your existing prime-desk stack, write us at hello@mobymarket.cryptuon.com and we will scope an engagement. If you are a security researcher, the bug-bounty program is public and the responsible-disclosure inbox is monitored 24/7.

Either way: do not trust marketing copy. Read the source.