HIP 50: Display All Potential Beacon Witnesses

[hiptron]

• Author(s): @captainhindsite
• Start Date: 2021-12-09
• Category: Technical
• Original HIP PR: HIP draft – Display all potential beacon witnesses #322
• Tracking Issue: HIP 50: Display All Potential Beacon Witnesses #331 (this page)

rendered view

https://github.com/helium/HIP/blob/master/0050-display-all-potential-beacon-witnesses.md

summary

Under the current Proof Of Coverage (POC) model, for each beacon sent, current tools / reporting mechanisms allow interested parties to monitor only those witnessing hotspots which have been randomly selected as potentially eligible to receive rewards. The details of other hotspots which could have successfully witnessed said beacon but were excluded by that random selection process remain unreported and inaccessible to hotspot owners

This can, especially during periods of sub-optimal network performance, make it difficult for hotspot owners to know if their hotspot is performing poorly in terms of witnessing beacons, or if they are just 'unlucky' with regard to the random selection process in effect. This in turn can prove an obstacle to hotspot owners wishing to optimise their installations for coverage and rewards. I propose a change to reporting, to display all potential witnesses regardless of the results of the random selection process, to provide greater clarity and confidence for hotspot owners seeking to optimise their installations.

[hiptron]

@captainhindsite apologies again for delay getting this merged. I've also updated title to clarify that this would require recording all witnesses in order to display them

[captainhindsite]

OK - thanks for the update. Will a 'channel' be created on Discord for discussion?

…

On Mon, 24 Jan 2022 at 15:38, DeWi HIP Editors ***@***.***> wrote: @captainhindsite <https://github.com/captainhindsite> apologies again for delay getting this merged. I've also updated title to clarify that this would require recording all witnesses in order to display them — Reply to this email directly, view it on GitHub <#331 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATPYRUEIQ4SZHHKVNJMELXLUXVWZFANCNFSM5MVWGKLQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[captainhindsite]

I see it just popped up.

…

On Mon, 24 Jan 2022 at 15:40, Pete Robinson ***@***.***> wrote: OK - thanks for the update. Will a 'channel' be created on Discord for discussion? On Mon, 24 Jan 2022 at 15:38, DeWi HIP Editors ***@***.***> wrote: > @captainhindsite <https://github.com/captainhindsite> apologies again > for delay getting this merged. I've also updated title to clarify that this > would require recording all witnesses in order to display them > > — > Reply to this email directly, view it on GitHub > <#331 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ATPYRUEIQ4SZHHKVNJMELXLUXVWZFANCNFSM5MVWGKLQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[hiptron]

Yep! thx again for your patience. we are discussing how to onboard folks to help me administer the HIP process

[jamiew]

I'm renaming back to the original title, Display All Potential Beacon Witnesses

[abhay]

This is a potentially unbounded addition of data to the chain without obvious benefit to all participants.

If the purpose of this is diagnostic, I'd consider encouraging diagnostic tools being added to manufacturer firmware that allows for collection of PoC packets and "purchased" via Helium Routers. These Routers could be owned by individual Hotspot owners or by manufacturers and provided as a service (somewhat like Discovery mode). This would both encourage usage of the network and get the data you're looking for.

[jamiew]

@abhay what do you think of the old idea of a listen-only gossip stream from the validator group? This was mentioned in discord channel again. From what I understood that would allow for general auditing as well as enable a third-party to capture data for something like this

[vincenzospaghetti]

@captainhindsite This HIP is resolved by HIP 70. Can we close this HIP? Please confirm or if I don't hear from you, I will go ahead and close it at the end of the week. Congrats on submitting your HIP and contributing to the community!

[captainhindsite]

Thanks for letting me know. Please go ahead and close HIP50. I'll check out HIP70

…

On Tue, 18 Oct 2022, 19:22 vincenzospaghetti, ***@***.***> wrote: @captainhindsite <https://github.com/captainhindsite> This HIP is resolved by HIP 70. Can we close this HIP? Please confirm or if I don't hear from you, I will go ahead and close it at the end of the week. Congrats on submitting your HIP and contributing to the community! — Reply to this email directly, view it on GitHub <#331 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATPYRUBKREUYRVQSZF5E5HTWD3TBZANCNFSM5MVWGKLQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>