Skip to content

Should we make proofs into IPLD native links #137

@Gozala

Description

@Gozala

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

spec/README.md

Line 355 in 692e8aa

| `prf` | `String[]` | Proof of delegation (hash-linked UCANs) | No |

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions