Skip to content

Conversation

kurotych
Copy link
Member

No description provided.

// The firmware version running on the hotspot.
string firmware_version = 3;
// Signer of the message
bytes signer_pubkey = 4;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bbalser we should have a timestamp of when this message was generated, no?
That way someone can't grab an old written message and send it back in.

Copy link
Member Author

@kurotych kurotych Aug 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm following the code style and added received_timestamp_ms field to enabled_carriers_info_report_v1. This field reflects time when the enabled_carriers_info_req_v1 was delivered to the ingest service.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I'm talking about the case where some resends a signed message to the ingest service.
The received_timestamp_ms would reflect the timestamp of when it was received, but the message was generated who knows how long ago and may not be valid any longer.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!
Added timestamp_ms = 4 to the message

@kurotych kurotych marked this pull request as ready for review August 28, 2025 07:29
@kurotych kurotych requested a review from bbalser August 28, 2025 07:29
@kurotych kurotych force-pushed the kurotych/carrier-enablement branch from 8012702 to f4942fe Compare September 9, 2025 15:14
@dcyoung
Copy link

dcyoung commented Sep 22, 2025

@kurotych anything holding this up?

@kurotych
Copy link
Member Author

@kurotych anything holding this up?

To implement this feature, we need to release a new service, which is currently under review
@dcyoung @bbalser

Releated PRs:

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.

4 participants