-
Notifications
You must be signed in to change notification settings - Fork 16
Feature: add smart contract verification while deploying #222
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
Pandora Service Contract
Add auth to contract
Feat/service registry mvp
Add `withCDN:bool` to `ProofSetInfo`
All providers getter
feat: add price getter
@wjmelements please review |
Why do you pull the submodules? |
|
||
pushd "$(dirname $0)/.." >/dev/null | ||
source tools/verify-contracts.sh | ||
CHAIN_ID=314159 verify_contracts_batch "$REGISTRY_IMPLEMENTATION_ADDRESS,src/ServiceProviderRegistry.sol:ServiceProviderRegistry,ServiceProviderRegistry Implementation" |
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.
The rest of this file should also use $CHAIN_ID
pushd "$(dirname "$0")/.." >/dev/null | ||
source tools/verify-contracts.sh | ||
|
||
CHAIN_ID=$CHAIN_ID verify_contracts_batch \ |
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.
I don't think you need CHAIN_ID=$CHAIN_ID
.
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.
ah it's not exported. maybe it should be
For
If we called the variable |
ya sorry will remove that in next commit |
okay correcting this |
) Towards FilOzone#254 We are cutting a set of contracts for the M3 milestone. The price changes in FilOzone#239 was done with FilOzone#250 being landed in mind. Since FilOzone#250 is not going to land before in M4, I have temporarily reverted the price changes, so that we keep the price intact for the M3 contract publishing.
Reviewer @rvagg @Kubuxu Closes FilOzone#257 This should reduce the proof storage growth by a factor of 256. If the proving period is 1 day, and the deal lasts 1 year, this mapping will use 2 slots instead of 356. #### Changes * Change provenPeriods to bitmap
Reviewer @rvagg Per a discussion with @jennijuju, we want to make the upgrade process more transparent. This changes upgrades to a two step process. First, we announce the planned upgrade. Then, after the designated time, we can complete the upgrade. The delay gives us time to check the pending implementation address. It also gives users notice even if we are not in communication with them. I also fix FilOzone#259 in this change, because I was already adding tests for `upgradeToAndCall`. I can fix it separately if this change is rejected. After validating that this is a good design that the team likes, I can replicate it for the other proxies in separate PRs. #### Test Plan I tested the new deployment scripts by running them on calibnet. * [announcePlannedUpgrade](https://calibration.filfox.info/en/message/bafy2bzaceb6vpcsy563vhpwig5g6jy7gb6fr2ssxhjgwiagj7k3vbjrg3dg56?t=3) * [upgradeToAndCall](https://calibration.filfox.info/en/message/bafy2bzaceadjmlemjyrv7nmwh5lzavdbntjmywvblrzmtuh3wsyldqlvxbcyo?t=3) #### Changes * announcePlannedUpgrade * update _authorizeUpgrade * new view method for pending upgrade * make gen * add and fix tests covering upgradeToAndCall with migrate * separate announce and upgrade scripts * update implementation-only script --------- Co-authored-by: Rod Vagg <[email protected]>
I removed some stuff from |
Prep v0.2.0 changelog and publish contracts
@wjmelements i am currently making the changes , will let u know once ready for review |
@wjmelements please review , i changed according to this
|
please see #272 @wjmelements |
Automatic Smart Contract Verification Integration
Resolves #214
This pull request implements automatic smart contract verification across deployment scripts in the
service_contracts/tools
directory, utilizing thefilfox-verifier
tool to verify contracts on the Filecoin network. The verification process is controlled via theAUTO_VERIFY
environment variable and enhances deployment reliability through automated post-deployment validation.Changes Made
Known Issue
Proxy contract verification encounters an import path error with PDP Proxy:
Recommended Fix
Update import statement to use the standardized OpenZeppelin naming convention (
@openzeppelin/contracts
) to resolve the verification error and ensure compatibility with the filfox-verifier tool.