Commit 7224a9b
authored
chore: bump contracts to v29 head (#4541)
## What ❔
Bumps contracts to the head commit of
[draft-v29](matter-labs/era-contracts#1419).
This is not a breaking change as the previous commit reflects the same
contract state, but it's harder to assert its validity.
<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->
## Why ❔
<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- The `Why` has to be clear to non-Matter Labs entities running their
own ZK Chain -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->
## Is this a breaking change?
- [ ] Yes
- [ ] No
## Operational changes
<!-- Any config changes? Any new flags? Any changes to any scripts? -->
<!-- Please add anything that non-Matter Labs entities running their own
ZK Chain may need to know -->
## Checklist
<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->
- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev
lint`.1 parent c577d86 commit 7224a9b
1 file changed
+1
-1
lines changed- l1-contracts/README.md+56
- l1-contracts/deploy-scripts/DeployCTM.s.sol+1-1
- l1-contracts/deploy-scripts/DeployL1CoreContracts.s.sol+2-2
- l1-contracts/deploy-scripts/DeployUtils.s.sol+1-1
- l1-contracts/deploy-scripts/upgrade/DefaultEcosystemUpgrade.s.sol+3-3
- l1-contracts/deploy-scripts/upgrade/EcosystemUpgrade_v28.s.sol+1-1
- l1-contracts/deploy-scripts/upgrade/EcosystemUpgrade_v29.s.sol+2
- l1-contracts/deploy-scripts/upgrade/EcosystemUpgrade_v29_2.s.sol+3-3
- l1-contracts/deploy-scripts/upgrade/README.md+2-2
- l1-contracts/package.json+1
- l1-contracts/scripts/verify-contracts.ts+262
- l1-contracts/test/foundry/l1/integration/deploy-scripts/DeployCTMIntegration.s.sol+1-1
- l1-contracts/test/foundry/l1/integration/deploy-scripts/DeployIntegrationUtils.s.sol+1-1
- l1-contracts/test/foundry/l1/integration/l2-tests-in-l1-context/L2Erc20L1Test.t.sol+2-2
- l1-contracts/test/foundry/l1/integration/l2-tests-in-l1-context/L2GatewayL1Test.t.sol+2-2
- l1-contracts/test/foundry/l1/integration/l2-tests-in-l1-context/L2NativeTokenVaultL1Test.t.sol+2-2
- l1-contracts/test/foundry/l1/integration/l2-tests-in-l1-context/_SharedL2ContractL1Deployer.sol+2-2
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/mainnet.toml+61
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/output/mainnet/run-latest.json+2.3k
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/output/mainnet/v29.2-ecosystem.toml+126
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/output/mainnet/v29.2-ecosystem.yaml+163
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/output/mainnet/verification-logs.txt+235
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/output/stage/v29.2-ecosystem.toml+7-7
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/output/stage/v29.2-ecosystem.yaml+12-7
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/output/stage/verification-logs.txt+8-8
- l1-contracts/upgrade-envs/v0.29.2-interopA-ff/stage.toml+1-1
- l1-contracts/upgrade-system/facets.ts+2-2
0 commit comments