VS Code extension
Before you run anchor deploy, compare your local build with what is on chain, without leaving the editor.
Install
- 1Download the extensionGet
tidemark.vsixfrom the v0.1.0 release. - 2Install itIn VS Code, open Extensions, click
⋯and chooseInstall from VSIX…, or run:It works the same in Cursor, Windsurf and VSCodium.shellcode --install-extension tidemark.vsix
- 3Run a commandOpen the command palette (
Ctrl+Shift+P) and typeTidemark.
Marketplace listing
The Marketplace listing is awaiting review; the release file is the same build.
Build from source
- 1Build the engine for NodeNeeds the
wasm32-unknown-unknowntarget andwasm-bindgen-cli 0.2.130.shellrustup target add wasm32-unknown-unknown cargo install wasm-bindgen-cli --version 0.2.130 --locked bash scripts/build-vscode.sh
- 2Open the extensionOpen the
vscode/folder in VS Code and pressF5. A second window starts with Tidemark loaded.
Commands
| Command | What it does |
|---|---|
| Tidemark: Review a build against the deployed program | Asks for a program id, fetches its ProgramData over RPC and reviews your local .so against it |
| Tidemark: Review two program binaries | Compares any two .so files |
The report opens in the Tidemark output channel in the same layout as the CLI, with the verdict hash. A warning pops up when the risk reaches your threshold.
Settings
| Setting | Default | Meaning |
|---|---|---|
tidemark.rpc | devnet | RPC used to fetch the deployed program (finalized commitment) |
tidemark.warnAt | high | Risk level that raises a warning |
One RPC
The extension trusts the RPC you configure for the deployed bytes. Use a provider you trust, or cross-check with
tidemark fetch.