SECURITY.md tells in full what ledgdex guarantees, and the trust that you still need. In short:
tampering is evident a changed byte breaks verification at that line, in Python and in the browser
rewrites are found ledgdex check keeps copies and follows receipts: signed proof of a rewrite
only the key holder signs strict Ed25519, and keys never leave your computer (600 files, sealed in browsers)
messages count one time the state ignores a signed message that a ledger records two times
hostile ledgers are data no script or link injection, no reads of local files, limits on size and depthWhat you must do:
- Keep owner keys offline, with a backup.
- Use device keys each day.
- Install the fast extra on each computer that signs.
- Run ledgdex check each day.
- Report problems to the address in SECURITY.md before you publish them.