-
Notifications
You must be signed in to change notification settings - Fork 28
PDP service contract whitelist #545
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
Conversation
cc @rvagg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fair enough if this is only for the synapse branch, but maybe it should be a config option rather than defined in code?
also go fmt
apparently not right in here somewhere
I see where you're coming from but since it only applies to the public service I am ok with leaving it as a build constant like the existing verifier. Merging synapse back to main will require some conceptual merging of the public service construct and we can revisit this question then as part of that. |
4c6c439
to
d8c7670
Compare
Using current Alpha release FilecoinWarmStorageService contract address on calibnet
d8c7670
to
22b172a
Compare
This provides some protection for curio PDP operators running publically accessible PDP services. Only the pandora PDP service contract is allowed upon proofset creation over the publically available PDP service.
The whitelist is network dependent -- only calibnet specified as pandora only launched on calibnet.
Closes FilOzone/synapse-sdk#34