nolus

Prop 348: Add the Solana Metis USDC Remote Lease Controller to the Relayer Allowlist

Summary

This proposal adds the newly deployed Solana Metis USDC protocol's Remote Lease controller contract (nolus1xd9sgdu3lvwm0pzrxg3c3lxwvuwkc6jgzk43zkgzjnndrdp5shvsfv3uzp) to the Solana relayer allowlist (solana_allowed_relayers) in the IBC 02-client parameters on the Nolus Pirin mainnet (pirin-1).

Opening the controller's IBC channel to its Solana counterpart requires it to submit a MsgChannelOpenInit against the Solana light client. The chain's 02-client module treats the signer of that message as a relayer, and the allowlist is fail-closed: until the controller's own address is present, that message is rejected and the channel can never open.

Proposed Changes

MsgUpdateParams replaces the entire 02-client parameter set, so allowed_clients is restated here unchanged at its current on-chain value:

  • 06-solomachine
  • 07-tendermint
  • 09-localhost

solana_allowed_relayers changes from the three existing relayer operator addresses to those same three plus the Remote Lease controller contract address:

  • nolus1cfzkvsvttuazxrm57v8xyl6v56s3ue5q8u8c5a
  • nolus1xmaacd2phwny53wwpexkf865hvjnzugrrlgwmd
  • nolus1t83k9x2cysj7g5lns7j382lhgtzaplpm3c654r
  • nolus1xd9sgdu3lvwm0pzrxg3c3lxwvuwkc6jgzk43zkgzjnndrdp5shvsfv3uzp (Solana Metis USDC Remote Lease controller)

Impact

The three existing relayer operators keep their access unchanged. The added address only grants the Remote Lease controller contract permission to submit Solana light-client channel-handshake messages for its own channel; it grants no other capability. No client type is added or removed, so the IBC connections and channels already in use on pirin-1 are unaffected.

By voting "YES" on this proposal, you agree to authorize the Solana Metis USDC Remote Lease controller to open its IBC channel on the Nolus Pirin mainnet.