Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make relayer_reward_per_message field an option #2632

Merged
merged 2 commits into from
Oct 19, 2023

Conversation

svyatonik
Copy link
Contributor

related to #2486
extracted from #2605
follow up for #2613

In #2613 I've missed the fact that unregistered relayers may still deliver messages. We still need to reward such relayers, but how to fill the relayer_reward_per_message then? Unregistered relayer can't specify this value. We could use some special value (u64::MAX) for such entries or we could use Option<u64>. 1-byte overhead looks not that large, so probably it is fine to use Option<u64>, because it is looks more natural.

I'm also thinking of replacing all u64 in messages runtime storage with Compact<u64>, it shall make values even smaller.

@svyatonik svyatonik merged commit 469a5a0 into master Oct 19, 2023
@svyatonik svyatonik deleted the make-relayer-reward-per-message-an-option branch October 19, 2023 06:35
bkontur pushed a commit that referenced this pull request May 7, 2024
* relayer_reward_per_message is now Option<RelayerRewardAtSource>

* fixed benchmarks compilation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants