Oracles

Status

PLANNED

No oracle is wired into any publicly verifiable Vessel contract, as of 2026-08-29.

The Vessel repository at github.com/Lemma-Development-Labs/vessel contains a README and a LICENSE and nothing else. There are no published contracts, no ABIs, and no deployed addresses to inspect. Any statement on this page about an oracle adapter inside Vessel is therefore design intent, not a description of running code.

What Vessel uses it for

The design principle comes before the provider list.

NAV derives from on-chain observable positions wherever possible. The spot leg is a token balance. The short leg is a position on a perp venue whose margin, size, and entry are readable from that venue. Funding is a payment that either arrived or did not. These are facts the Engine can read directly. Vessel accounts from them first.

External feeds are inputs, never authorities over solvency claims. A price feed may be used to mark a position, to bound an acceptable execution price during a rebalance, or to check that a venue's own mark is not drifting from the wider market. It is not used as the sole basis for the conservation invariant ΔNAV_Hull + ΔNAV_Ballast + ΔReserve + fees = G, which is enforced in code against observed positions, and it is not used as the sole basis for the subordination floor B / (H + B) ≥ 20%.

Today the hedge venue is SimVenue SIMVENUE — SIMULATED, a simulated venue with an owner-settable funding rate behind the IVenue interface. SimVenue does not need an external oracle to function, which is one reason the oracle layer remains unbuilt. Perpl integration is next; whether that integration introduces an external feed dependency, and which provider, is undecided.

What is actually wired today

Nothing yet.

No Vessel contract reads from Chainlink, Chronicle, Pyth, Redstone, Stork, Supra, Switchboard, or any other feed. The deployed testnet contracts hedge against SimVenue, whose funding rate is set by the venue owner rather than read from a market. The specific role an oracle will play in the Perpl-backed engine is not yet specified in any public document UNVERIFIED — PENDING GATE-0.

Interface

There is no Vessel oracle interface to publish. When one exists it will be documented here with its exact Solidity signature. Until then, the only relevant interface is the venue abstraction:

// Design-stage. The name is confirmed by the protocol team's build brief;
// the members are not published in any public repository.
interface IVenue {
    // funding, position, and margin reads live here
}

For reference, the Pyth listing on docs.monad.xyz/tooling-and-infra/oracles describes Pyth as a pull oracle and shows a MON/USD feed id, 0x31491744e2dbf6df7fcf4ac0820d18a609b49076d45066d3568424e62f686cd1. This is evidence that MON/USD price data is available on Monad. It is not evidence that Vessel consumes it.

Addresses

Contract (testnet)	Address	Actions
Vessel oracle adapter	UNVERIFIED — PENDING GATE-0

Contract (mainnet)	Address	Actions
Vessel oracle adapter	UNVERIFIED — PENDING GATE-0

Provider-side contract addresses (feed registries, Pyth's on-chain contract, and so on) are published by each provider, not by Vessel, and are not reproduced here because none of them is a Vessel dependency today.

Verify it yourself

Two checks, both independent of Vessel's own claims.

Check the provider landscape. The authority for which oracles support Monad is the oracles page at docs.monad.xyz/tooling-and-infra/oracles. Read 2026-08-29, it lists the following providers as SUPPORTED on both mainnet and testnet: Chainlink, Chronicle, Pyth, Redstone, Stork, Supra, Switchboard. Gelato VRF appears in the testnet table only; the page does not explain the omission from mainnet. "Supported" is the docs' word. This page does not upgrade it to "live", and it does not add any provider that page does not list.

Check that Vessel reads none of them. There is no contract to check. Confirm the absence directly:

# The public repo holds no Solidity as of 2026-08-29
git clone https://github.com/Lemma-Development-Labs/vessel
ls vessel
# README.md  LICENSE

When contract addresses are published, the check becomes cast code <addr> --rpc-url https://testnet-rpc.monad.xyz followed by reading the verified source on a Monad explorer for any external latestRoundData, getPriceUnsafe, or equivalent call.

Failure mode

A bad external feed can misprice NAV inputs. A stale, manipulated, or simply wrong price would, if trusted without bounds, mark the spot leg or the short leg incorrectly, and a wrong mark flows into the residual that Ballast earns, into the reserve accounting, and in the limit into whether a shortfall is recognised at all.

HIGHBad feed misprices NAV inputs

The mitigations are structural rather than provider-specific, which is why they can be stated before a provider is chosen.

Observables-first accounting. Balances, positions, margin, and funding received are read from the chain and from the venue. A feed can only ever refine a mark; it cannot replace an observed position.

Sanity bounds on inputs. Any external price enters through a bound: deviation from the venue mark, staleness against block time, and a hard rejection outside the bound. A rejected input falls back to observables and, if the engine cannot proceed safely, to de-risking. The litepaper's rule already applies: a buffer breach triggers automatic de-risking, never added leverage.

No solvency claim rests on a feed alone. The subordination floor, the conservation invariant, and the shortfall ordering (Ballast, then Reserve, then Hull principal) are all enforced against observed quantities. A feed failure can produce a wrong number in a dashboard; it should not by itself be able to move Hull principal.

The exact bound parameters are not published UNVERIFIED — PENDING GATE-0. They will be listed here when the adapter exists.

MITIGATION · Observables-first accounting; sanity bounds on every external input; no solvency claim rests on a feed alone.

Unaudited, testnet

Vessel is experimental software in testnet. The oracle layer described on this page is planned. Do not rely on any of it for capital decisions.

Links

• Monad oracle support page: docs.monad.xyz/tooling-and-infra/oracles
• Monad tooling and infrastructure directory: docs.monad.xyz/tooling-and-infra/
• Monad developer docs: docs.monad.xyz
• Vessel litepaper: vessel.wtf/litepaper
• Vessel repository: github.com/Lemma-Development-Labs/vessel