Repository navigation
Add Road Events allocation for GroupData - #3750
Merged
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
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.
Requests GroupData data-type
0x0150for Road Events.Road Events are signed road reports (police, accidents, closures, hazards…) and votes on them, defined as Nostr kinds 1315/1316. On a MeshCore radio, each event travels as one
PAYLOAD_TYPE_GRP_DATAdatagram on the public hashtag channel#roadstr. The frame is 117–163 bytes for a report and 134 for a vote, and it carries the author's key and Schnorr signature. Any receiver can verify it and rebuild the original event byte for byte, so a node with internet can pass it on to Nostr relays, and back, without being trusted.Two independent, interoperable apps already send and receive it:
Both run the same conformance vectors. On the phone they reach the radio through MeshCore Open's local API (proposed in zjs81/meshcore-open#616), so road events and chat share one companion connection. Both currently use the dev value
0xFF52. They are already listening on0x0150and will switch sending to it once this is merged.The change adds one row to
docs/number_allocations.md.