What Vessel Publishes

This page lists what Vessel commits to publish, and when. A commitment is not an artifact. Where a line below describes something that has not yet been published, it says so. The public repository at github.com/Lemma-Development-Labs/vessel contains only a README and a LICENSE as of 2026-08-29, so every contract-level artifact named here is a commitment, not a thing you can fetch today.

Unaudited, testnet

Vessel is experimental software in testnet. Nothing on this page is a statement that the contracts have been audited or reviewed.

Gate-0 commitments

Gate-0 is the point at which the deployed testnet contracts become publicly verifiable. The following commitments come from the protocol team's build brief. None of them is met as of 2026-08-29.

• Deployed addresses are listed on /developers/addresses, one row per contract, with unpublished rows shown as unverified rather than omitted.
• Source is verified on MonadVision through Sourcify and on Monadscan, following the Monad contract verification guide; the Sourcify path needs no API key, and a verify command that prints an error is confirmed on the explorer, not trusted from the terminal.
• ABIs and the full event list are published alongside the addresses; the event reference is /developers/events.
• The indexer endpoint is public; an Envio HyperIndex contract-import requires the contract to be deployed and verified on a Monad explorer first, so this item follows source verification, not the other way round.

Ongoing commitments

• The verification ledger is updated with dated rows; a row is never edited in place, a new dated row supersedes it.
• Integration tiers are re-derived from what the deployed contracts actually call, and downgrades are published with the same prominence as upgrades. The hedge venue today is SimVenue SIMVENUE — SIMULATED, an owner-settable simulated venue behind the IVenue interface; Perpl remains IN_PROGRESS until a deployed contract calls it.
• Builder-code revenue from execution rebates on Perpl is disclosed. The amount as of 2026-08-29 is not yet published UNVERIFIED — PENDING GATE-0.
• Incidents are announced on x.com/vessel_hq and t.me/+Akd24ACXWl5lY2E1; a dated ledger row follows the announcement.
• Accrual runs on the litepaper cadence: daily accrual, continuous NAV, and the Hull rate re-derived as a contract parameter, r_H = clamp(EWMA_30d(net funding APR) × (1 − h), 0, r_cap), with h = 40% and r_cap = 15% APR. The rate is a parameter, not a performance figure.

What triggers a ledger update

Any of the following adds a dated row to the ledger at /resources/verification:

• A contract is deployed, redeployed, upgraded, or paused.
• An address on /developers/addresses changes state from unverified to verified, or the reverse.
• An integration tier changes in either direction.
• A hedge venue changes, including the move from SimVenue to Perpl.
• A parameter in the accrual formula, the subordination floor θ_min = 20%, the Reserve target of 2% of TVL, or the 48-hour Ballast cooldown is changed.
• An incident is announced.
• A source conflict is found between two primary sources; the ledger records the conflict and which source the docs follow.
• An audit scope is agreed, begins, or completes.

What is not committed

• No page on this site presents an APR or yield as expected or historical performance. The Hull rate is a contract parameter at every occurrence.
• No date is committed for Gate-0. The team brief does not state one, and this page does not estimate one.
• The frequency of builder-code revenue disclosure is not stated in the team brief UNVERIFIED — PENDING GATE-0.