FIP: Removal of the ProveReplicaUpdates method from the miner actor #1152
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
rvagg
requested review from
jennijuju,
anorth,
jsoares,
TippyFlitsUK,
momack2,
lanzafame and
dannyob
as code owners
lanzafame
approved these changes
May 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new FIP proposing the removal of the
ProveReplicaUpdatesmethod (Method 27) from the miner actor.The method has been effectively superseded by
ProveReplicaUpdates3, which provides the same Snap Deals functionality with greater flexibility. On-chain analysis shows no active usage of this method for at least six months, with storage providers having fully migrated to the newer method.This follows the same pattern as FIP-0101 and FIP-0103, which removed other deprecated methods. The change will reduce technical debt and simplify the protocol without impacting functionality.
Discussion thread: #1151