Jonathan Navarrete

labcoat

“From Rust source to decoded trace.”

tagline, verbatim from labcoat.sh

labcoat is a Rust-native command line for Alkanes contracts, covering the path from source to a decoded trace, alongside a managed local Bitcoin regtest the project calls Labcoat Network.

labcoat

raster
The labcoat mark
The labcoat mark

what it does

4

Contract lifecycle

labcoat scaffolds a Rust contract workspace with contract sources, native integration tests, configuration and agent instructions. It builds every contract for WASIp1 and runs host integration tests before a chain is involved, then publishes a contract by package name through commit and reveal. Opcode calls, chain-state reads and event decoding run through its call, simulate and trace commands, whose output covers create, invoke, return and revert events.

Labcoat Network

A single command downloads a bitcoind-derived executable and its Alkanes and Esplora WebAssembly modules, pinned to the installed release, and runs one process providing a Bitcoin regtest chain with in-process Alkanes and Esplora indexes. The documentation describes the network as local, private and resettable, and states that it runs regtest rather than Signet. Status, logs, snapshot, restore, teardown and reset commands control it, alongside a built-in wallet and faucet.

JSON envelopes

Every command accepts a JSON flag and emits exactly one versioned envelope on stdout, with logs and progress kept on stderr. Error envelopes carry a stable code, a readable message and a hint naming a recovery command. A printed envelope exits zero even when its ok field is false, so the documentation directs callers to read the envelope rather than infer success from the exit code.

MCP server

labcoat runs a stdio MCP server exposing its network, wallet, build, deployment, call, simulation and trace operations as tools, using the same typed operations as the command line. The documentation names the executable, the JSON envelopes and the MCP tools as the supported public interface, and notes that internal crates may change independently of it.

The project describes it as early-stage software for local Alkanes development, states that its interfaces may change before 1.0, and says its mainnet deployment controls are not production-ready. That is the project’s own characterisation, repeated here rather than summarised away.

Facts

org
not stated
licence
MIT