Skip to content

CAIP-390: Minimal Cross-Chain Asset Metadata Standard#390

Merged
bumblefudge merged 1 commit intoChainAgnostic:mainfrom
ldclabs:main
Feb 2, 2026
Merged

CAIP-390: Minimal Cross-Chain Asset Metadata Standard#390
bumblefudge merged 1 commit intoChainAgnostic:mainfrom
ldclabs:main

Conversation

@zensh
Copy link
Copy Markdown
Contributor

@zensh zensh commented Dec 22, 2025

No description provided.

Signed-off-by: 0xZensh <txr1883@gmail.com>
@bumblefudge
Copy link
Copy Markdown
Collaborator

Hey! This is promising, and I like the basic idea. I have some questions, although none of them have a right answer or even one I prefer:

  • is an array of strings enough for "locations"? I wonder if people might prefer some kind of ordering or ranking (JSON array order is famously unstable across languages and type systems), or some other kind of metadata (are some locations "preferred" or "canonical"? are some specifically non-canonical/secondary?)
  • can non-https urls go in external_url? for example, an IPFS native URL, or an ENS-based mutable pointer? are there any security considerations about bare-IPv4 addresses or non-ICANN addresses?

@pelle and @ajunge from Nota Bene have a similar use case and it might be looking at a system they proposed a year or two ago for having a canonical registry for metadata based on the more free-form, human-readable namespaces documentation. Maybe there's some overlap there? At least worth reviewing as adjacent prior art.

Copy link
Copy Markdown
Contributor

@obstropolos obstropolos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a great way to consolidate this sort of thing if adopted / make it nice and clean.

I'm fine approving as a draft for now.

Copy link
Copy Markdown
Collaborator

@bumblefudge bumblefudge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well, no word from the NB crew, let's just merge as draft and they can open PRs later if they want to align this with existing work in prod or otherwise lobby for changes!

@bumblefudge bumblefudge merged commit cb1f3b8 into ChainAgnostic:main Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants