Persist claimed pulse in note-claim registry payloads#353
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Description
claimedPulsetoNoteClaimArgsand include aclaimedPulse-awarepulseandclaimedPulsefield when building note-claim payloads/URLs insrc/components/SigilExplorer/registryStore.tsso the claim URL carries the pulse data.claimedPulsethrough to the persisted registry entry, registry payload, and inhaler enqueue path inregistryStore.tsso the value is stored and broadcasted.src/pages/VerifyPage.tsxto computenoteClaimedPulseviauseMemothat prefers the registryclaimedPulseand otherwise falls back toembeddedProof.receivePulse,sharedReceipt.receivePulse, orreceiveSig.createdAtPulsethroughnormalizeClaimPulsefor robust display.Testing
npm run devand the Vite server started successfully and served the app at the local URL. (succeeded)/verifyand captured a full-page screenshot to validate render changes (screenshot produced). (succeeded)Codex Task