[feature] CIP-26 / CIP-68 / CIP-113 support (Asset Store)

[matiwinnetou]

Just like you have off-chain pool metadata we would like to request a feature that you would develop an "asset" store module, effectively adding CIP-26 / CIP-68 / CIP-113 support.

The idea is to mirror what Yaci-Store does when it comes to Asset Store: bloxbean/yaci-store#870

Now that Db-Sync is modularised it should be possible.

Main motivation is e.g. GraphQL since GraphQL API on Cardano is based on DbSync. https://github.com/cardano-foundation/cardano-graphql/, at the moment it has far from ideal support for native assets and it could be way more robust once you provide official support for asset module / store in DB Sync.

Regarding CIP-113 (soon on mainet, currently pending audit), to learn more about this you can also read / investigate:

• https://github.com/cardano-foundation/cip113-programmable-tokens
• feat: add CIP-113 programmable token support cardano-foundation/cf-token-metadata-registry#68

[Cmdv]

Thanks @matiwinnetou . This looks doable — the off-chain pool / vote metadata features is a good comparison.

The pattern is in insert_options in the config (see doc/configuration.md). offchain_pool_data and offchain_vote_data are the closest match — background fetchers, retry queues, hash validation, and the vote side already does CIP-100/108/119. A new asset metadata feature would fit in the same shape and would be opt-in (off by default) like those two are.

The yaci-store PR is pretty big though, so maybe it would be ideal to split it up? For example:

1. CIP-68 first — it's all on-chain and we already store the inline datums, so it's mostly about structuring the data. Smallest job.
2. CIP-26 next — needs a GitHub sync worker, but the off-chain pattern fits.
3. CIP-113 later — the spec is still in CIPs (#444), audit is pending, and it's not on mainnet. Yaci-store ships it off by default for the same reason. Probably best to wait.

Few things we'd need to know:

1. Which CIP is the priority for graphql? 68 is cheapest, 26 covers more.
2. Have you talked to the cardano-graphql folks? Want to make sure they're on board with consuming this from db-sync vs going straight to cf-token-metadata-registry V2.
3. Does the schema need to match the V2 API shape, or is db-sync-style naming fine if consumers reshape it?
4. For CIP-113 — ok to wait for the spec/audit, or do you want it disabled-by-default like yaci-store?
5. Is V2-API-shape compatibility (subject / extensions / query priority etc.) a hard requirement on the db-sync schema, or is db-sync-idiomatic naming acceptable as long as the consumer can shape the response?
6. For CIP-113 specifically — happy to defer until after spec finalisation + audit, or do you want it landed disabled-by-default like yaci-store does?

[matiwinnetou]

@Cmdv

1/ CIP-26 and CIP-68 are priority , CIP-113 officially is not on main-net yet, we use test data and test smart contract for testing
2/ Yes I am in contact and cardano-graphql maintainer
3/ Schema you can dedide completely on your own, it needs to make sense within realm of db-sync
4/ CIP-113 is only disabled by default for now because it is not on main-net yet, once it is, it will be re-enabled by default
5/ In the meantime in Yaci-Store decision was made to disable by default CIP-26 as well but honestly you don't have to follow the same logic. The idea behind this is that while not officially but unofficially CIP-26 is kinda deprecated (supported but not encouraged) and perhaps we will work with CIP Editors soon to see how we can soft deprecate it. However, anybody can enable CIP-26 via a configuration parameter
6/ No V2 Schema is absolutely not requirement, its more important that you store relevant data, name, description, logo. Keep in mind those fields mean different things depending if this is CIP-26 or CIP-68 which complicates a bit situation, e.g. LOGO is base64 in case of CIP-26 but in case of CIP-68 its just url.
7/ Yes, feel free to defer CIP-113 , we are expecting audit to be completed within 2 weeks though and mainnet-release target at the moment is ca. 06.2026