-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unused keys for makers in bad standing #1109
base: main
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,78 @@ | |||
# HIP XXXX: Wipe unused onboarding keys for makers in bad standing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably needs a more clear title. most of the community doesn't know what an onboarding key is (unfortunately).
How about something like:
Remove Onboarding Capability for Hotspots Manufactured by Makers in Bad Standing
|
||
This HIP proposes to wipe any remaining unused onboarding keys for makers not in good standing. | ||
|
||
We are seeing gaming clusters setup 100+ hotspots in a few minutes, this leads the authors to believe they are selling keys without selling hardware. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is quite an assertion. We should probably have some real data behind it in the HIP before having that allegation out there.
|
||
We are seeing gaming clusters setup 100+ hotspots in a few minutes, this leads the authors to believe they are selling keys without selling hardware. | ||
|
||
We wish to remove any keys for makers in bad standing that have not been used, and offer a proof of purchase and delivery form to be run by the Iot working group for any users with real hardware. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This creates a new customer service flow. Is the IOT WG prepared to do this?
LongAP 49 | ||
Embit 1 | ||
|
||
Helium foundation will remove these keys from the onboarding server, and setup a flow for users to submit proof of purchase and proof of delivery for any hotspots where physical hardware exists. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's say 10% of the above list tries to go through this flow that means ~26k potential customer service requests that the HF + IOTWG has to manage.
No description provided.