ChronoLibrary doesn’t try to reinvent the blockchain. Instead, it quietly rewires how we build on top of it. ChronoLibrary is a toolkit for developers who want to develop blockchain applications with deterministic, reproducible state derived entirely from on-chain data. It introduces a new model for state management, where application logic lives in structured memos and can be replayed by any client.
Developed by All In Bits, the team behind foundational Cosmos infrastructure, ChronoLibrary reflects a long-standing commitment to building modular systems that empower developers. It continues a tradition of creating tools prioritizing transparency, composability, and decentralization.
At the heart of ChronoLibrary are ChronoState and ChronoSync, two tightly integrated components. ChronoState reads memos embedded in blockchain transactions, filters them by prefix, and emits structured events. ChronoSync then provides configurable handling and storage of those events, making it possible to persist application state across various databases.
Let’s take a closer look at how it works.
ChronoState: Deterministic State via Event Sourcing
Memo-Based Event Parsing
ChronoState listens for transactions with specific memo prefixes, allowing developers to define app-specific actions directly on-chain. This approach ensures that only relevant data is processed and all state transitions can be deterministically replayed.
Event Sourcing Model
Instead of maintaining state directly, ChronoState reconstructs it by replaying the sequence of recorded events. This structure provides a clear audit trail and eliminates ambiguity around the state’s origin.
Scoped Execution
Applications can be scoped to specific addresses and prefixes, making managing multiple apps or modules in parallel across the same chain easy.
ChronoSync: Configurable Event Handling and Storage
Pluggable Persistence Layers
ChronoSync supports SQLite, MongoDB, and Postgres out of the box. Developers can choose the backend that best suits their storage and query needs.
Selective Event Routing
Not every event needs to be stored. ChronoSync lets developers decide how to handle each event. Based on application logic, you can store it, forward it, or ignore it entirely.
Advanced Filtering Options
Developers can filter events by sender, receiver, or other transaction metadata, providing complete control over what data is ingested and how it is used.
Looking Ahead
By shifting application logic into verifiable, memo-driven event streams, ChronoLibrary opens new possibilities for architecting apps on-chain. By turning memos into a decentralized event stream, ChronoLibrary enables shared state as a protocol layer rather than a proprietary backend. The result is a system where applications are open by default, frontends are interchangeable, and logic is transparent from top to bottom. You are welcome to explore more or contribute to the repository.