REM: DOI + blockchain anchoring for Trillian tree roots — proposal & demo

Hi Trillian team. I’m Lawrence Reilly, author of the REM protocol Internet-Draft (DOI + blockchain anchoring for permanence). REM aims to make auditable ledger roots citable and permanently discoverable.

Why I’m writing: I believe Trillian is an ideal append-only ledger backbone for REM. I’d like to share a 1-page mapping (Trillian → REM DOI metadata → blockchain anchor) and a tiny demo repo so implementers can try this end-to-end.

Links

REM Internet-Draft (IETF): https://www.ietf.org/archive/id/draft-reilly-rem-protocol-00.html

REM GitHub (demo / repo): https://github.com/lawrencejohnreilly-creator/rem-protocol

Trillian repo: https://github.com/google/trillian

Proposed mappings / quick ideas

Use Trillian as the high-throughput append-only ledger; periodically anchor Trillian’s signed tree root into a public blockchain and register that anchor (root hash + metadata) with a DOI.

Store COSE/Trillian inclusion proofs (or pointers to them) inside the DOI metadata so archived artifacts are cryptographically linked to the audit log.

Runtime: clients verify inclusion proofs against Trillian. Archive: REM issues DOI + blockchain anchor for long-term citation and discoverability.

Ask: Would Trillian maintainers/contributors be open to a short 30-minute sketch session to discuss practical integration and a minimal demo plan? I can prepare the 1-page mapping and a small demo script beforehand.

I can prepare a 1-page mapping + a tiny demo repo and share them for a short sketch if anyone’s interested.

Thanks,
Lawrence John Reilly
lawrencejohnreilly@gmail.com
| GitHub: https://github.com/lawrencejohnreilly-creator/rem-protocol