Open OR13 opened 2 years ago
That makes sense, I think the idea of the emulator is to play around with formats to inform the specs and also act as something like a validator in the future. That's why the ccf.py
part isn't actually hooked up to a real CCF instance but rather generates a fake receipt equivalent. Can we do the same for other ledger types? I fear that by just importing vendor libraries it hides all the details and makes local testing and validation harder. What do you think?
EDIT: I think when adding a new ledger type there should also be an accompanying spec for the receipt details (mostly format and validation), whether informal in some .md file (not sure if that belongs in this repo though) or as extension to the receipts I-D.
https://github.com/microsoft/scitt-api-emulator/blob/main/scitt_emulator/ccf.py
The CCF interface is well defined, I am interested in adding support for Amazon QLDB and Trillian at this layer.
It looks to me that this must be done in python code for now.
Any advice on starting this work?
I was thinking to port some of the work I prototyped in https://github.com/transmute-industries/did-eqt