DOGMACAPITAL
WorkspaceVenues
Liquidity sources

Venues

Every venue DOGMA CAPITAL routes through, and none it does not. The router can only reach a venue that is listed in DogmaVenueRegistry on chain, so this list is not a description of the routing surface, it is the routing surface.

Venues listed
2
2 enabled
Pools indexed
0
across all venues
Aggregate depth
$0.00
total value in indexed pools
Registry
On chain

Routing surface

Sorted by venue id: the same id the router uses on chain
ID Venue Model Fee tiers Pools Depth Legs filled Win rate Factory Router State
1 Concentrated V3 Concentrated 0.05% 0.30% 1.00% 0 $0.00 0 0.00% 0x1f7d…2EfA 0xCaf6…5cb2 Enabled
2 Constant Product V2 Constant product 0.30% flat 0 $0.00 0 0.00% 0x8bcE…937f 0x89e5…9eba Enabled
A concentrated venue is swept once per fee tier, so listing three tiers is three pool reads per quote. That cost is why the win rate matters.

How a venue gets listed

Listing is a single owner transaction against DogmaVenueRegistry. It records the venue's model (constant product or concentrated), its factory, the router the settlement leg is sent through, its fee, and: for a concentrated venue: the fee tiers worth probing.

The Quoter, the Book and the Router all read that registry rather than holding an address of their own, which is what makes adding a venue a configuration change instead of a redeploy of everything that quotes or settles.

Turning a venue off is delegated to the keeper, so an incident can be contained without the owner key. Turning one back on is the owner's alone: a compromised keeper can degrade routing but can never widen it.

What the router may do

A route is a list of legs, each naming a venue id and a size. DogmaRouter looks each id up in the registry and refuses anything unknown or disabled. Even a route the desk itself constructed cannot reach a venue that has not been listed.

Per-leg minimums are deliberately zero. The guarantee lives at the order level: the router measures the recipient's balance before and after the whole route and reverts unless the total cleared the signed floor. One leg coming in soft is fine as long as the order did not.

The router holds nothing between transactions. Anything that ends up stuck in it: a rebasing token, a mistaken direct transfer: can only be swept to the fee sink, never to an address the caller names.