Notebook session ended
This session ended after eight hours.
Sign in again to continue from where you left off.
Notebook gate offline
The sign-in service is not responding right now.
Wait a minute and try again, or read what is already public from the hub.
Foundational walk through the vest project. Read top to bottom if you're new; no prior context assumed.
More about this project on the Vest hub.
Use when: onboarding to the VEST codebase for the first time; explaining VEST's role in the TimeChain platform to a new team member; deciding which vest-node module owns a verification failure
Use when: tracing why a sequence number is incorrect after concurrent appends; understanding what fields are hashed when computing an entry's integrity hash; adding a range query over audit entries in a given sequence window
Use when: debugging a VestError::InvalidSignature returned from ProofVerifier::verify_signature; constructing a valid AuditSignature for a new signer in an integration test; tracing how current_hash propagates through a multi-depth chain
Use when: verifying that a specific operation is included in the audit log without replaying the full log; computing the root hash from a leaf after receiving a ProofPath over the wire; debugging why MerkleProof::verify returns false for a newly created proof
Use when: understanding why add_state_proof returns Err when a StateProof has operation_count == 0; computing the cumulative size of a timeline's proof chain before serialising for export; verifying a sealed timeline by walking its StateProof chain
Use when: reading verification counters after a batch signature check to determine failure rate; choosing between verify_signature and verify_signature_proof when handling an AuditSignature vs a SignatureProof; diagnosing why verify_proof_path returns Err while verify_merkle_proof returns Valid for the same proof
Use when: implementing a gRPC client that submits or fetches VESTProof messages; adding a new compliance framework marker to an existing AuditEntry; mapping Rust struct fields to their protobuf counterparts when debugging serialisation mismatches
Use when: tagging an audit entry for HIPAA or 21 CFR Part 11 before export as legal evidence; configuring retention policy and legal hold on a specific document timeline; checking which PII types are present in an entry before responding to a GDPR data subject request
Use when: validating that a Roughtime timestamp meets the ±100ms legal precision target from SRS SEAL-NF-003; debugging a TimestampProof that passed threshold but has a radius_us outside acceptable bounds; selecting between RoughtimeProof, RFC3161Proof, and BlockchainProof for a given compliance requirement
Use when: exporting a document timeline as court-admissible evidence after all operations are complete; choosing a SealReason value when closing a timeline due to regulatory retention completion; verifying a SealedTimeline received from an external auditor by checking witness seals
Use when: writing the VEST homepage hero or one-liner; explaining what category VEST sits in to a regulated buyer
Use when: qualifying a VEST sales conversation; deciding which case study to lead with for a given prospect
Use when: answering 'how is this different from a blockchain?'; answering 'why not just use Trillian or a Certificate Transparency log?'
Use when: writing the first cold email or LinkedIn outreach to a head of compliance; filling the one-page sales sheet that goes into a procurement bundle
Use when: explaining why VEST is not on a public sales site yet; framing the path from open-source release to first paying customer