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

Add Support for Escrowed Checkpoint Signature Rewards #1218

Open
karlem opened this issue Nov 27, 2024 · 0 comments
Open

Add Support for Escrowed Checkpoint Signature Rewards #1218

karlem opened this issue Nov 27, 2024 · 0 comments

Comments

@karlem
Copy link
Contributor

karlem commented Nov 27, 2024

Problem

In a child subnet, 10 validators sign a checkpoint. However, as a relayer, I only need to submit 7 signatures to meet the quorum. To save costs, I omit the remaining 3 signatures. From the parent subnet’s perspective, only 7 validators appear to have participated, even though 10 actually did.

Alternatively, the relayer might submit the checkpoint as soon as the quorum is reached without waiting for additional signatures. This results in validators who signed later not receiving rewards for their participation.

Proposed Solution

Allow relayers to append additional signatures after submitting a checkpoint ID to the parent subnet. Relayers should have an economic incentive to do so.

To enable this, rewards for checkpoint signatures should be escrowed for a grace period. This gives the relayer time to gather and submit additional signatures, ensuring fair reward distribution among all signing validators.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant