Clone, build, test
This page describes the current state, not the intended one. Where a step does not exist yet, it says so instead of inventing it.
What the protocol repository contains today
The protocol repository at github.com/Lemma-Development-Labs/vessel was cloned on 2026-08-29. It contains a README and a LICENSE. Nothing else.
That means, as of that date:
- No Solidity sources.
- No Foundry or Hardhat project.
- No test suite.
- No ABIs.
- No deployed addresses.
There is nothing to build and nothing to test. Any page on this site that names a contract, a function signature, or an address is describing the design, and renders those items as unverified UNVERIFIED — PENDING GATE-0 until the code is public. See Contracts and Addresses.
If a third party publishes "how to build Vessel" instructions, they are not building this repository, because there is nothing in it to build. Treat any such instructions, and any binary or address they produce, as unverified.
What arrives at Gate-0
The litepaper states that the conservation invariant
ΔNAV_Hull + ΔNAV_Ballast + ΔReserve + fees = G
is enforced in code and fuzzed for every epoch. Today that is a claim in a document. It becomes a claim you can check on the day the contracts publish: clone, run the suite, and read the invariant test yourself.
What the published repository will contain is not verified. The litepaper's
language implies a fuzz suite around the waterfall; the toolchain
(Foundry UNVERIFIED — PENDING GATE-0 or otherwise), the test layout, and the
commands are not published UNVERIFIED — PENDING GATE-0. This page will be
rewritten with the real commands when they exist, and the verified_at date
in the footer will move.
The date of Gate-0 is not published UNVERIFIED — PENDING GATE-0.
What you can do today
Three things are real and checkable now.
1. Run this documentation site locally
This site is a Docusaurus 3 project. The commands below are the scripts
declared in its package.json, not a generic template. Node 18 or newer is
required by the engines field.
git clone git@github.com:Lemma-Development-Labs/vessel-docs.git
cd vessel-docs
npm install
npm start
npm start runs docusaurus start and serves the site with hot reload.
Other scripts in the same file:
npm run check # validates frontmatter on every page
npm run build # runs check + llms.txt generation, then a production build
npm run serve # serves the production build
npm run typecheck # tsc
npm run build runs scripts/check-frontmatter.mjs and
scripts/gen-llms.mjs first. A page missing verified_by or verified_at
fails the build. That is deliberate: every page carries the sources it was
checked against, and the build refuses pages that do not.
Whether the docs repository is public is a property of its GitHub settings, which this page does not verify. If the clone fails with a permissions error, that is why.
2. Read the litepaper
The litepaper at vessel.wtf/litepaper is the primary source for every protocol-level statement on this site: the delta band, the leverage split, the Hull rate formula, the subordination floor, the waterfall, and the shortfall ordering. It is a design document. It is not a substitute for code, and this site does not treat it as one.
One known staleness: the litepaper states a 400ms block time for Monad. Current Monad documentation at docs.monad.xyz gives 300ms blocks, 300ms speculative finality, and 600ms full finality. The litepaper predates the current network figures.
3. Verify every third-party fact
Every number on this site that comes from Monad, Perpl, Kuru, Pendle, or a registry carries a source tag in the page footer. The verification page lists each source, how it was read, and the conflicts found between sources. You can repeat every check listed there without trusting this site.
For code presence at any address published later, the check is:
cast code <address> --rpc-url https://testnet-rpc.monad.xyz
Monad testnet is chain ID 10143; mainnet is 143. Contract verification on Monad explorers follows the guide at docs.monad.xyz (Foundry and Hardhat sub-guides). That guide applies to Vessel contracts once they exist, not before.
Status of the testnet app
vessel.wtf states that Vessel is experimental software in testnet and
that the deployed contracts hedge against a simulated venue
SIMVENUE — SIMULATED behind the IVenue interface. The testnet app is reached
from vessel.wtf. The testnet.vessel.wtf hostname does not resolve as of
2026-08-29 and is not a working URL.
A deployed testnet contract with unpublished source is a contract you cannot audit. Interact with it on that basis.
Summary
| Artifact | State on 2026-08-29 |
|---|---|
| Protocol source | Not published |
| Test suite | Not published |
| ABIs | Not published |
| Deployed addresses | Not published |
| Docs site source | This repository; builds with the commands above |
| Litepaper | Published at vessel.wtf/litepaper |
| Audit | None; unaudited |