Numina 4.0.0 brings the website, operations workspace and installable mobile web app together. Your service workflows and private Treasury records remain available in the same design.
This build identity is calculated from the packaged application files. Detached build provenance is checked separately using the exact inventory fingerprint below. The rc26 control-plane dependency retains its own identity and signed records.
APPLICATION / BUILD PROVENANCE
One file. Trace its build.
A detached signed statement can identify the builder and the exact release file. The statement stays separate so the original file remains unchanged.
The lookup opens GitHub’s public records for this fingerprint. A listed statement is evidence to verify; its presence alone does not establish a valid signature, SLSA level or deployment match. An empty or unavailable lookup does not verify the release.
Verify the downloaded file independently
Save the exact manifest above as application-release-v4.json. Use GitHub CLI to check its digest, the designated repository and the pinned builder identity.
Load the current manifest to prepare verification.
Review the verified source revision and workflow run against the intended release. A signature check does not by itself prove that these bytes were deployed or that all SLSA Build L3 controls are established.
The source archive, Linux image archive and inventory have their own dated build evidence.
The recorded build produced a Linux image. Production hosting and financial execution are not established by that build. Current application capabilities are reported separately below.
GitHub CLI verified these artifact signatures against the pinned builder and source revisions. This page checks the retained review and inventory fingerprints; it does not repeat Sigstore signature verification in the browser. The contract was a precompiled input. This record does not establish a security audit, reserves, custody, settlement or a new SLSA level.
Rechecked 14 September 2026: all three historical artifacts passed separate GitHub CLI verification commands with exit code 0. Inspect the dated results and signed statements ↗ · Original completion record ↗. The command records are unsigned observations; the original artifact signatures retain their build-only scope.
Current NUSD application status
Current application status unknown
NUSD contract address
Unknown
Token identity verification
Unknown
Treasury backing status
Unknown
NUSD service pricing status
Unknown
NUSD quotations
Unknown
Issuance
Unknown
Transfers
Unknown
Settlement
Unknown
Redemption
Unknown
These fields come from the current public application status response. Enabled capabilities describe application configuration; transaction receipts and reserve evidence are separate. The canonical Numina treasury and private provider observations remain in their authenticated views.
The Numina 4 application uses control-plane runtime v1.9.0-rc26. Its signed declaration and control-state receipts can be checked against the public key pinned in this website.
A runtime signature authenticates the service’s declaration. It does not independently establish a build-platform security level or verify the bytes of the referenced SBOM and provenance artifacts.
APPLICATION / SLSA BUILD ASSURANCE
Historical Build L3. Evidence you can verify.
The historical Numina 2.0.0 deployment archive and application inventory from GitHub Actions run 34717406980 · GitHub access required ↗ meet SLSA v1.2 Build Level 3 under our documented self-assessment, with verified builder-signed provenance.
Assessment
Producer self-assessment · September 12, 2026
Scope
The two exact signed artifacts listed in the assessment
The assessed inventory fingerprint is 30434a312366a8869b93e9f27b428ee0e5f385c1bd0e8fc877912a98fe97f792. These downloads preserve that completed build; the current release inventory above may identify a later build. Each later artifact requires its own signature and identity verification.
This is a build-artifact assessment, not third-party certification. It trusts GitHub’s hosted platform, Sigstore and the pinned builder. It does not assess subsequent hosting transformations, the separate rc26 runtime build, financial execution, reserve backing or native-store publication. The official slsa.dev predicate is also used for production.