Skip to content

Core Quickstart

This guide gets a developer from a clean machine to a working DigiEmu Core CLI.

Terminal window
git clone https://github.com/DigiEmu/core.git
Set-Location .\core
Terminal window
go version
Terminal window
go test ./...

Do not continue with a local build if the test suite fails.

Terminal window
go build -o digiemu.exe ./cmd/digiemu

Confirm that the executable exists:

Terminal window
Get-Item .\digiemu.exe
Terminal window
.\digiemu.exe --help

The stable v1 verification interface accepts an explicit bundle path:

Terminal window
.\digiemu.exe verify `
--bundle "<bundle-path>" `
--json

A verification JSON result exposes fields including:

ok
ref
expected
got
hash_alg
canonical_scope
trace
message
Terminal window
.\digiemu.exe replay `
--bundle "<bundle-path>" `
--json

For the same fixed bundle, replay is intended to preserve deterministic state reconstruction and deterministic trace ordering.

This step is optional and uses experimental functionality.

Terminal window
go run ./cmd/digiemu `
experimental conformance run `
testdata/core_2_conformance

Expected summary:

Conformance run summary: total=11 passed=11 failed=0

JSON:

Terminal window
go run ./cmd/digiemu `
experimental conformance run `
testdata/core_2_conformance `
--json

At this point you have:

  1. cloned the public Core source
  2. executed its test suite
  3. built the CLI locally
  4. exercised the deterministic verification interface
  5. exercised replay
  6. optionally checked the Core 2.0 draft conformance suite