-
Notifications
You must be signed in to change notification settings - Fork 49
More deterministic deploys #1523
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
base: dev
Are you sure you want to change the base?
Conversation
❌ Deploy Preview for kleros-v2-university failed. Why did it fail? →
|
❌ Deploy Preview for kleros-v2 failed. Why did it fail? →
|
|
❌ Deploy Preview for kleros-v2-neo failed. Why did it fail? →
|
Important Review skippedAuto reviews are limited to specific labels. Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Code Climate has analyzed commit 3e23959 and detected 1 issue on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
|
[WIP]
Known issue currently
We are deploying upgradable proxies and we want the proxy to have a deterministic address.
But while testing, we can see that the proxy's address would change depending on the implementation's initializer's parameters. We understand where the problem is coming from but not entirely sure about the best solution.
PR-Codex overview
The focus of this PR is to refactor contracts and scripts related to arbitration and staking, update deployment functions, and improve contract initialization.
Detailed summary
SortitionModuleBase
,SortitionModule
, andSortitionModuleNeo
._deployer
parameter inTestERC20
constructor.KlerosCore
andKlerosCoreNeo
.deployTokens.ts
and00-home-chain-arbitrable.ts
.hardhat.config.ts
.