Issue

• Link: Syncrobit #60 and #58 ecc selection helium-syncrobit#2
• Summary: Syncrobit has multiple potential key locations

How

• check for the existence of a duplicate key on the helium API and onboarding server
• change syncrobit swarm key and onboarding key URI attributes to have multiple slot=0 query strings and when this is identified is when we need to check the API
• start by checking the provided slots against the API. If these do not work, try slots 0 to 15, if this still does not work then fail with error message
• it is possible that the onboarding key and public key are different as per the helium OG miner, however I am actually yet to see this on a Syncrobit despite them mentioning this in the codebase https://github.com/syncrobit/chameleonos/blob/main/board/common/overlay/etc/init.d/S31hwdetect#L60-L65
• when onboarding key and public key differ, you can look them up on the onboarding server using either... for example https://onboarding.dewi.org/api/v2/hotspots/1129PajMfySVrXbfNuEYNppfDejamcAxRbntAySMwLSZDhJjqeen and https://onboarding.dewi.org/api/v2/hotspots/112638Zq4es37K1jcEVVLUU52ak52mxbpD8f73pHF9KXeqLtA6Rj are the same device. You can see onboardingKey and publicAddress are different. Either link returns the same JSON

Screenshots

References

Relates-to: #230
Relates-to: NebraLtd/helium-syncrobit#2
Relates-to: #222
Closes: #221
Relates-to: #238
Ref: https://nebraltd.slack.com/archives/C024BNQ1Y6T/p1680959586571789?thread_ts=1680959586.571789&cid=C024BNQ1Y6T

Checklist

• Tests added
• Cleaned up commit history (rebase!)
• Documentation added
• Thought about variable and method names