Partial Set Security: investigate the PFM issue for the reward distribution

[sainoe]

Problem description:

In the PSS reward distribution logic, consumer chains are identified from the IBC path used to send rewards. It allows tracking the rewards received for each consumer chain and allocating them to opted-in validators.

This causes a problem if, for instance, Stride wants to send native Noble USDCs as rewards to the HUB, because it requires unwinding the denom by sending it through Noble. In this scenario, rewards will be allocated to Noble instead of Stride.

For more context, see this comment.

Potential solution

An alternative would be to use the memo or any other field that the sending chain can write to identify the source, which would be durable when passed through Noble's PFM.

PFM code ref

Solving Criteria

Ensure the rewards are allocated to the sender consumer chain

Note: keep in mind backward compatibility while changing the consumer logic