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.

Sign up for GitHub

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

Jump to bottom

Finalize rVASP Implementation #27

Closed

3 of 5 tasks

bbengfort opened this issue Feb 1, 2021 · 0 comments · Fixed by #37

Closed

3 of 5 tasks

Finalize rVASP Implementation #27

bbengfort opened this issue Feb 1, 2021 · 0 comments · Fixed by #37

Collaborator

bbengfort commented Feb 1, 2021 •

edited

Loading

Questions:

Should we deploy a single PostgreSQL database into the TestNet for the rVASPs? (Currently, they all use a local SQLite3 database)

Still TODO:

Add service stubs for signing key exchange and address confirmation
Create manifests for alice, bob, and evil rVASP
Specify database initialization for alice, bob, and evil rVASPs in the TestNet
On transaction request, rVASP engages the TRISA protocol
Opt-in to transaction ID for log messages #1 and Add beneficiary VASP ID and originating VASP ID to transaction request #2 for the demo service

bbengfort mentioned this issue

Finalize rVASP Implementation #37

Merged

bbengfort closed this as completed in #37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment