| Crates.io | fuse-core |
| lib.rs | fuse-core |
| version | 1.2.0 |
| created_at | 2026-01-02 19:28:00.601185+00 |
| updated_at | 2026-01-02 19:28:00.601185+00 |
| description | Core VCE protocol implementation for verifiable compliance proofs |
| homepage | |
| repository | https://github.com/Mikebrown0409/project-fuse |
| max_upload_size | |
| id | 2019076 |
| size | 188,215 |
Core VCE protocol implementation for verifiable procedural proofs.
This crate provides the fundamental data structures and operations for creating and verifying Verifiable Compliance Envelopes (VCE).
fuse-core is the stable, infrastructure-only layer of Project FUSE. It proves that a procedural verification ran to completion; it does not assert the truth of the content being verified.
ComplianceSpec: Defines what needs to be verifiedVerifiableComplianceEnvelope: The complete VCE artifactComplianceProof: Zero-knowledge proof structureComplianceResult: Pass/Fail enumerationJournalOutput: Decoded journal data from zkVM executionAdd to your Cargo.toml:
[dependencies]
fuse-core = "1.2.0"
use fuse_core::{ComplianceSpec, VerifiableComplianceEnvelope, Result};
// Create a compliance specification
let spec = ComplianceSpec::new(
"Example claim".to_string(),
"system_hash".to_string(),
Default::default(),
"jurisdiction".to_string(),
"1.0".to_string(),
chrono::Utc::now() + chrono::Duration::days(365),
);
// Load and verify an envelope
let mut envelope = VerifiableComplianceEnvelope::from_file("proof.vce")?;
envelope.verify()?;
let is_compliant = envelope.is_compliant()?;
As of v1.0.0, the core proof format and verification semantics are considered stable. Breaking changes will only be introduced in v2.0.0.
Licensed under the Apache License 2.0. See the main Project FUSE repository for details.