Everyone SBAT know the plan for deploying attestation services to Alfajores/Betanet

[nambrot]

Expected Behavior

There should be a plan that everyone can reference that minimizes the impact on the user experience of both mobile users and validators.

Current Behavior

There is no plan anyone can reference

[nambrot]

Roadmap for imminent changes to Identity, especially as it relates to the wallet:

Already finished protocol work:

• Creation of the attestation service Validators SBAT run an attestation service #1039
• Helm chart for Clabs to deploy attestation service for clabs validators Validators SBAT reference hosting tooling for the attestation service #1076
• Metadata registration + contractkit work to register and access attestation service url Users SBAT handle identity metadata #1104

Protocol work necessary before mobile can start work (this sprint):

• Make randomness historically available Developers SBAT have access to randomness of prior blocks #1181
• Addition of the revealIssuers tx to accomodate https://github.com/celo-org/celo-labs/issues/80

Mobile work necessary to move to attestation service (requirement for Betanet?):

• Have wallet implement the above changes (remove reveal tx, add revealIssuers tx) Wallet Users SBAT to reveal to an attestation service #1040
• For a smooth transition on Alfajores (assuming we will need it), we can temporarily support revealing both via the old reveal tx (and thus use the central verification pool), and directly to the attestation service to protect against validators not being "compliant" on Alfajores.

Rollout plan (Alfajores):

• We update documentation to indicate to validators that at the next Alfajores deploy they are expected to run the attestation service (however we still keep the old reveal functionality in for validators who miss it) as well as register the attestation service URL in their metadata that they have to host.
• Once mobile work has finished, we'll do the deploy to alfajoresstaging for testing.
• Reset Alfajores (@timmoreton ?)
• Have the mobile app run with both modes of revealing and observe if validators are "compliant".

Rollout plan (Betanet):

• We update documentation to indicate to validators that they are expected to run the attestation service as well as register the attestation service URL in their metadata that they have to host.

Further work:

• Raise the attestation fee to $0.07 (since it can cost more than $0.05 to send) + derivative changes for the wallet
• Eventually remove ABE code from celo-blockchain

[nambrot]

As talked about in today's sprint meeting, we will no longer have the grace period in which we reveal both ways. Instead the mobile app will detect, similarly to right now, if a validator does not seem to have the right setup for attestation and request additional attestations which hopefully yield validators that will actually run the attestation service. We do so to be able to merge this with the hashing changes

[nambrot]

Also this board https://github.com/orgs/celo-org/projects/113

[nambrot]

Alfajores re-deploy is tentatively scheduled for 10/23, so we aim to get all the relevant changes in then