diff --git a/build/tools/contracts/uniswap-contracts.mdx b/build/tools/contracts/uniswap-contracts.mdx index 8feae19544..06266b6f11 100644 --- a/build/tools/contracts/uniswap-contracts.mdx +++ b/build/tools/contracts/uniswap-contracts.mdx @@ -1,11 +1,11 @@ --- title: Uniswap Contracts -description: Uniswap v4 and v3 contract addresses on Celo Mainnet and the Celo Sepolia Testnet +description: Uniswap v4 contract addresses on Celo Mainnet and Celo Sepolia, and v3 addresses on Celo Mainnet id: uniswap-contracts --- -The latest versions of Uniswap v4 and v3 contracts are deployed at the addresses listed below, on both Celo mainnet and the Celo Sepolia testnet. Integrators should no longer assume that they are deployed to the same addresses across chains and be extremely careful to confirm mappings below. +The latest versions of Uniswap v4 and v3 contracts are deployed at the addresses listed below. Uniswap v4 is on both Celo mainnet and the Celo Sepolia testnet; Uniswap v3 addresses are listed for Celo mainnet only. Integrators should no longer assume that they are deployed to the same addresses across chains and be extremely careful to confirm mappings below. ## Uniswap V4 Contracts @@ -30,19 +30,21 @@ Two test routers (`PoolSwapTest` at [0x42592B9fFA3be9351cf06EC499e28b88a4A99f50] ## Uniswap V3 Contracts -| Contract | CELO Address | Alfajores Address | -| ---------------------------------- | ------------------------------------------ |--------------------------------------------| -| UniswapV3Factory | [0xAfE208a311B21f13EF87E33A90049fC17A7acDEc](https://celoscan.io/address/0xAfE208a311B21f13EF87E33A90049fC17A7acDEc) | [0x229Fd76DA9062C1a10eb4193768E192bdEA99572](https://alfajores.celoscan.io/address/0x229Fd76DA9062C1a10eb4193768E192bdEA99572) | -| Multicall2 | [0x633987602DE5C4F337e3DbF265303A1080324204](https://celoscan.io/address/0x633987602DE5C4F337e3DbF265303A1080324204) | [0x692A12C7C167c44e54c3d381CA3EE91F058Dc404](https://alfajores.celoscan.io/address/0x692A12C7C167c44e54c3d381CA3EE91F058Dc404) | -| ProxyAdmin | [0xc1b262Dd7643D4B7cA9e51631bBd900a564BF49A](https://celoscan.io/address/0xc1b262Dd7643D4B7cA9e51631bBd900a564BF49A) | [0xE4d1eBb97Fe5fabFaBbB8C004C424EE12dE8A07d](https://alfajores.celoscan.io/address/0xE4d1eBb97Fe5fabFaBbB8C004C424EE12dE8A07d) | -| TickLens | [0x5f115D9113F88e0a0Db1b5033D90D4a9690AcD3D](https://celoscan.io/address/0x5f115D9113F88e0a0Db1b5033D90D4a9690AcD3D) | [0xFdACaEfB0f85C9BE9d319023453cC85C812d7e1E](https://alfajores.celoscan.io/address/0xFdACaEfB0f85C9BE9d319023453cC85C812d7e1E) | -| NFTDescriptor | [0xa9Fd765d85938D278cb0b108DbE4BF7186831186](https://celoscan.io/address/0xa9Fd765d85938D278cb0b108DbE4BF7186831186) | [0xE3da4F834D45b27AF95600e6546991dC3B50adAC](https://alfajores.celoscan.io/address/0xE3da4F834D45b27AF95600e6546991dC3B50adAC) | -| NonfungibleTokenPositionDescriptor | [0x644023b316bB65175C347DE903B60a756F6dd554](https://celoscan.io/address/0x644023b316bB65175C347DE903B60a756F6dd554) | [0xB00B8C3aB078EB0f7DeC6cE19c1a1da5bf4f8d7e](https://alfajores.celoscan.io/address/0xB00B8C3aB078EB0f7DeC6cE19c1a1da5bf4f8d7e) | -| TransparentUpgradeableProxy | [0x505B43c452AA4443e0a6B84bb37771494633Fde9](https://celoscan.io/address/0x505B43c452AA4443e0a6B84bb37771494633Fde9) | [0x9ddD6325FBE93A715B422883cED853CD843f217C](https://alfajores.celoscan.io/address/0x9ddD6325FBE93A715B422883cED853CD843f217C) | -| NonfungiblePositionManager | [0x3d79EdAaBC0EaB6F08ED885C05Fc0B014290D95A](https://celoscan.io/address/0x3d79EdAaBC0EaB6F08ED885C05Fc0B014290D95A) | [0x0eC9d3C06Bc0A472A80085244d897bb604548824](https://alfajores.celoscan.io/address/0x0eC9d3C06Bc0A472A80085244d897bb604548824) | -| V3Migrator | [0x3cFd4d48EDfDCC53D3f173F596f621064614C582](https://celoscan.io/address/0x3cFd4d48EDfDCC53D3f173F596f621064614C582) | [0x245d3F47F55c532dbE9340368855Be631B162cfd](https://alfajores.celoscan.io/address/0x245d3F47F55c532dbE9340368855Be631B162cfd) | -| QuoterV2 | [0x82825d0554fA07f7FC52Ab63c961F330fdEFa8E8](https://celoscan.io/address/0x82825d0554fA07f7FC52Ab63c961F330fdEFa8E8) | [0x3c1FCF8D6f3A579E98F4AE75EB0adA6de70f5673](https://alfajores.celoscan.io/address/0x3c1FCF8D6f3A579E98F4AE75EB0adA6de70f5673) | -| SwapRouter02 | [0x5615CDAb10dc425a742d643d949a7F474C01abc4](https://celoscan.io/address/0x5615CDAb10dc425a742d643d949a7F474C01abc4) | [0x8C456F41A3883bA0ba99f810F7A2Da54D9Ea3EF0](https://alfajores.celoscan.io/address/0x8C456F41A3883bA0ba99f810F7A2Da54D9Ea3EF0) | -| Permit2 | [0x000000000022D473030F116dDEE9F6B43aC78BA3](https://celoscan.io/address/0x000000000022D473030F116dDEE9F6B43aC78BA3) | [0x000000000022D473030F116dDEE9F6B43aC78BA3](https://alfajores.celoscan.io/address/0x000000000022D473030F116dDEE9F6B43aC78BA3) | -| UniversalRouter | [0x643770E279d5D0733F21d6DC03A8efbABf3255B4](https://celoscan.io/address/0x643770E279d5D0733F21d6DC03A8efbABf3255B4) | [0x84904B9E85F76a421223565be7b596d7d9A8b8Ce](https://alfajores.celoscan.io/address/0x84904B9E85F76a421223565be7b596d7d9A8b8Ce) | -| v3StakerAddress | [0x6586FB35393abF7Ff454977a9b3c912d218791C6](https://celoscan.io/address/0x6586FB35393abF7Ff454977a9b3c912d218791C6) | [0x8AC47D3e65a3e6aD14596ee7d18ad1d1aA53208F](https://alfajores.celoscan.io/address/0x8AC47D3e65a3e6aD14596ee7d18ad1d1aA53208F) | +Uniswap v3 has no published Celo Sepolia deployment. To test against Uniswap on Celo Sepolia, use the v4 contracts above. + +| Contract | CELO Address | +| ---------------------------------- | ------------------------------------------ | +| UniswapV3Factory | [0xAfE208a311B21f13EF87E33A90049fC17A7acDEc](https://celoscan.io/address/0xAfE208a311B21f13EF87E33A90049fC17A7acDEc) | +| Multicall2 | [0x633987602DE5C4F337e3DbF265303A1080324204](https://celoscan.io/address/0x633987602DE5C4F337e3DbF265303A1080324204) | +| ProxyAdmin | [0xc1b262Dd7643D4B7cA9e51631bBd900a564BF49A](https://celoscan.io/address/0xc1b262Dd7643D4B7cA9e51631bBd900a564BF49A) | +| TickLens | [0x5f115D9113F88e0a0Db1b5033D90D4a9690AcD3D](https://celoscan.io/address/0x5f115D9113F88e0a0Db1b5033D90D4a9690AcD3D) | +| NFTDescriptor | [0xa9Fd765d85938D278cb0b108DbE4BF7186831186](https://celoscan.io/address/0xa9Fd765d85938D278cb0b108DbE4BF7186831186) | +| NonfungibleTokenPositionDescriptor | [0x644023b316bB65175C347DE903B60a756F6dd554](https://celoscan.io/address/0x644023b316bB65175C347DE903B60a756F6dd554) | +| TransparentUpgradeableProxy | [0x505B43c452AA4443e0a6B84bb37771494633Fde9](https://celoscan.io/address/0x505B43c452AA4443e0a6B84bb37771494633Fde9) | +| NonfungiblePositionManager | [0x3d79EdAaBC0EaB6F08ED885C05Fc0B014290D95A](https://celoscan.io/address/0x3d79EdAaBC0EaB6F08ED885C05Fc0B014290D95A) | +| V3Migrator | [0x3cFd4d48EDfDCC53D3f173F596f621064614C582](https://celoscan.io/address/0x3cFd4d48EDfDCC53D3f173F596f621064614C582) | +| QuoterV2 | [0x82825d0554fA07f7FC52Ab63c961F330fdEFa8E8](https://celoscan.io/address/0x82825d0554fA07f7FC52Ab63c961F330fdEFa8E8) | +| SwapRouter02 | [0x5615CDAb10dc425a742d643d949a7F474C01abc4](https://celoscan.io/address/0x5615CDAb10dc425a742d643d949a7F474C01abc4) | +| Permit2 | [0x000000000022D473030F116dDEE9F6B43aC78BA3](https://celoscan.io/address/0x000000000022D473030F116dDEE9F6B43aC78BA3) | +| UniversalRouter | [0x643770E279d5D0733F21d6DC03A8efbABf3255B4](https://celoscan.io/address/0x643770E279d5D0733F21d6DC03A8efbABf3255B4) | +| v3StakerAddress | [0x6586FB35393abF7Ff454977a9b3c912d218791C6](https://celoscan.io/address/0x6586FB35393abF7Ff454977a9b3c912d218791C6) | diff --git a/build/tools/libraries-sdks/contractkit/odis.mdx b/build/tools/libraries-sdks/contractkit/odis.mdx index dec573e6a4..3bde3d8b00 100644 --- a/build/tools/libraries-sdks/contractkit/odis.mdx +++ b/build/tools/libraries-sdks/contractkit/odis.mdx @@ -60,19 +60,32 @@ const serviceContext: ServiceContext = { The ODIS endpoint URL for each environment can be found here: -| Environment | Key | -| ----------------- | -------------------------------------------------------------------- | -| Alfajores Staging | https://us-central1-celo-phone-number-privacy-stg.cloudfunctions.net | -| Alfajores | https://us-central1-celo-phone-number-privacy.cloudfunctions.net | -| Mainnet | https://us-central1-celo-pgpnp-mainnet.cloudfunctions.net | +| Environment | URL | +| ------------ | ---------------------------------------------------------------- | +| Mainnet | https://odis-combiner-mainnet.rc1-europe-west1.celo-testnet.org | +| Celo Sepolia | https://odis-combiner.celo-sepolia.celo-testnet.org | The ODIS public key for each environment can be found here: -| Environment | Key | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| Alfajores Staging | 7FsWGsFnmVvRfMDpzz95Np76wf/1sPaK0Og9yiB+P8QbjiC8FV67NBans9hzZEkBaQMhiapzgMR6CkZIZPvgwQboAxl65JWRZecGe5V3XO4sdKeNemdAZ2TzQuWkuZoA | -| Alfajores | kPoRxWdEdZ/Nd3uQnp3FJFs54zuiS+ksqvOm9x8vY6KHPG8jrfqysvIRU0wtqYsBKA7SoAsICMBv8C/Fb2ZpDOqhSqvr/sZbZoHmQfvbqrzbtDIPvUIrHgRS0ydJCMsA | -| Mainnet | FvreHfLmhBjwxHxsxeyrcOLtSonC9j7K3WrS4QapYsQH6LdaDTaNGmnlQMfFY04Bp/K4wAvqQwO9/bqPVCKf8Ze8OZo8Frmog4JY4xAiwrsqOXxug11+htjEe1pj4uMA | +| Environment | Key | +| ------------ | -------------------------------------------------------------------------------------------------------------------------------- | +| Mainnet | FvreHfLmhBjwxHxsxeyrcOLtSonC9j7K3WrS4QapYsQH6LdaDTaNGmnlQMfFY04Bp/K4wAvqQwO9/bqPVCKf8Ze8OZo8Frmog4JY4xAiwrsqOXxug11+htjEe1pj4uMA | +| Celo Sepolia | kPoRxWdEdZ/Nd3uQnp3FJFs54zuiS+ksqvOm9x8vY6KHPG8jrfqysvIRU0wtqYsBKA7SoAsICMBv8C/Fb2ZpDOqhSqvr/sZbZoHmQfvbqrzbtDIPvUIrHgRS0ydJCMsA | + +`@celo/identity` 6.0.0-beta.0 and later ship both as ready-made contexts. The beta needs `viem` installed alongside it: + +```bash +npm install @celo/identity@6.0.0-beta.0 viem +``` + +```ts +import { OdisUtils } from "@celo/identity"; + +const { getServiceContext, OdisContextName } = OdisUtils.Query; +const serviceContext = getServiceContext(OdisContextName.CELO_SEPOLIA); // or OdisContextName.MAINNET +``` + +Version 5.1.2 has no Celo Sepolia context, so build the `ServiceContext` from the values above. ## Query phone number identifier diff --git a/build/tools/libraries-sdks/contractkit/setup.mdx b/build/tools/libraries-sdks/contractkit/setup.mdx index 5d5262030e..969242a869 100644 --- a/build/tools/libraries-sdks/contractkit/setup.mdx +++ b/build/tools/libraries-sdks/contractkit/setup.mdx @@ -48,7 +48,7 @@ You will need Node.js v18.x. ## Initializing the Kit -To start working with ContractKit you need a `kit` instance and a valid net to connect with. In this example will use `alfajores` (you can read more about it [here](/learn/network/overview)) +To start working with ContractKit you need a `kit` instance and a valid net to connect with. In this example will use Celo Sepolia (you can read more about it [here](/learn/network/overview)) ```ts import Web3 from "web3"; diff --git a/build/tools/libraries-sdks/portal/index.mdx b/build/tools/libraries-sdks/portal/index.mdx index 3db5228e2b..a78c3186c9 100644 --- a/build/tools/libraries-sdks/portal/index.mdx +++ b/build/tools/libraries-sdks/portal/index.mdx @@ -169,7 +169,7 @@ const portal = new Portal({ gatewayConfig: { ["eip155:1"]: "https://api.portalhq.io/rpc/v1/eip155/1", ["eip155:42220"]: "https://api.portalhq.io/rpc/v1/eip155/42220", // Celo Mainnet - ["eip155:44787"]: "https://api.portalhq.io/rpc/v1/eip155/44787", // Celo Alfajores + ["eip155:11142220"]: "https://api.portalhq.io/rpc/v1/eip155/11142220", // Celo Sepolia }, }); ``` @@ -177,6 +177,10 @@ const portal = new Portal({ + +Portal's [chain list](https://docs.portalhq.io/resources/blockchain-support) does not yet name Celo Sepolia (`eip155:11142220`). Confirm support with Portal before relying on the Celo Sepolia examples on this page. + + ### Creating an MPC Wallet To create a new MPC wallet, use the `portal.createWallet()` function. This will generate distributed MPC key shares, storing the user's signing share in the device's secure keychain. @@ -228,7 +232,7 @@ After creating a wallet, you can fund it with test tokens using `portal.receiveT ```javascript -const chainId = "eip155:44787"; // Celo Alfajores +const chainId = "eip155:11142220"; // Celo Sepolia const params = { amount: "0.01", // You will receive 0.01 CELO token: "NATIVE", // Token, use "NATIVE" for the chain's native token @@ -242,7 +246,7 @@ console.log(`✅ Transaction hash: ${response.data.txHash}`); ```swift -let chainId = "eip155:44787" // Celo Alfajores +let chainId = "eip155:11142220" // Celo Sepolia let params = FundParams( amount: "0.01", // You will receive 0.01 CELO token: "NATIVE" // Token, use "NATIVE" for the chain's native token @@ -256,7 +260,7 @@ print("✅ Transaction hash: \(response.data.txHash)") ```kotlin -val chainId = "eip155:44787" // Celo Alfajores +val chainId = "eip155:11142220" // Celo Sepolia val params = FundParams( amount = "0.01", // You will receive 0.01 CELO token = "NATIVE" // Token, use "NATIVE" for the chain's native token @@ -270,7 +274,7 @@ println("✅ Transaction hash: ${response.data.txHash}") ```javascript -const chainId = "eip155:44787"; // Celo Alfajores +const chainId = "eip155:11142220"; // Celo Sepolia const params = { amount: "0.01", // You will receive 0.01 CELO token: "NATIVE", // Token, use "NATIVE" for the chain's native token diff --git a/contribute-to-celo/release-process/attestation-service.mdx b/contribute-to-celo/release-process/attestation-service.mdx deleted file mode 100644 index 518c9eb768..0000000000 --- a/contribute-to-celo/release-process/attestation-service.mdx +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: "Attestation Service Release Process" -sidebarTitle: "Attestation Service" -description: Details of the release process for updating the attestation service on the Celo platform. ---- - - -As of block height 31,056,500 (March 26, 2025, 3:00 AM UTC), Celo is no longer a standalone Layer 1 blockchain—it is now an Ethereum Layer 2! -Some documentation may be outdated as updates are in progress. If you encounter issues, please [file a bug report](https://github.com/celo-org/docs/issues/new/choose). - -For the most up-to-date information, refer to our [Celo L2 documentation](/build#celo-l2-mainnet). - - ---- - - -This release process is currently in use. - - -## Versioning - -Releases of Attestation Service are made as needed. Releases are numbered according to semantic versioning, as described at [semver.org](https://semver.org). - -Development builds should be identified with `-dev`, and only one commit should exist with a released version `x.y.z` for any `(x, y, z)`. - -## Documentation - -Documentation is maintained in the [celo-org/docs](https://github.com/celo-org/docs) repo and is hosted on [docs.celo.org](/). - -## Identifying releases - -### Git branches - -Development is done on the `master` branch, which corresponds to the next major or minor version. Changes to be included in a patch release of an existing minor version are cherry-picked to that existing release branch. - -### Git tags - -Each release should be [created on Github](https://github.com/celo-org/celo-monorepo/releases) and tagged with the version number, e.g. `attestation-service-vX.Y.Z`. Each release should include a summary of the release contents, including links to pull requests and issues with detailed description of any notable changes. - -Tags should be signed and can be verified with the following command. - -```bash -git verify-tag attestation-service-vX.Y.Z -``` - -On Github, each release tag should have attached signatures that can be used to verify the Docker images. - -### Docker tags - -Each Docker image is tagged with `attestation-service-`. Just as a Git tag immutably points to a commit hash, the Docker tag should immutably point to an image hash. - -In addition, each Docker image corresponding to a released version should be tagged with `attestation-service-vX.Y.Z`. - -The latest image qualified for deployment to various networks are also tagged as follows: - -- Alfajores: `attestation-service-alfajores` -- Baklava: `attestation-service-baklava` -- Mainnet: `attestation-service-mainnet` - -### Signatures - -Artifacts produced by this build process (e.g. tags, Docker images) will be signed by a [core developer key](https://github.com/celo-org/celo-monorepo/blob/master/developer_key_publishing.md). - -Public keys for core developers are hosted on celo.org and can be imported to `gpg` with the following command: - -```bash -gpg --auto-key-locate wkd --locate-keys $EMAIL -``` - -Currently hosted core developer keys used for Attestation Service releases include: - -- tim@clabs.co - -## Build process - -### Docker images - -Docker images are built automatically with [Google Cloud Build](https://cloud.google.com/build) upon pushes to `master` and all release branches. Automated builds will be tagged in [Google Artifact Registry](https://cloud.google.com/artifact-registry) with the corresponding commit hash. - -A signature should be produced over the image automatically built at the corresponding commit hash and included with the Github release. - -Release image signatures can be verified with the following command: - -```bash -docker save $(docker image inspect us.gcr.io/celo-testnet/celo-monorepo:attestation-service-vX.Y.Z -f '{{ .Id }}') | gpg --verify attestation-service-vX.Y.Z.docker.asc - -``` - -## Testing - -As well as monorepo CI tests, all releases are expected to go through manual testing as needed to verify security properties, accuracy of documentation, and compatibility with deployed and anticipated versions of `celocli` and wallets including Valora. Releases currently involve coordinating with Valora to run the verification e2e tests in CI. - -## Promotion process - -### Source control - -Patch releases should be constructed by cherry-picking all included commits from `master` to the `release/attestation-service/x.y` branch, if necessary created from the `attestation-service-vX.Y.Z` tag of the most recent major or minor release. The first commit of this process should change the version number encoded in the source from `x.y.z` to `x.y.z+1-dev` and the final commit should change the version number to `x.y.z+1`. - -Major and minor releases should be constructed by pushing a commit to the `master` branch to change the encoded version number from `x.y.z-dev` to `x.y.z`. A `attestation-service-vX.Y.Z` tag should be created at this commit which uniquely references one commit; release notes should be published alongside this. The next commit should change the version number from `x.y.z` to `x.y+1.0-dev`, or `x+1.0.0-dev` if the next planned release is a major release. - -### Distribution - -Distribution of an image follows this schedule: - - - - - - - - - - - - - - - - - - -
DateAction
T-1w -
    -
  1. Deploy release candidate build to Alfajores testnet
    2. -
  2. Test manually and via e2e verification tests
    3. -
-
T -
    -
  1. Confirm Valora production and testing builds against Alfajores experience no issues and that e2e verification tests complete successfully
    2. -
  2. Publish the release notes and tag the relevant commit on GitHub
    3. -
  3. Tag released Docker image with attestation-service-alfajores, attestation-service-baklava, attestation-service-mainnet, and attestation-service-vX.Y.Z tags (removing tags from other releases)
    4. -
  4. Inform the community of the new release via Discord and the Celo Forum
    5. -
-
T+1w onwards -
    -
  1. Confirm Mainnet services have upgraded without issues
    2. -
  2. Continue monitoring dashboards for user issues
    3. -
-
- -### Emergency Patches - -Bugs which affect the security, stability, or core functionality of the Celo identity protocol or prevent new users onboarding to wallets including Valora may need to be released outside the standard release cycle. In this case, an emergency patch release should be created on top of all supported minor releases which contains the minimal change and corresponding test for the fix. - -If the issue is not exploitable, release notes should describe the issue in detail and the image should be distributed publicly. - -If the issue is exploitable and mitigations are not readily available, a patch should be prepared privately and signed binaries should be distributed from private commits. Establishing trust is key to pushing out the fix. An audit from a reputable third party may be contracted to verify the release to help earn that trust. - -## Vulnerability Disclosure - -Vulnerabilities in Attestation Service releases should be disclosed according to the [security policy](https://github.com/celo-org/celo-blockchain/blob/master/SECURITY.md). \ No newline at end of file diff --git a/contribute-to-celo/release-process/index.mdx b/contribute-to-celo/release-process/index.mdx index 675a698329..387b8ae697 100644 --- a/contribute-to-celo/release-process/index.mdx +++ b/contribute-to-celo/release-process/index.mdx @@ -10,5 +10,4 @@ It is critical that updates to the Celo platform can be released on a regular ba - [Smart Contracts](/contribute-to-celo/release-process/smart-contracts) - [Blockchain Client](/contribute-to-celo/release-process/blockchain-client) -- [CeloCLI and ContractKit](/contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils) -- [Attestation Service](/contribute-to-celo/release-process/attestation-service) \ No newline at end of file +- [CeloCLI and ContractKit](/contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils) \ No newline at end of file diff --git a/docs.json b/docs.json index 9e2246afea..70f1c6fc1b 100644 --- a/docs.json +++ b/docs.json @@ -437,8 +437,7 @@ "contribute-to-celo/release-process/index", "contribute-to-celo/release-process/smart-contracts", "contribute-to-celo/release-process/blockchain-client", - "contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils", - "contribute-to-celo/release-process/attestation-service" + "contribute-to-celo/release-process/base-cli-contractkit-dappkit-utils" ] } ] @@ -1027,6 +1026,10 @@ "source": "/home/roadmap", "destination": "/learn" }, + { + "source": "/contribute-to-celo/release-process/attestation-service", + "destination": "/contribute-to-celo/release-process" + }, { "source": "/build/build-with-thirdweb/overview", "destination": "/build/tools/dev-environments/thirdweb" @@ -1941,7 +1944,7 @@ }, { "source": "/community/release-process/attestation-service", - "destination": "/contribute-to-celo/release-process/attestation-service" + "destination": "/contribute-to-celo/release-process" }, { "source": "/community/release-process/base-cli-contractkit-dappkit-utils", @@ -3049,7 +3052,7 @@ }, { "source": "/what-is-celo/joining-celo/contributors/release-process/attestation-service", - "destination": "/contribute-to-celo/release-process/attestation-service" + "destination": "/contribute-to-celo/release-process" }, { "source": "/what-is-celo/joining-celo/contributors/release-process/blockchain-client", diff --git a/learn/protocol/transactions/transaction-types.mdx b/learn/protocol/transactions/transaction-types.mdx index 23785def4e..a4f5272d9c 100644 --- a/learn/protocol/transactions/transaction-types.mdx +++ b/learn/protocol/transactions/transaction-types.mdx @@ -306,7 +306,7 @@ import { parseGwei, } from "viem"; import { privateKeyToAccount } from "viem/accounts"; -import { celoAlfajores } from "viem/chains"; +import { celoSepolia } from "viem/chains"; import "dotenv/config"; // use to read private key from environment variable ``` @@ -328,11 +328,11 @@ const PRIVATE_KEY = process.env.PRIVATE_KEY; */ const account = privateKeyToAccount(`0x${PRIVATE_KEY}`); const publicClient = createPublicClient({ - chain: celoAlfajores, + chain: celoSepolia, transport: http(), }); const walletClient = createWalletClient({ - chain: celoAlfajores, // Celo testnet + chain: celoSepolia, // Celo Sepolia testnet transport: http(), }); ```