-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Wallet] Report to analytics reveal statuses from validators #5315
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I would say we want status
, attempt
, provider
, duration
(if present), errors
(if present).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good. i would say we'd want all the data you specified in the PR overview.
i'm going to sync with tim to understand the schema for multiple attempts and whether it makes sense to parse at the level of throwing the event here or to keep in the "status" field.
i'll get back to you on it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Just curious, are there plans to deprecate the proxy entirely? It was only meant to be used while validators got their attestation services set up properly with TLS.
try { | ||
const urlParams = new URLSearchParams({ | ||
phoneNumber, | ||
salt: pepper ?? '', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of scope here but just a nit, would be nice to have salt renamed in attestation service too: https://github.com/celo-org/celo-monorepo/blob/master/packages/utils/src/io.ts#L109
Since there's been changes there anyway seems like there's an opportunity to do that (in a backwards compat way) before the next release. cc @aslawson @timmoreton
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we've already published the attestation service, so unfortunately can't do it this iteration :/
@jmrossy yup, we are currently in the process of urging validators to enable TLS now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
@jmrossy I've addressed the feedback, PTAL. |
@jeanregisser can you please provide more details if we need to verify this task. |
No need to verify @Lss-Ankit thanks! |
Thanks @jeanregisser for the update. |
Description
Implementing a second part of https://github.com/celo-org/celo-labs/issues/574. The logic is the following:
proxyRevealStatus
.TODO
yarn deploy
needs to be run inpackages/attestation-proxy
to deploy firebase function.Other changes
features. USE_PHONE_NUMBER_PRIVACY
Tested
proxyRevealStatus
andproxyReveal
tocelo-mobile-alfajores
and tested forcing using proxy in the codebase on alfajores.Related issues
Backwards compatibility
Yes