Skip to content

[RFC0000_2] User Registration on Web - UI Flow - Phase 2 #15

@ProfilaMitchell

Description

@ProfilaMitchell

Table of Contents

Housekeeping

RFC0000

Named Concepts

Explain any new concepts introduced in this request.

Summary

Integrating ATALAPrism SDK into Profila. End user should have his own DID and Profila should be custodian.

Reference-Level Explanation

Proposed changes will strongly influence backend, but will not affect frontend.
Backend side will be expanded with Web3.0 flow :

  • setup and secure multiuser wallet ( storing DIDs of users )
  • create API to use it from backend
  • update flow of registration -> registering user (consumer or brand) will cause to create P-DID or B-DID

Alternatives

Rationale

Drawbacks

Useful References

Unresolved Questions

Parts of the System Affected

Backend

Future possibilities

Infrastructure

  • Hosting multiuser wallet which holds DID

Testing

Documentation

Version History

Recordings

Work Phases

Non-Coding

  • Finalize scope - what responsibility AtalaPRISM has and what should be done in-house
  • Research AtalaPRISM SDK and other tooling from IO
  • Make consensus with IO about API

Implementation

  • Write automatic tests proving AtalaPRISM solution works
  • Setup infrastructure AtalaPRISM solution
  • Integrate AtalaPRISM solution with backend

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions