librotenado specification
Version 0.1 – a draft, not yet stable. Normative statements will use the key words of RFC 2119 and RFC 8174.
| Part | Content | State |
|---|---|---|
| 0001 Base types | amounts, currencies, dates, accounts, bookings | draft, implemented |
| 0002 Events and synchronisation | events, hybrid logical clocks, chains per device, merging; the accounts of a set of books | draft, implemented |
| 0003 Canonical encoding | a byte-exact encoding every implementation can hash (RFC 8785); objects and their types | draft, implemented |
| 0004 Chart of accounts | the harmonised chart: hierarchy with attributes; national charts as translations | draft, implemented (form; the accounts themselves follow) |
| 0005 Documents | invoices, receipts, statements as records of their own; originals as artefacts | draft, implemented |
| 0006 Encryption | end-to-end encryption: an ordered list of members and keys, a books key per member, a chain of keys | draft, proposal |
| 0007 Filings | submissions to authorities: derived from a state of the books, never changed; adapters over HTTPS | draft, proposal |
| 0008 Parties | the organisations and persons books belong to: legal form, registers, tax numbers, roles and shares | draft, implemented |
The reasoning behind the protocol is in the whitepaper.