FIP-XXXX: Enable smart contract notifications for Direct Data Onboarding (DDO) #1180
+291
−0
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
rvagg
force-pushed
the
rvagg/unlock-ddo
branch
2 times, most recently
from
2550d3b to
51b7ac7
Compare
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 FIP removes the restriction that currently limits Direct Data Onboarding (DDO) sector content notifications to only the built-in storage market actor (f05). By enabling any smart contract to receive these notifications when data is committed to sectors, this proposal unlocks new possibilities for custom marketplaces, data DAOs, and other data-driven applications on Filecoin. The change maintains security through storage provider controls while acknowledging the operational responsibility for managing gas consumption risks when interacting with untrusted contracts.
Discussion: #1181