issue-166-open-timestamps #220
No reviewers
enes
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sigit/sigit.io#220
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "issue-166-open-timestamps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the full Open Timestamps Flow
On create, a new (incomplete) timestamp is created for the nostrId of the original CreateSignatureEvent. It is stored in the timestamps array on the Meta object. No further signature is added to the timestamp.
On signing, a new (incomplete) timestamp is created for the nostrId of the DocSignature event and is stored in the same timestamps array on Meta.No further signatures or checks are performed.
When the user go to the verify page, Sigit will try to upgrade the available timestamps. If no upgrade is currently available (i.e., the timestamp has not been posted on the Bitcoin blockchain yet), nothing happens.
If an upgrade is available, the timestamp will be available and a nostr event will 'sign' the timestamp completion. The nostr signature will be added to the timestamp object.
Then, the user will need to sign another event, updating app data and sending notifications to other users.
Note that if more than one timestamp can be updated at the same time, it will be done with just one nostr event, and the finished timestamp will contain the same signature.
The final timestamp should include the timestamp itself with several Bitcoin attestations, the nostr event that signed its completion, and a nostrId - which is related to the nostr event action that the timestamp verified (i.e. create or sign).
Looks good, just two nitpicky html/css comments. It would be nice to match the padding and make it work without extra span wrapper.
@ -54,0 +69,4 @@nostrId: string) => {if (isTimestampVerified(timestamps, nostrId)) {return <FontAwesomeIcon icon={faCheck} />Can we make add the
className={styles.ticket}>to the icon directly here instead of wrapping the SVG in the code below?@ -47,0 +45,4 @@.ticket {margin-left: auto;}Tiny styling improvement, 5px padding to match the first icon.