Lumoin.Veridical.Cli.win-x64
0.0.4
dotnet add package Lumoin.Veridical.Cli.win-x64 --version 0.0.4
NuGet\Install-Package Lumoin.Veridical.Cli.win-x64 -Version 0.0.4
<PackageReference Include="Lumoin.Veridical.Cli.win-x64" Version="0.0.4" />
<PackageVersion Include="Lumoin.Veridical.Cli.win-x64" Version="0.0.4" />
<PackageReference Include="Lumoin.Veridical.Cli.win-x64" />
paket add Lumoin.Veridical.Cli.win-x64 --version 0.0.4
#r "nuget: Lumoin.Veridical.Cli.win-x64, 0.0.4"
#:package Lumoin.Veridical.Cli.win-x64@0.0.4
#addin nuget:?package=Lumoin.Veridical.Cli.win-x64&version=0.0.4
#tool nuget:?package=Lumoin.Veridical.Cli.win-x64&version=0.0.4
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.
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).
MCP server
Run as an MCP stdio server:
veridical -mcp
Exposed tools: Info, Hash, SelfTest. 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.
Added:
- Initial public packages: `Lumoin.Veridical.Core`, `Lumoin.Veridical.Hashing`,
`Lumoin.Veridical.Backends.Managed`, `Lumoin.Veridical.Bbs`,
`Lumoin.Veridical.Secdsa`, `Lumoin.Veridical.Analysis`, and the
`Lumoin.Veridical.Cli` command-line / MCP tool.
- `Lumoin.Veridical.Longfellow`: a consumable, serialization-free facade over the
dual-field Longfellow zero-knowledge-over-ECDSA mdoc prover and verifier.
- `WellKnownLigeroParameters` and `LigeroSoundnessRegime`: pinned Ligero
polynomial-commitment soundness parameters with a regime-based opened-column
derivation (defaulting to the provable Johnson bound).
- A constant-time NIST P-256 scalar-field Montgomery backend, used by SECDSA and
ECDSA signing in place of the variable-time `BigInteger` path.
- `SECURITY.md`: the consolidated security and constant-time posture.
Changed:
- The masked-Spartan non-hiding BaseFold entry points are renamed
`ProveBaseFoldSound` / `VerifyBaseFoldSound`, and the zero-knowledge entry
points (`ProveZkBaseFold` / `VerifyZkBaseFold`) require a hiding commitment
provider.
See full changelog at https://github.com/lumoin/Lumoin.Veridical/blob/main/CHANGELOG.md.