Somnia Venues

Launch your own venue. Set your own fees.

A venue is your market, built on Somnia's infrastructure. You choose the markets, the brand, the users and the fee. Somnia runs the order books, matching, oracles, liquidity and settlement, all onchain. A venue isn't a separate protocol: it is a branded market built from the platform's products, registered under your operator in Somnia Markets.

What you decide

Markets	Spot pairs, binary event contracts or both, on crypto, RWAs or any question with a public data source. Perpetual futures are live on testnet.
Fee	The fee your venue charges on the activity it brings, paid to your address as each trade settles. Somnia's protocols charge nothing on top.
Brand and front end	Your own interface, built on the Markets SDK and its GraphQL indexer. An open-source template is coming in the Venue Kit.
Users	Open to everyone or limited to an allow-list. You can sponsor gas and use session accounts so users trade without wallet prompts.
Liquidity	Your markets trade on the shared books, so liquidity isn't split. Quote with your own desk, or use Somnia's market-making service.
Operations	Every venue setting is a public transaction, and your venue's markets and trading are live in the Somnia Explorer.

Launch a venue today

Everything a venue needs already exists onchain, behind the Markets SDK. Build and test on the Shannon testnet first; the SDK docs explain how to get testnet funds.

1. Register as an operator. OperatorAdmin.registerOperator makes your address an operator in MarketsCore, with a default fee recipient.
2. Create a venue. OperatorAdmin.createVenue registers a venue under your operator. Its market type is fixed when it's created, along with its first fee and policy.
3. Set its fee. On event (binary) markets, each venue has its own fee parameters and fee recipient, and a market keeps the fee it was created with. On spot markets, a venue can earn a builder fee on the orders it routes, when they carry its builder attribution, the trader has approved it as a builder, and the pool's fee cap allows it.
4. Choose who creates markets. The venue's policy, set when it's created, opens market creation to everyone or gates it.
5. Build the front end on the Markets SDK, which covers trading, accounts, prices and the GraphQL indexer.
6. Watch it. Every venue and operator, and what they've traded, is on the Venues page in the Somnia Explorer. The SDK can also check a venue's health.

The contracts behind these calls, including how a market records the operator and venue it was created under, are in the contracts reference.

Coming soon

The Venue Kit will wrap these steps in a front-end template, Somnia CLI commands and an agent skill, so you or a coding agent can scaffold, register and launch a venue in a few commands. A console in the Somnia Explorer to run a venue, and the Somnia CLI and MCP server, are coming too.