Skip to content

Add Road Events allocation for GroupData - #3750

Merged
liamcottle merged 1 commit into
meshcore-dev:devfrom
jooray:docs/road-events-data-type
Nov 1, 2026
Merged

liamcottle merged 1 commit into
meshcore-dev:devfrom
jooray:docs/road-events-data-type

Conversation

@jooray

@jooray jooray commented Nov 1, 2026

Copy link
Copy Markdown

Requests GroupData data-type 0x0150 for 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_DATA datagram 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 on 0x0150 and will switch sending to it once this is merged.

The change adds one row to docs/number_allocations.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants