Native rewards distribution protocol

[maurolacy]

Alternatively to sending the rewards to Babylon using ICS-020 (#96), we can keep the rewards on the Consumer, for simplicity and a cleaner / simpler user experience.

At the same time, we can still make Babylon to process the distribution table across delegators; for ownership / control, commissions, etc. (Or we can do all the processing on the Consumer).

For this, we can establish a custom IBC message to send the distribution table across FPs to Babylon (instead of sending it on the Memo field of the ICS-020 transfer). And then another custom messages in the opposite direction, to send back the distribution table across delegators to the FPs. (Or send the distribution table and funds to the btc-staking contract, and process / distribute everything locally).

There's WIP for this already in the https://github.com/babylonlabs-io/babylon/tree/f/consumer-reward-distribution branch. Also, the babylon-contract InstantiationMsg has the optional transfer_info field (

babylon-contract/contracts/babylon/src/msg/contract.rs

Line 58 in 9fdc9a1

pub transfer_info: Option<crate::msg::ibc::IbcTransferInfo>,

) which can be used to disable ICS-020 entirely.