Skip to content

ChronoSeal v1.0.0 - Protocol Freeze & Audit Readiness

Choose a tag to compare

View all tags
@thakares thakares released this 30 May 14:44
· 19 commits to main since this release
v1.0.0
1a58ef9

ChronoSeal v1.0.0 - Protocol Freeze & Audit Readiness

ChronoSeal v1.0.0 marks the first stable protocol release of ChronoSeal as a daemon-first browser attestation service.

This release completes the v1 hardening cycle, introduces protocol stability guarantees, adds black-box replay testing, fuzzing infrastructure, operational documentation, and establishes the long-term public contract for third-party integrations.

ChronoSeal is designed as a first-class Unix daemon.

The supported integration surface is the ChronoSeal protocol and REST API. Internal implementation details remain private and may evolve independently.

Highlights

Protocol Stability

The ChronoSeal protocol has been formalized and documented.

Added:

  • docs/PROTOCOL.md
  • docs/PROTOCOL_STABILITY.md
  • docs/WRAPPER_GUIDE.md

The following surfaces are now considered part of the public contract:

  • /init
  • /hb
  • JSON request/response schemas
  • VM opcode semantics
  • Mutation commitment rules
  • Hash-chain progression rules

Third-party wrappers should depend only on documented protocol behavior and REST APIs.

Black-Box Replay Testing

Introduced:

chronoseal-replay

A standalone protocol validation utility that interacts with a running chronoseald instance exclusively through the public REST API.

Supported validation scenarios include:

  • Valid session progression
  • Replay attack rejection
  • Invalid signatures
  • Invalid VM execution traces
  • Invalid mutation commitments
  • Timestamp drift validation
  • Concurrent heartbeat handling
  • Rate-limiter verification

This tool enables deterministic protocol validation and regression testing without exposing internal implementation details.

Fuzz Testing Infrastructure

Added a dedicated fuzzing workspace:

fuzz/

Current fuzz targets:

  • VM execution engine
  • Environment decoder
  • Protocol parsing and validation

The fuzzing framework is built using:

cargo-fuzz
libfuzzer-sys

and is intended to support long-running adversarial testing and future CI integration.

Property-Based Testing

Added property-based testing coverage for:

  • VM execution stability
  • Environment decoding robustness

Randomized testing validates that core deterministic components remain panic-free across arbitrary inputs.

Documentation

Added:

  • docs/OPERATIONS.md
  • docs/SECURITY_ASSUMPTIONS.md
  • docs/WHY_IT_FAILS.md
  • docs/PROTOCOL.md
  • docs/PROTOCOL_STABILITY.md
  • docs/WRAPPER_GUIDE.md

These documents define:

  • Protocol behavior
  • Operational deployment guidance
  • Security boundaries
  • Failure analysis
  • Wrapper development guidance
  • Long-term protocol compatibility expectations

Security & Reliability Hardening

Implemented:

  • Server-side VM verification
  • Session-state concurrency protection (CAS)
  • Replay validation improvements
  • Protocol verification enhancements
  • Storage scalability improvements
  • Improved observability and metrics support

The protocol now enforces:

  • Stateful progression
  • Mutation verification
  • VM execution verification
  • Replay resistance
  • Concurrent update protection

Architecture

ChronoSeal remains intentionally:

  • Daemon-first
  • Protocol-first
  • API-first
  • Unix-first

ChronoSeal is not:

  • A Rust SDK
  • An embeddable library
  • A framework

The intended deployment model remains:

chronoseald
      ↓
REST API
      ↓
Applications / Wrappers

This release formalizes that philosophy and freezes the protocol rather than internal implementation details.

New Components

Added

  • chronoseal-replay/
  • fuzz/
  • docs/OPERATIONS.md
  • docs/PROTOCOL.md
  • docs/PROTOCOL_STABILITY.md
  • docs/SECURITY_ASSUMPTIONS.md
  • docs/WHY_IT_FAILS.md
  • docs/WRAPPER_GUIDE.md

Updated

  • shared/src/vm.rs
  • shared/tests/

Upgrade Notes

This release introduces protocol stability guarantees for future wrapper and integration development.

Consumers should rely exclusively on:

  • Documented protocol behavior
  • Documented REST APIs
  • Published protocol specifications

Internal implementation details remain subject to change.

Looking Ahead

Post-v1.0 development will focus on:

  • Long-running fuzzing
  • External security review
  • Protocol validation
  • Performance improvements
  • Operational tooling
  • Additional observability

without breaking the public protocol contract.

Version: v1.0.0

Status: Stable Protocol Release

Project Type: Daemon-first Browser Attestation Service

Compatibility: Protocol v1

Assets 2
Loading
0 Join discussion