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
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Lumoin.Veridical.Cli.win-x64" Version="0.0.4" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Lumoin.Veridical.Cli.win-x64" Version="0.0.4" />
                    
Directory.Packages.props
<PackageReference Include="Lumoin.Veridical.Cli.win-x64" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Lumoin.Veridical.Cli.win-x64 --version 0.0.4
                    
#r "nuget: Lumoin.Veridical.Cli.win-x64, 0.0.4"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Lumoin.Veridical.Cli.win-x64@0.0.4
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Lumoin.Veridical.Cli.win-x64&version=0.0.4
                    
Install as a Cake Addin
#tool nuget:?package=Lumoin.Veridical.Cli.win-x64&version=0.0.4
                    
Install as a Cake Tool

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.

There are no supported framework assets in this package.

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.

Version Downloads Last Updated
0.0.4 135 6/28/2026
0.0.3 153 6/18/2026
0.0.2 162 6/17/2026
0.0.1 143 6/16/2026

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.