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

Next.js has taken the web dev world by storm

It’s the @reactjs framework devs rave about praising its power, flexibility, and dev experience

Don't feel like you're missing out!

Here's everything you need to know in 10 tweets

Let’s dive in 🧵


Next.js is a @reactjs framework from @vercel

It couples a great dev experience with an opinionated feature set to make it easy to spin up new performant, dynamic web apps

It's used by many high-profile teams like @hulu, @apple, @Nike, & more

https://t.co/whCdm5ytuk


@vercel @hulu @Apple @Nike The team at @vercel, formerly Zeit, originally and launched v1 of the framework on Oct 26, 2016 in the pursuit of universal JavaScript apps

Since then, the team & community has grown expotentially, including contributions from giants like @Google

https://t.co/xPPTOtHoKW


@vercel @hulu @Apple @Nike @Google In the #jamstack world, Next.js pulled a hefty 58.6% share of framework adoption in 2020

Compared to other popular @reactjs frameworks like Gatsby, which pulled in 12%

*The Next.js stats likely include some SSR, arguably not Jamstack

https://t.co/acNawfcM4z


@vercel @hulu @Apple @Nike @Google The easiest way to get started with a new Next.js app is with Create Next App

Simply run:

yarn create next-app

or

npx create-next-app

You can even start from a git-based template with the -e flag

yarn create next-app -e https://t.co/JMQ87gi1ue

https://t.co/rwKhp7zlys

You May Also Like