chunningham
chunningham
@mnzaki this is something we should look at in the typeorm sdk storage stuff
Current status: only actions and components changed are the ones related to authentication requests. Further action changes will wait for #1325 to be merged in order to avoid duplicating work....
@koivunej, `libipld` does indeed have a `Store` trait, which seems intended to act as the API for any IPFS implementation (assuming that's what you're referring to), however it's IMO not...
That approach makes a lot of sense IMO, I was just thinking about using libipld to handle the protobuf parts to reduce dependancies and to make some things clearer (e.g....
makes sense, every header except `ucv`, `alg` and `typ` encoded together as dag-json or dag-cbor? An adjacent question about varsig, if we're encoding a self-describing/framed data structure, is it necessary...
Strong agree with reorganizing the `e` block into the top level, its quite intuitive (the `e` block already was "top-level" info about the KEL). The only weirdness is the `te`...
Just to fill in the inference gap, the key difference (pun intended) is that in `did:key`, there is a 1:1 correspondence of DID to Pubkey and the public key itself...
Unless I'm misunderstanding, in any versioned protocol breaking versions by definition are not traversable forwards-wise by deployments which are not up to date. The version string which can be peeked...
being worked on in KID0002
Support for restoring this field in the ICP event to the KIDs is unopposed, a PR should on the way to do so.