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
In my opinion, it should not be the responsibility of the CIP to specify a maximum character length as part of the spec; or, at the very least, this should be dramatically increased. If an explorer wants to only store the first 1000 characters, and then provide a link to the full content hosted elsewhere, that would be an acceptable decision of the tool, but should not be an imposition imposed by the specification. In particular, 1000 characters is extremely limiting.
The text was updated successfully, but these errors were encountered:
I'll leave this here, because it is most likely related: I was trying to figure out why the HF governance proposal was creating a hash mismatch in db-sync and would therefore not be included as metadata json in endpoints on Koios. Turns out db-sync enforces a way too low character limit on governance action metadata: IntersectMBO/cardano-db-sync#1928 (comment)
The CIP119 limit was probably set for a similar reason.
Maybe it is time to rethink how to handle off-chain metadata and if it needs to be in db-sync at all?
In my opinion, it should not be the responsibility of the CIP to specify a maximum character length as part of the spec; or, at the very least, this should be dramatically increased. If an explorer wants to only store the first 1000 characters, and then provide a link to the full content hosted elsewhere, that would be an acceptable decision of the tool, but should not be an imposition imposed by the specification. In particular, 1000 characters is extremely limiting.
The text was updated successfully, but these errors were encountered: