well known name handling for IBC denoms

[turadg]

What is the Problem Being Solved?

https://github.com/Agoric/agoric-sdk/issues/8879 manages IBC paths but developers need a way to refer to them by well known names

Description of the Design

• Treat channel info as immutable
• We provide a lookup service to get the info for a particular chain
• The set is append-only (the value for a particular chain name is immutable)
• The right to append is held only by BLD Stakers
• If a developer needs the info before it’s on-chain (between staker votes) they look it up through some other trusted source (e.g. Google for the chain’s docs)

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

[dckc]

some recent relevant work: https://github.com/agoric-labs/ag-power-tools/pull/8#issuecomment-2050161852

see also:

• https://github.com/DCFoundation/cosmos-proposal-builder/issues/38

[dckc]

btw "petname" is a bit of a stretch here. It suggests that each person can have their own name for the tokens and that the names can be changed. I suppose those are true from the perspective of the BLD stakers as one aggregate "person", but... it's a stretch.

[dckc]

"well known name handling" might be better