From bitbadges
Convert, validate, or derive BitBadges addresses — cosmos↔EVM conversion, IBC backing, wrapper, mint-escrow, alias address derivations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bitbadges:addressThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
BitBadges runs on a Cosmos chain with EVM compatibility, so addresses come in two formats and several derived forms. This skill anchors all six common operations so the user doesn't get them wrong.
BitBadges runs on a Cosmos chain with EVM compatibility, so addresses come in two formats and several derived forms. This skill anchors all six common operations so the user doesn't get them wrong.
bb account convert <address> --to <bb1|0x>
bb account validate <address>
bb1... ↔ 0x... is deterministic — same key, two encodings. The CLI handles the bech32/hex math.
| Need | Command |
|---|---|
| Backing address for an IBC denom (smart-token deposits) | bb account alias for-ibc-backing <denom> |
| Wrapper address for a collection | bb account alias for-wrapper <collection-id> |
| Mint-escrow address for a collection | bb account alias for-mint-escrow <collection-id> |
These are protocol-controlled addresses with auto-set approvals. Don't try to write to them directly — use the corresponding flow (IBC backing, mint, etc.).
bb1... with cosmos1... — they are different chains.npx claudepluginhub bitbadges/bitbadges-plugin --plugin bitbadgesCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.