You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems we are assuming dag-json as de default and unique codec that uprtcl objects can have.
The standard JSON serialization problem seems to be already explored in IPLD.
We should probably extend the CID validation functions to be aware of the codec, eventually accept dag-cbor and also consider accepting holochain serializations.
One question I have is the limitation of block size in IPFS, and how the configuration of the file decomposition into blocks is coded into the codec, if it is, which I think it's not.
It seems we are assuming
dag-json
as de default and unique codec that uprtcl objects can have.The standard JSON serialization problem seems to be already explored in IPLD.
We should probably extend the CID validation functions to be aware of the codec, eventually accept
dag-cbor
and also consider accepting holochain serializations.Context
The text was updated successfully, but these errors were encountered: