Joel Thorstensson
Joel Thorstensson
Right now the pinning-server has no way of knowing what version of the 3box-js library that is sending the `PIN_DB` message. We should send along the version in this message...
See https://github.com/orbitdb/orbit-db/pull/514 This allows us to have better guarantees of when the store has synced with the pinning-node. The method can also be used for the root store.
Currently the index of CAIPs in the readme frequently get out of date. It would be great if we had a github action that updated the index after a PR...
Readme is out of date and doesn't contain all current CAIPs.
Right now identity objects are stored [within each entry](https://github.com/orbitdb/ipfs-log/blob/master/src/entry.js#L50-L51). This results in a lot of duplicated data when there is a lot of entries created by the same identity. One...
So that we can use [noble-secp256k1](https://github.com/paulmillr/noble-secp256k1) which is an order of magnitude smaller than elliptic.
This package now contains many things related to the JOSE spec. We should modularize it to a few different (to be determined) packages. Suggestion: * `@did-jose/jws` * `@did-jose/jwe` * `@did-jose/jwt`...
The *Supported Encryption Schemes* section states that `XSalsa20-Poly1305` is a supported encryption scheme. However, xsalsa is not and can not be supported by JWE because it lacks support for AAD....
Was revisiting this spec and I noticed that IPLD (IPFS) is being used in a kind half baked way. Some of the data included in the "request object" is assumed...
Timestamp information was not properly propagated to the event log.