The Synchronic Web is a global infrastructure for data assurance, enabling anyone to cryptographically and temporally notarize information. By publishing data to the Synchronic Web, creators and organizations can irrefutably prove the existence and integrity of their data at a specific points in time relative to their trusted anchors. This system supports strong notions of shared global state, provenance, and verifiable history, making it useful for public transparency, cybersecurity, digital media, legal records, intellectual property, and more.
At its core, the Synchronic Web is powered by distributed programs called journals, which maintain immutable, version-controlled logs (records) and continuously synchronize cryptographic metadata with other journals to achieve global consensus.
Please see the full documentation for more details.
This repository serves as the main entry point and documentation hub for the Synchronic Web project. It contains:
- info/
Documentation, quickstart guides, whitepapers, and additional resources for understanding and using the Synchronic Web. - Quick Links to Core Components:
- Journal SDK: Core executable for deploying a Synchronic Web node ("journal").
- Record Logic: Lisp/Scheme functions and data structures for configuring journal logic.
- Service Deployments: Containerized microservices and Docker Compose networks for deploying Synchronic Web applications, including
gateway,explorer,workbench, and the SMB-backedfile-systemprojection service. - Experiment Analysis: Experiments for analyzing performance and robustness of Synchronic Web networks, including a local
compose/social-agent-networkgenerator for multi-node social-agent testing.
sync-services/tests/local-compose.sh smokeis the quickest single-node service-stack validation path for explorer/workbench/gateway/router/file-system.sync-analysis/compose/social-agent-network/generate.pyprovides a local multi-node test network with one full service cluster and one social agent per node.sync-web/info/README.mddocuments the UI screenshot/testing workflow used when the docs site needs fresh explorer/workbench captures.