celo-monorepo

This is a feature release bringing a number of changes. It is recommended that all validators deploy this version on baklava then upgrade on mainnet.

Documentation

Full documentation is here.

Upgrading

Validator operators are advised to test first on Baklava before deploying changes on Mainnet.

Deploy the Docker image identified as follows:

• us.gcr.io/celo-testnet/celo-monorepo:attestation-service-1-0-4
• us.gcr.io/celo-testnet/celo-monorepo@sha256: d315dc8ec4981bdf60c34f296623f101b77ed0fc0ca28e2b7fe1884ad8d59097

Existing configurations should work as is. New configuration options are described in the documentation.

Changes

• This release supports Nexmo applications so that multiple validators can share a single Nexmo billing account but use different callback URLs.

This release contains minor bug fixes.

Documentation

Full documentation is here.

Upgrading

All validators are advised to test first on Baklava before deploying changes on Mainnet.

Deploy the Docker image identified as follows:

• us.gcr.io/celo-testnet/celo-monorepo:attestation-service-1-0-3
• us.gcr.io/celo-testnet/celo-monorepo@sha256:bbeaae0a728801e24abbaa6e15903ad120ce529e676b82d6a816cb3d4ba622d8

Existing configurations should work as is.

Changes

• Allow Twilio delivery receipts to be received by Attestation Service instances running behind proxies that rewrite protocol or host (e.g. CloudFlare)
• Fix an issue responding to certain failed health checks under /healthz

This release contains a number of changes to Attestation Service to better support multiple providers, add delivery receipts, and provide insight into failures.

Documentation

Full documentation is here.

Upgrading

All validators are advised to test first on Baklava before deploying changes on Mainnet.

Deploy the Docker image identified as follows:

• us.gcr.io/celo-testnet/celo-monorepo:attestation-service-1-0-2
• us.gcr.io/celo-testnet/celo-monorepo@sha256:d58b43eb16d287a574a2d16a10a929777de1bade6a2f51a6be3f897d66dc7519

New configuration options are described in the documentation. Existing configs should work as is, but validators are advised to set up a Nexmo account and test delivery receipts.

Changes

• Interface for providers to support delivery receipts, and support added to receive them for Twilio and Nexmo
• Better support for using multiple providers
• Provider configs can be specified per country code like SMS_PROVIDERS_US=twilio,nexmo
• SMS send retry logic made generic for all providers:
  ** use country specific provider order, then filtered by unsupported regions
  ** retry send for each provider with backoff (then moving on to next provider)
  ** if a delivery report comes back with a failure, that causes a retry to happen
• Renamed BLACKLIST config options params to UNSUPPORTED_REGIONS though existing configs are backwards compatible and will work unchanged
• If VERIFY_CONFIG_ON_STARTUP option set, service startup now verifies account and signer key match, that metadata is available, and that attestation claim is made, to reduce chance of misconfiguration
• Off-by-default NEXMO_ACCOUNT_BALANCE_METRIC option to expose Nexmo balance as a metric so it can be alerted on to prevent validators running out of funds
• New metrics:
  ** Counts by provider, country code, and delivery status: attestation_attempts_delivery_status
  ** Counts by provider, country code, and error code: attestation_attempts_delivery_error_codes
  ** Eventual delivery success (or timeout without a delivery report): attestation_requests_believed_delivered_sms
  ** Eventual delivery report of failure: attestation_requests_failed_to_deliver_sms
  ** attestation_requests_unable_to_serve now broken down by country code
• Health check now detects a full node not syncing but running behind

This is a patch to Valora 1.0.0(15) that includes a single change to better handle zero-balance users who attempt to verify.

Security

While no dependencies have changed in this patch, to formally follow the release process, I have audited yarn dependencies to confirm no high severity issues. I have not rerun static analysis with MobSF on production iOS and Android builds, these results are unchanged and in the original release were reviewed with security team to confirm no blocking issues

Testing

The feature affected by this patch was tested by @jeanregisser confirming expected behavior for these cases. Additionally:

• End-to-end iOS and Android tests run locally
• Sanity testing on Pixel 2
• Ongoing smoke testing with Ankit and his Lodestone QA team
• Ongoing internal testing
  For more details on the ongoing testing that will be confirmed before promotion to public release, see the Wallet Release Process.

Commits included

• Adding odis balance check (improved UX for zero-balance verification) https://github.com/celo-org/celo-monorepo/pull/4729
• Updating build number to 1.0.1

Version scheme

Note that while we wanted to have the first public release version use 1.0.0, in order to keep the existing 1.0.0(15) in the App Store approved and ready for release while this version processes, we had to use a different version number so we used the normal version scheme for a patch, bumping to 1.0.1.

This release represents the first public release of Valora

Security

• Audited yarn dependencies to confirm no high severity issues
• Ran static analysis with MobSF on production iOS and Android builds, reviewed results with security team to confirm no blocking issues

Testing

• End-to-end iOS and Android tests run locally
• Sanity testing on Pixel 2 and iPhone Xs
• Ongoing smoke testing with Ankit and his Lodestone QA team
• Ongoing internal testing

For more details on the ongoing testing that will be confirmed before promotion to public release, see the Wallet Release Process.

Commits included

This build was cut from master on August 18, and includes cherry-picked fixes for:

• Withdraw CELO QR scan fixes (bug fix) https://github.com/celo-org/celo-monorepo/pull/4740
• Add ‘Confirm Phone Number’ option to settings https://github.com/celo-org/celo-monorepo/pull/4744
• Make invitation links use vlra.app domain https://github.com/celo-org/celo-monorepo/pull/4733
• Salt was renamed to pepper (bug fix) https://github.com/celo-org/celo-monorepo/pull/4756
• Add back trigger for enabling dev mode in setting menu (regression fix) https://github.com/celo-org/celo-monorepo/pull/4760
• Fix ODIS url in mainnet bug from rename (bug fix) https://github.com/celo-org/celo-monorepo/pull/4772
• Show correct app icon on older Android devices (bug fix) https://github.com/celo-org/celo-monorepo/pull/4774

Due to an issue only occurring in production iOS releases (https://github.com/celo-org/celo-monorepo/issues/4781), https://github.com/celo-org/celo-monorepo/pull/4723 was reverted to downgrade @celo/client 0.0.315 back to the stable 0.0.309, but celo branding changes and an transfer end-to-end test fix in this PR were kept. Note that these test related changes (https://github.com/celo-org/celo-monorepo/commit/9a17cf2fc135e48500892bcd8c8cde39a7b49f14 , https://github.com/celo-org/celo-monorepo/commit/9f6e19e7a17eb9d897b4d51a06907f1de1afabd9, https://github.com/celo-org/celo-monorepo/commit/adfd67d5200555cd3464591d6a0523394289ee3d) have no effect on the build.

Features included

Relative to the last internal release, this update adds CELO transfers, logout, and a new vlra.app domain for invitation links. Other improvements include performance tracking metrics for Android and bug fixes for accounts with no balance.

Version code

Moving forward, we will use a normal version scheme, ie 1.0.1 for a patch. We chose to use the scheme 1.0.0(15) so that our first public release could be 1.0.0 🥇

This update includes new features like CELO transfers, logout, and a new vlra.app domain for invitation links. Other improvements include performance tracking metrics for Android and bug fixes for accounts with no balance.

Hello world!

The initial core smart contract release for the Celo Mainnet network

Update to the combiner and signer. The combiner update will be going out now, and the signer update will be bundled with future changes.

• Strengthen combiner/signer interface
• Identify discrepancies between signers' DBs/full-nodes state
• Add retry to blockchain queries

Release for the Alfajores network reset on April 9th, 2020
Includes the Android and iOS Wallet release v1.7.0

Release for the Alfajores network reset on February 4th, 2020
Includes the Android and iOS Wallet release v1.6.0

Release for the Alfajores network reset and redeployment on October 3.
Includes the Android Wallet release v.1.5.0

• New designs for the home screen, tab bar, and some onboarding screens
• Info about Celo dollars equivalent in local currencies
• Faster fee calculation and improved send flow UX
• Backup keys are now always accessible and kept in secure storage
• Fixes for payment requests, i18n, deep linking, escrow payments and more

• Update to the Alfajores Testnet
• Includes Celo-blockchain at f7095b78003062db9536e1d070772d20a3f81e93
  ** BLS signatures for consensus and block headers
  ** Recovery of block randomness
  ** Encrypted validator announce messages

Mainly bug fixes relating to the Send and Onboarding flows.

• 20+ bug fixes across the onboarding and payment flows!
• Compatibility with the new BLS signature based network
• More robust invite code redemption and verification
• New mechanism for fee calculation to improve reliability and organization
• Automatic account balance updating and related bug fixes
• Improved handling of recent recipients
• Smoother UX for alerts and notifications

Released on 2019-07-24