The other day we shared a thread on the 5 types of work a Hotspot can perform to mine $HNT. Today we take a look at the work of a Challenger in Proof-of-Coverage (PoC).

Challenges are used by PoC to validate wireless coverage. As a Challenger, your Hotspot is chosen by the network to create a challenge, or encrypted multi-layer packet, over the Internet.
The challenge process begins with the Challenger selecting an initial target Hotspot, followed by a group of Hotspots known by the @helium blockchain to be within range of each other as a result of RF witnessing.
These Hotspots are given a multi-layer packet (think an “envelope of envelopes”) that only they can decrypt to prove they are providing legitimate wireless coverage.
The Challenger could be anywhere in the world and does not need to be co-located near other Hotspots. Challenge requests occur every 120 blocks, and if the consensus group accepts the challenge transaction as being valid, the challenge proceeds.
One very cool thing about public key cryptography is that data can be encrypted for decryption by a specific recipient while only knowing the recipient's public key. This allows the Challenger to encrypt each layer of the packet specifically for only certain Hotspots to decrypt.
The Challenger delivers this multi-layered packet via the Internet #p2p network to the first Hotspot in the challenge path.
Once Challengees and Witnesses broadcast and receive the layers of the packet via RF, they send proof they decrypted their layer of the packet back to the Challenger. The Challenger then bundles the receipts together and submits them to the consensus group to be rewarded in $HNT.
The role of the Challenger is similar to something like the role of a client in the @filecoin network. In that case, the client is asking a miner for proof that the file they are storing is still being stored.
In the case of Helium, the Challenger is asking the miners on the network to prove they are still creating network coverage that can be used by devices.

🎙To learn more, listen to this great podcast episode on PoC with @armanhotspot and @amirhaleem: https://t.co/dUx9eFq06d.

More from Tech

After getting good feedback on yesterday's thread on #routemobile I think it is logical to do a bit in-depth technical study. Place #twilio at center, keep #routemobile & #tanla at the periphery & see who is each placed.


This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.

We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.

Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.

This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile

You May Also Like