-
Notifications
You must be signed in to change notification settings - Fork 408
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
HIP 115: Redefining the MOBILE Maker Approval Process #921
Conversation
This Helium Improvement Proposal (HIP) defines the approval process and requirements for Manufacturers of MOBILE Hotspots and Access Points (MOBILE Makers) to get a Maker Key.
Q1: What does Stripping of Maker Keys actually mean? If there are 4 requirements for each tier better to number them rather than bullet them. A Tier3 vendor needs 50M x $0.0036 and 2B DC = >$200K Currently Tier3 vendors (FreedomFi and Bobcat) onboard ($40) and assert ($10) using DC on both MOBILE and IOT networks from the same wallet. So currently supporting 100 onboards for both networks (inc assert) would need 1B DC not 400M DC. For slashing, better we work with UTC defined epochs not calendar days. |
Addressed Waveforms comments
Comments have been addressed in newest commit. Q1: Added Clarification Comment 5: Added numbers instead of bullets Comment 7: changed days to epochs |
This Helium Improvement Proposal (HIP) defines the approval process and requirements for Manufacturers of MOBILE Hotspots and Access Points (MOBILE Makers) to get a Maker Key.