Wiki article · Published October 2, 2026 · Living document

Sovereign Contracts

Smart contracts, auditable by design — open source, MIT

A local-first pipeline for sovereign contract work: every stage inspectable, every artifact reproducible, nothing hidden behind a hosted black box. Built for contexts where the contract is the relationship and the audit trail is the product.

Inspect the repository Read the references
Golden Gate Book
Wiki · MMXXVI

Sovereign Contracts is a local-first workspace for auditable smart-contract development, built by Marcus Richards and published as open source under the MIT license. It pairs Hardhat 3 for Solidity compilation, testing, coverage, and deployment with a Python layer for preflight checks and pipeline gates, with the stated end state that the full check suite goes green on a local Mac without any cloud accounts.

The design treats sovereignty as an engineering property: if any stage of the pipeline requires a hosted service, an API key, or an opaque binary, that stage cannot be audited, and the audit trail it was supposed to produce is incomplete.

Background

Smart-contract toolchains routinely depend on hosted infrastructure: remote compilers, cloud test networks, third-party verification services. Each dependency is a point where the builder must trust rather than verify. Sovereign Contracts was built to answer whether a professional-grade contract pipeline, compile, test, coverage, deploy, verify, could run entirely on local hardware with every artifact reproducible from source.

Design

The stack has two sides. Hardhat 3 handles Solidity compilation, the test suite, Ignition-based deployment, on-chain verification when keyed, and built-in coverage reporting. Python 3, kept to the standard library at its core, handles host preflight, pipeline gates, and glue. Two vault scaffolds ship with the workspace: a SecureVault for owner-custody ETH and an AccountingVault implementing a pull and credit ledger under a different threat model.

Quality is enforced by gates, not intentions:

  • make check runs preflight, compilation, and the full test suite, unit, safety, and invariants, as the fast local gate.
  • make check-full adds Slither static analysis.
  • A coverage gate holds a 100 percent statement floor on the production vaults.
  • An environment probe scans for secret patterns before anything leaves the machine.

Testnet deployment and contract verification are documented as explicit, separately-invoked operations, never as defaults.

Limitations

What is not claimed. Sovereign Contracts is a pipeline scaffold, not an audited product. Its vaults are scaffolds, and passing the local gates does not constitute a security audit of any deployed contract. Network operations are documented procedures, not tested defaults, and the project makes no claim about the safety of any specific mainnet deployment.

Development history

Sovereign Contracts was created in July 2026 and published under the MIT license. It remains under development as of October 2026.

See also

  • Interlock, the agent safety substrate
  • Star Lab, the local laboratory where doctrines are tested

References

  1. Sovereign Contracts source repository. github.com/marsojuji-cmyk/sovereign-contracts (public, MIT).
  2. Hardhat documentation. hardhat.org/docs
  3. Slither static analysis framework. github.com/crytic/slither
Inspect the repository Back to the workshop