Should we make proofs into IPLD native links

Open Gozala opened this issue 3 years ago • 1 comments

This is something that comes up every now and then on our side, the fact that that prf are just strings that are serialized CIDs

https://github.com/ucan-wg/spec/blob/692e8aab59b763a783fe1484131c3f40d997b69a/README.md?plain=1#L355

Implies that we have to do pre / post processing to map those back into CIDs. It is really tempting to just follow the DAG-JSON spec to encode them as links instead https://ipld.io/specs/codecs/dag-json/spec/#links which also specifies exact base encoding that helps with hash consistency

This is not critical and has some size costs associated, but it came enough times that I thought it might be worth surfacing

Dec 08 '22 19:12 Gozala

Do you mean wrapping them in {"/": CID}? I think that's a surprising format for people not working in native IPFD, no?

Mar 20 '23 18:03 expede