FLUP: Consider migrating feeaddress from vanity address to module account

[Manav-Aggarwal]

Context

From PR #6441 review discussion: #6441 (comment)

@damiannolan suggested considering using a regular module account instead of the current vanity bech32 address (celestia1feeaddress...) for the feeaddress module. Benefits:

• Can leverage existing x/auth query infrastructure
• Vanity address provides no real value to EVM (which uses hex addresses for cross-chain transfers)
• Simpler, more standard Cosmos SDK pattern

Blocker

This migration cannot be done until the following upstream PR is merged and released:

• fix: support 32 byte addresses in remote recv collateral bcp-innovations/hyperlane-cosmos#151

The Hyperlane-Cosmos module currently doesn't support bridging directly to 32-byte module account addresses. Once PR #151 is released, we can migrate.

Action Items

1. Monitor fix: support 32 byte addresses in remote recv collateral bcp-innovations/hyperlane-cosmos#151 for merge/release
2. Once released, create a PR to migrate from vanity address to module account

References

• Original discussion: feat(feeaddress): add feeaddress with protocol-injected tx #6441 (comment)
• x/auth account query: https://github.com/celestiaorg/cosmos-sdk/blob/release/v0.52.x-celestia/x/auth/keeper/grpc_query.go#L133

[linear]

CEL-970

[rootulp]

I don't understand why that's a blocker, module account addresses are 20 bytes for Celestia. See #6454

[Manav-Aggarwal]

Closed by #6456