Struct DataIntegrityProof 

pub struct DataIntegrityProof {
    pub type_: String,
    pub cryptosuite: CryptoSuite,
    pub created: Option<String>,
    pub verification_method: String,
    pub proof_purpose: String,
    pub proof_value: Option<String>,
    pub context: Option<Vec<String>>,
}

Serialized Data Integrity proof.

Fields

type_: String

Must be ‘DataIntegrityProof’

cryptosuite: CryptoSuite

created: Option<String>

verification_method: String

proof_purpose: String

proof_value: Option<String>

context: Option<Vec<String>>

Implementations

impl DataIntegrityProof

pub async fn sign_multi<S>( data_doc: &S, signers: &[&dyn Signer], options: SignOptions, ) -> Result<Vec<DataIntegrityProof>, DataIntegrityError>

where S: Serialize,

Signs data_doc with every signer in signers, producing one DataIntegrityProof per signer.

Fail-fast: if any signer errors, no proofs are emitted and the error is returned immediately.

All signers share the same SignOptions — the per-signer cryptosuite still defaults via Signer::cryptosuite, so a heterogeneous list of signers (Ed25519 + ML-DSA-44) produces one proof per suite automatically.

impl DataIntegrityProof

pub async fn sign<S>( data_doc: &S, signer: &dyn Signer, options: SignOptions, ) -> Result<DataIntegrityProof, DataIntegrityError>

where S: Serialize,

Produces a Data Integrity proof over data_doc.

The cryptosuite is picked from SignOptions::cryptosuite if set, otherwise from Signer::cryptosuite. Canonicalization (JCS or RDFC) is derived from the suite.

pub fn verify_with_public_key<S>( &self, data_doc: &S, public_key_bytes: &[u8], options: VerifyOptions, ) -> Result<(), DataIntegrityError>

where S: Serialize,

Verifies a proof against data_doc using caller-provided public key bytes.

Sync because this is pure CPU — callers who already have the key should not be forced into an async runtime. See verify for the resolver-based async variant.

pub async fn verify<S, R>( &self, data_doc: &S, resolver: &R, options: VerifyOptions, ) -> Result<(), DataIntegrityError>

where S: Serialize + Sync, R: VerificationMethodResolver + ?Sized,

Verifies a proof by resolving the public key from its verificationMethod via a VerificationMethodResolver.

Use did_vm::DidKeyResolver for did:key: URIs (no I/O); plug in a custom resolver for did:web, did:webvh, or any other method. The library also checks that the resolved key’s KeyType matches the proof’s cryptosuite — a cheap guard against “right proof, wrong key” class bugs.

Async because typical resolvers perform I/O (HTTP, cache lookups, HSM introspection).

Trait Implementations

impl Clone for DataIntegrityProof

fn clone(&self) -> DataIntegrityProof

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for DataIntegrityProof

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for DataIntegrityProof

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for DataIntegrityProof

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.