assets-ext-regression

To verify yaci-store asset metadata API responses, run regression checks that compare CIP-26 and CIP-68 outputs byte-for-byte against the Cardano Foundation token metadata registry to detect wire-format divergences.

Token metadata differs between yaci-store and tokens.cardano.org due to wire-format regressions in CIP-26 or CIP-68 responses; byte-level comparison against the CF V2 API identifies the exact data divergences causing the mismatch.

Running CIP-26 and CIP-68 metadata regression tests requires reachable yaci-store endpoints, configured comparison sources from the Cardano Foundation registry, and regression scripts to execute the byte-level compatibility checks.

Wire-shape regression testing for Cardano token metadata APIs compares yaci-store output against CF V2 API responses byte-for-byte to identify unexpected structural or data divergences before a release.

You can validate an assets-ext code change before a yaci-store release by running regression sweeps that compare CIP-26 and CIP-68 API responses against the Cardano Foundation registry to ensure byte-level compatibility.

If yaci-store assets-ext metadata regression tests fail, use the end-to-end verification workflow to interpret results and perform targeted troubleshooting on the specific CIP-26 or CIP-68 metadata divergences detected.