build(deps): bump @celo/utils from 1.5.2 to 3.1.0

[dependabot]

Bumps @celo/utils from 1.5.2 to 3.1.0.

Release notes

Sourced from @​celo/utils's releases.

ContractKit SDKS 3.1

New Feature

• Adds ability to verify governance proposals which interact with non core contracts using sourcify #10019

Packages with changes

• @​celo/explorer
• @​celo/governance

@​celo/celocli 1.7.4

Fixes

• Removes incorrect account check on payment delegations enabling any address to be delegated to including celo safe vaults
• Adds governance version check to governance approval method

ContractKit SDKs v3.0.1

New Features

Add support for arbitrary off-chain identifiers in the @​celo-org/identity sdk. Previously, the sdk was written to be phone number specific and identifiers were prefixed with tel:// after returning from ODIS. This update adds new prefixes for twitter + email and refactors the code to be identifier agnostic.

celo-org/celo-monorepo#9985

ODIS 2.0.0

@​oblivious-decentralized-identifier-service-2.0.0

ODIS 2.0.0 is a complete refactor of ODIS that adds support for

• The CIP40 API and PEAR Account Recovery protocol.
• Improved rate limiting via OdisPayments.sol to support the Federated Attestations Identity protocol (CIP51)
• Multiple key versions, to enable future key rotations and enhanced security

ODIS signers should upgrade to us.gcr.io/celo-testnet/celo-monorepo:oblivious-decentralized-identifier-service-2.0.0

Before upgrading

1. Please ensure that your key shares are named correctly in your keyvault prior to upgrading your signer.

• If you are using Azure or AWS , the original bls share should be named phoneNumberPrivacy-1 and the more recent version of that key share (generated during the resharing ceremony on 10/22/21) should be labeled phoneNumberPrivacy-2. The CIP40 key share generated during the DKG ceremony on 10/22/21 should be named domains-1.
• If you are using Google Cloud, you should create two keys named phoneNumberPrivacy (with versions 1 and 2) and domains (with only version 1). The KEYSTORE_GOOGLE_SECRET_NAME env variable isn't used anymore.
• Please do not delete or rename any existing shares, but rather add the shares to your vault as duplicates under these new names. If you are unsure for any reason about how to label your key shares please reach out on Discord. If you would like to setup time to go through the update synchronously, don't hesitate to reach out.

3. Please ensure that you have set the following environment variables to true in order to enable all APIs (See Signer README for more info) LEGACY_PHONE_NUMBER_PRIVACY_API_ENABLED PHONE_NUMBER_PRIVACY_API_ENABLED DOMAINS_API_ENABLED

NOTE / UPDATE : This upgrade is currently incompatible with MySQL. If you're using MySQL for your signer DB, please let us know and hold off on upgrading.

NOTE: You will not be able to roll back the upgrade because the database will be updated in a non-backwards compatible way. If your signer is having trouble starting up, it is almost certainly an issue with how your keys are labeled. Please double check your key configuration prior to upgrading, and if an issue does occur there's no need to worry. The system is able to handle limited downtime from 1 or 2 signers at a time and we will be readily available on discord to help troubleshoot.

After upgrading

1. Please checkout celo-monorepo on master, run yarn && yarn build from the root directory (might take 10-15 mins), and follow the Validating before going live instructions in the Signer README to test that your service is configured properly. If you encounter difficulties or would like further guidance, don't hesitate to reach out on Discord.
2. Please post in the Discord channel once your upgraded service is live and passing the configuration tests.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by aaron-clabs, a new releaser for @​celo/utils since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
ubeswap-interface	✅ Ready (Inspect)	Visit Preview	Jan 11, 2023 at 6:08PM (UTC)

[dependabot]

Superseded by #664.