From bf447b661945016c873e75b2476e8ab0b7ee37dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mart=C3=ADn=20Volpe?= Date: Wed, 22 Apr 2026 17:23:30 +0200 Subject: [PATCH 1/2] Update smart-contracts.mdx --- contribute-to-celo/release-process/smart-contracts.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contribute-to-celo/release-process/smart-contracts.mdx b/contribute-to-celo/release-process/smart-contracts.mdx index 3171aa4ca..b9aecda96 100644 --- a/contribute-to-celo/release-process/smart-contracts.mdx +++ b/contribute-to-celo/release-process/smart-contracts.mdx @@ -91,7 +91,7 @@ yarn tags:view ```bash # Run from `packages/protocol` in the celo-monorepo PREVIOUS_RELEASE="core-contracts.v${N-1}" -NETWORK=${"baklava"|"alfajores"|"mainnet"} +NETWORK=${"anvil"|"sepolia"|"mainnet"} # A -f boolean flag can be provided to use a forno full node to connect to the provided network yarn release:verify-deployed -n $NETWORK -b $PREVIOUS_RELEASE -f ``` @@ -500,4 +500,4 @@ None Work in progress - \ No newline at end of file + From 5945e37495a67d9a2b891ec17a611e42ff1555b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mart=C3=ADn=20Volpe?= Date: Wed, 22 Apr 2026 17:30:23 +0200 Subject: [PATCH 2/2] Update smart-contracts.mdx --- .../release-process/smart-contracts.mdx | 44 +++++-------------- 1 file changed, 10 insertions(+), 34 deletions(-) diff --git a/contribute-to-celo/release-process/smart-contracts.mdx b/contribute-to-celo/release-process/smart-contracts.mdx index b9aecda96..c169815b4 100644 --- a/contribute-to-celo/release-process/smart-contracts.mdx +++ b/contribute-to-celo/release-process/smart-contracts.mdx @@ -91,7 +91,7 @@ yarn tags:view ```bash # Run from `packages/protocol` in the celo-monorepo PREVIOUS_RELEASE="core-contracts.v${N-1}" -NETWORK=${"anvil"|"sepolia"|"mainnet"} +NETWORK=${"anvil"|"celo-sepolia"|"mainnet"} # A -f boolean flag can be provided to use a forno full node to connect to the provided network yarn release:verify-deployed -n $NETWORK -b $PREVIOUS_RELEASE -f ``` @@ -137,7 +137,7 @@ Use the following script to build and deploy a candidate release. This takes as STORAGE updates are adopted by deploying a new proxy/implementation pair. This script outputs a JSON contract upgrade governance proposal. ```bash -NETWORK=${"baklava"|"alfajores"|"mainnet"} +NETWORK=${"anvil"|"celo-sepolia"|"mainnet"} RELEASE_CANDIDATE="core-contracts.v${N}" yarn release:make -b $RELEASE_CANDIDATE -n $NETWORK -r "report.json" -i "releaseData/initializationData/release${N}.json" -p "proposal.json" -l "libraries.json" ``` @@ -171,7 +171,7 @@ Additionally, include `initialization_data.json` from the CGP if any of the cont ```bash RELEASE_CANDIDATE="core-contracts.v${N}" -NETWORK=${"baklava"|"alfajores"|"mainnet"} +NETWORK=${"anvil"|"celo-sepolia"|"mainnet"} # A -f boolean flag can be provided to use a forno full node to connect to the provided network yarn release:verify-release -p "upgrade_proposal.json" -b $RELEASE_CANDIDATE -n $NETWORK -f -i initialization_data.json ``` @@ -182,7 +182,7 @@ After a release executes via Governance, you can use `release:verify-deployed` a ```bash RELEASE="core-contracts.v${N}" -NETWORK=${"baklava"|"alfajores"|"mainnet"} +NETWORK=${"anvil"|"celo-sepolia"|"mainnet"} yarn release:verify-deployed -n $NETWORK -b $RELEASE -f ``` @@ -342,40 +342,17 @@ Deploying a new contract release should occur with the following process. On-cha T+2w
    -
  1. - On Tuesday: Run the{" "} - smart contract release script{" "} - in order to to deploy the contracts to Baklava as well as submit a - governance proposal. -
      -
    • - Transition proposal through Baklava governance process. -
      • -
    • - Update your forum post with the Baklava PROPOSAL_ID, - updated timings (if any changes), and notify the community in the - Discord #governance channel. -
      • -
    -
    2. -
- - - - T+3w - -
    -
  1. Confirm all contracts working as intended on Baklava.
    2. +
  2. Confirm all contracts working as intended on an Anvil testnet.
  3. Run the{" "} smart contract release script {" "} - in order to to deploy the contracts to Alfajores as well as submit a + in order to to deploy the contracts to Celo Sepolia as well as submit a governance proposal.
  4. - Update your forum post with the Alfajores PROPOSAL_ID, + Update your forum post with the Celo Sepolia PROPOSAL_ID, updated timings (if any changes), and notify the community in the Discord #governance channel.
    5. @@ -383,10 +360,10 @@ Deploying a new contract release should occur with the following process. On-cha - T+4w + T+3w
      -
    1. Confirm all contracts working as intended on Alfajores.
      2. +
    2. Confirm all contracts working as intended on Celo Sepolia.
    3. Confirm audit is complete and make the release notes and forum post contain a link to it. @@ -476,9 +453,8 @@ Each smart contract release governance proposal should be accompanied by a [Gove - Background information. - Link to the release on Github. - Link to the audit report(s). -- Anticipated timings for the Baklava and Alfajores testnets and Mainnet. +- Anticipated timings for the Celo Sepolia testnet and Mainnet. -It's recommended to post as early as possible and at minimum one week before the anticipated Baklava testnet governance proposal date. Make sure to keep the post up to date. All updates (excluding fixing typos) should be communicated to the community in the [Discord](http://chat.celo.org/) `#governance` channel.