FMSG-003: finalize message hashes and accept hash references - #37
Merged
Conversation
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
1 participant
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.
Define
sha256/psha256on messages, independent batch hashes, and atomic identity assignment when messages become sent, including local-only delivery. Existing numeric IDs remain supported; message routes also accept SHA-256, and requestpidcan preserve an original or batch hash while responsepidremains numeric.Document authorization, immutable encoding, and the added mutation/thread response fields. Require existing records to be finalized offline before serving this API version; sent messages always have hashes. Update examples to match the contract. The binary protocol and hash algorithm are unchanged.
Validation: reviewed against the coordinated daemon/API implementation and PostgreSQL tests; Markdown diff checks pass.
Implementation: daemon, API, and Docker integration. Merge daemon before API, then Docker.