VERIFY screen #14

Closed
opened 2024-05-08 14:33:28 +00:00 by b · 1 comment
Owner

The home screen should have two options - SIGN or VERIFY

The VERIFY screen should accept either a URL or allow the user to upload a SIGIT file. What happens next is the same as if the user arrives via URL (eg from a SIGIT DM)

If the SIGIT file cannot be verified, we can provide helpful information about what went wrong

If the SIGIT file contains a fully signed package, we display the package information

If the SIGIT file is not fully signed, and the user is the next signee, we move to the SIGN screen

If the SIGIT file is not fully signed and the logged in user is NOT the next signee, display the package information plus "Awaiting signature by $npub" (in the VERIFY screen)

The home screen should have two options - SIGN or VERIFY The VERIFY screen should accept either a URL or allow the user to upload a SIGIT file. What happens next is the same as if the user arrives via URL (eg from a SIGIT DM) If the SIGIT file cannot be verified, we can provide helpful information about what went wrong If the SIGIT file contains a fully signed package, we display the package information If the SIGIT file is not fully signed, and the user is the next signee, we move to the SIGN screen If the SIGIT file is not fully signed and the logged in user is NOT the next signee, display the package information plus "Awaiting signature by $npub" (in the VERIFY screen)
s self-assigned this 2024-05-13 12:08:21 +00:00
Owner

closed by #20

closed by #20
s closed this issue 2024-05-14 10:11:15 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sigit/sigit.io#14
No description provided.