ChronoSeal v0.3.0
ChronoSeal v0.3.0
ChronoSeal continues evolving as a lightweight, privacy-first browser attestation framework focused on raising the operational cost of AI-driven automation, scripted abuse, and stealth browser impersonation — without degrading legitimate user experience.
This release strengthens architectural clarity, deployment usability, runtime configuration, and overall project maturity.
Highlights
Privacy-First Design Expansion
- Expanded design philosophy documentation
- Improved explanation of behavioral continuity verification
- Refined threat-model documentation
- Clearer separation between anti-automation goals and invasive fingerprinting
Runtime & Configuration Improvements
- Added CLI configuration and runtime management support
- Improved deployment flexibility for self-hosted environments
- Better operational control for native and containerized deployments
Documentation Enhancements
- Expanded architecture documentation
- Improved security model explanations
- Refined developer onboarding material
- Better deployment and integration guidance
Infrastructure & Build
- Improved project structure consistency
- Updated CI workflow organization
- Better Docker and system deployment readiness
Security Notes
ChronoSeal remains intentionally:
- Stateless from a long-term tracking perspective
- Ephemeral by design
- Privacy-preserving
- CAPTCHA-free
- Non-invasive
The framework focuses on behavioral continuity and cryptographic proof-of-presence rather than persistent identity tracking.
Build Requirements
Rust
- Rust stable ≥ 1.87
WASM Toolchain
cargo install wasm-packBuild Instructions
Build WASM Client
wasm-pack build wasm --target web --release
mv wasm/pkg frontend/pkgBuild Server
cargo build -p server --releaseDevelopment Mode
bash scripts/dev.shDocker Deployment
docker compose up -d --buildIncluded Components
- Rust Axum server
- WASM cryptographic client
- Behavioral entropy verification
- Blake3 chained attestations
- Ed25519 signing
- Stack-machine execution engine
- SQLite in-memory session engine
Known Philosophy
ChronoSeal is designed to:
- Raise scraping costs
- Increase automation complexity
- Preserve user privacy
- Remain invisible to legitimate users
It is not intended to become a surveillance framework, invasive fingerprinting platform, or CAPTCHA ecosystem.
Repository
GitHub:
https://github.com/thakares/chronoseal-rs
License
Dual licensed under:
- Apache-2.0
- MIT
Full Changelog: v0.2.0...v0.3.0