Tests: passed: suite/signing.test.ts on duckdb replicas pass every case of the suite of signed deltas; passed: suite/signing.test.ts on postgres replicas pass every case of the suite of signed deltas; passed: suite/signing.test.ts on sqlite replicas pass every case of the suite of signed deltas
Under signed trust an epoch MUST be adopted only from a proposer on the list (where there is one) whose key signed it, valid when the epoch's bound id was made; an epoch that is not signed, one signed by a key of another replica and one from a replica off the list MUST be refused with a sentence, and the one that is signed MUST be adopted and end with the same files.
Enforced (check): .github: cd commons/anyfs-sql && bun run verify — suite/signing.test.ts
Under signed trust a dump MUST be replayed only with the manifest its replica signed (<sha256>:<rows>:<blobs> under the domain anyfs-dump/1): a dump that is not signed, one that is not the text the manifest was signed for, one whose counts are wrong, one signed by a key that is not the replica's, one from a replica off the list and one that holds a row of a replica off the list MUST each be refused and write nothing, and the manifest MUST be written to and read back from <replica>.sql.sig.
Enforced (check): .github: cd commons/anyfs-sql && bun run verify — suite/signing.test.ts
A raw import by the real sqlite3 under signed trust MUST write no row of a replica the roster does not name (the trust table and its trigger), and the limit MUST be said: the database cannot check a signature, so what a raw import brings in from a replica of the roster is vouched for by nothing but that filter, and the library's import is what holds the signature.
Enforced (check): .github: cd commons/anyfs-sql && bun run verify — suite/signing.test.ts
Given a dump of a replica off the roster replayed by the real sqlite3 into a signed database, When the files are read, Then none of its rows is there, per FR-004.
Given a dump and the manifest its replica signed, When the text is changed by one byte, Then the import refuses it, per FR-003.
Keys are held as in the core: Ed25519, a roster of entries with a validity window, a key identified by the first 16 hexadecimal digits of the SHA-256 of its 32 bytes.