Skip to content

GoldKey Enforcer v0.2.1 (beta)

Pre-release
Pre-release

Choose a tag to compare

@noah-ing noah-ing released this 16 Aug 00:10
· 3 commits to main since this release

GoldKey Enforcer v0.2.1 beta

This prerelease packages the local, fail-closed GoldKey enforcement runtime for design-partner evaluation. It includes four config-driven launchers for guarded MCP, AgentCash, and constrained Base-wallet execution, plus the lower-level SDK and examples.

Release integrity

  • Artifact: goldkey-enforcer-0.2.1.tgz
  • Size: 120073 bytes
  • SHA-256: 62dbeb10684e075a9ca7d08862eaa99b30f2c2f958bba3f9cc8ecbd7c212d3e5
  • SHA-512 SRI: sha512-y0qBohVxB/5F9DkzXBDKeerlpudXlpHaewj7D4coqLyC9IbBbH7vtZ1bBYyck31hdXiTaNTQOYvwAa/enm54wQ==
  • License: ISC
  • Runtime: Node.js 22 or newer

Download both attached files, verify the local tarball against the attached integrity manifest, and install only that verified local file with lifecycle scripts disabled. The package is intentionally marked private and is not published to an npm registry.

Verification performed for this build

  • The artifact rebuilt deterministically to the same SHA-256.
  • A clean temporary project installed the tarball with --ignore-scripts, imported the public SDK, and ran the packaged wallet CLI.
  • 160 enforcer tests passed.
  • 21 edge/distribution tests passed.
  • 15 contract tests passed offline.
  • 162 repository tests passed; one optional live-Postgres contention test was skipped.
  • The packaged file set was scanned for workstation paths, private keys, and common credential patterns.

Important beta limits

This is beta software, locally tested but not independently audited or certified. The local enforcer is a security boundary only when it is the exclusive path to the protected connector or signer. Remove all direct bypass routes, keep payment and execution keys separate, use low-balance execution wallets, and stop on any ambiguous outcome or verification failure.

See the bundled README for exact installation, topology, and fail-closed operating requirements. Design-partner evaluation is available through the repository's pilot link.