AZIP-24: Track First Prover Attribution for Checkpoints - #64
Open
aminsammara wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
AZIPs/azip-24-first-prover-attribution.md(category: Core, status: Draft).Authored by Santiago Palladino (@spalladino); opened here on his behalf.
Adds a queryable record of the prover that first advanced the proven tip over each checkpoint. The Rollup writes one sparse attribution entry at the end of each proof range that advances the tip, and
getFirstProvenBy(checkpointNumber)resolves any proven checkpoint to the prover whose proof first covered it. This lets a sender or application pay an out-of-protocol tip to the prover that made an L2-to-L1 message available in the outbox, including when that availability came from a proof of only part of an epoch. It adds no protocol rewards and changes no proof validity, message processing, or reward distribution rules.Notes for review:
IRollupinterface. Attribution does not backfill checkpoints proven before activation.discussions-toisN/A, matching prior AZIPs (e.g. AZIP-23, AZIP-16).