Lumoin.Veridical.Cli.linux-arm64
0.0.8
dotnet add package Lumoin.Veridical.Cli.linux-arm64 --version 0.0.8
NuGet\Install-Package Lumoin.Veridical.Cli.linux-arm64 -Version 0.0.8
<PackageReference Include="Lumoin.Veridical.Cli.linux-arm64" Version="0.0.8" />
<PackageVersion Include="Lumoin.Veridical.Cli.linux-arm64" Version="0.0.8" />
<PackageReference Include="Lumoin.Veridical.Cli.linux-arm64" />
paket add Lumoin.Veridical.Cli.linux-arm64 --version 0.0.8
#r "nuget: Lumoin.Veridical.Cli.linux-arm64, 0.0.8"
#:package Lumoin.Veridical.Cli.linux-arm64@0.0.8
#addin nuget:?package=Lumoin.Veridical.Cli.linux-arm64&version=0.0.8
#tool nuget:?package=Lumoin.Veridical.Cli.linux-arm64&version=0.0.8
veridical
A command-line and Model Context Protocol (MCP) tool for Lumoin.Veridical.
Install
dotnet tool install --global Lumoin.Veridical.Cli
Commands
veridical info Print platform and scalar-backend information.
veridical hash <input> BLAKE3-256 hash of UTF-8 text (or --hex bytes).
veridical hash <hex> --hex BLAKE3-256 hash of a hex-encoded byte string.
veridical selftest Run known-answer conformance vectors; exit non-zero on failure.
veridical prove <request> Prove a supply-chain predicate bundle from local data; artifact JSON to stdout.
veridical verify <artifact> Verify a proof artifact and report the statement it proves; exit non-zero if it does not.
For prove and verify, the file argument may be - to read from standard input.
selftest runs deterministic known-answer vectors — a BLAKE3 test vector, field
arithmetic (multiply, invert), and the batch multiply checked against the
single-element path across lane-group boundaries. It is the same code used as the
native-AOT conformance check in CI, so it validates that the AOT-compiled build
computes correct results on each target (including the SIMD paths on ARM).
Predicate proofs
prove and verify cover a supply-chain predicate bundle: an ordered conjunction of
at-least / at-most fixed-point claims (for example, a battery-passport bundle —
recycled content at or above a minimum and carbon footprint at or below a cap),
proven over Spartan-over-Ligero — a transparent (hash-based) proof system with no
trusted setup and no key material to distribute. The measured quantities are witness
inputs and are not written into the artifact's JSON fields — but the wired proof path
is sound and binding, not witness-hiding: the embedded Ligero openings reveal
committed-matrix columns in cleartext, and for the wired circuit sizes those columns
determine the full witness — including the measured quantities — by interpolation.
Treat the artifact as disclosing the measured values to whoever receives it. What the
proof adds is integrity — the recipient can check that the claims verifiably hold and
that the statement was not altered — with one static binary and no PKI. A hiding
(masked) configuration is a possible future upgrade, not what ships here.
provereads a request that carries the statement parameters and the measured quantities, and writes a proof artifact. Send the artifact only to parties allowed to learn the measured values (see the disclosure note above).verifyneeds only the artifact — no private data, no PKI, no platform change. It rebuilds the statement circuit from the artifact's claim descriptors, reconstructs the public instance from the revealed public inputs (no witness), and checks the proof. It then prints the described statement.
A regulatory bound is either a constant baked into the circuit or a public input
the artifact reveals. Either way the bound is bound to the proof: changing a constant
in the descriptor, a revealed public input, or the commitment parameters causes
verification to fail. The proof attests that the described statement is satisfiable —
verify prints that statement so an operator confirms it is the compliance claim they
require.
Every claim carries a kind discriminator. A range claim compares a measured
quantity against a bound (atLeast / atMost); the bundle's range claims are proven
together over Spartan-over-Ligero. A memberOf claim states that a measured
quantity is one of a public list of allowedValues; each is proven by its own
LogUp-over-Ligero lookup argument, whose proofs travel in the artifact's
lookupProofs. The same disclosure note applies to both kinds.
The commitment parameters (curve, query count, lookup query count, inverse rate, digest size) are pinned to one wired set that both verbs enforce, so an artifact cannot silently weaken them. The lookup query count is higher than the range one: the lookup argument opens three independently forgeable columns, so its 128-bit target carries a union-bound surcharge (65 columns instead of 64 at rate 1/16).
Example
A request proving recycled content ≥ 30.0%, carbon footprint ≤ 12.50, and a material code drawn from an allowed list, over private measurements of 32.5%, 11.20 and 7:
{
"format": "veridical-supply-chain-predicate-request/3",
"curve": "bls12-381",
"transcriptDomain": "veridical.supplychain.batterypassport.v1",
"queryCount": 64,
"lookupQueryCount": 65,
"inverseRate": 16,
"digestBytes": 32,
"claims": [
{ "name": "recycled_content", "kind": "range", "direction": "atLeast", "fractionalDigits": 1, "inclusiveMaximum": "100.0", "bound": "constant", "boundValue": "30.0", "measured": "32.5" },
{ "name": "carbon_footprint", "kind": "range", "direction": "atMost", "fractionalDigits": 2, "inclusiveMaximum": "100.00", "bound": "constant", "boundValue": "12.50", "measured": "11.20" },
{ "name": "material_code", "kind": "memberOf", "fractionalDigits": 0, "inclusiveMaximum": "9999", "allowedValues": ["3", "7", "42", "1001"], "measured": "7" }
]
}
veridical prove request.json > artifact.json
veridical verify artifact.json
# VALID: proves recycled_content >= 30.0 (constant); carbon_footprint <= 12.50 (constant); material_code in {3, 7, 42, 1001} (4 allowed value(s))
The artifact and request JSON are serialized by Lumoin.Veridical.Json, an AOT-safe
(source-generated) reference serializer that consumers can reuse.
MCP server
Run as an MCP stdio server:
veridical -mcp
Exposed tools: Info, Hash, SelfTest, Prove, Verify. The packaged
.mcp/server.json lets MCP-aware clients discover and launch the server.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.