chore: cip68 - Githubissues

few things I am not sure about:

CIP68 specifies description field within metadata for the NFT standard as ? description : bounded_bytes, ; UTF-8, but CIP25 also allows an array. Right now array won't pass the validation. ✅
what about (future) CIP68 metadata with version > 1? Currently version other than 1 won't pass the validation. ✅ (discussed)
Should additional fields within the metadata that are not defined in CIP25 (or off-chain metadata standard) fail the validation? Currently they will pass. ✅ (CIP25 allows additional fields)
Regarding implementation in RYO: If CIP68 metadata (extracted from datum) are present, but fail the validation. Should they be returned anyway or in such a case it will fallback to regular onchain metadata? ✅ (discussed, should not matter as both should never be defined)

blockfrost / openapi