One of the more unique aspects of the @Helium Network is the Consensus Protocol. Proof-of-Coverage (#PoC) is used for sybil resistance and to periodically select a new #HoneyBadgerBFT group.
Ask any Hotspot host and they will tell you how they dream of joining the coveted Consensus Group - a small group of Hotspots on #ThePeoplesNetwork that receives 6% of all $HNT mined per epoch.
It turned out #NakamotoConsensus was not ideal due to its deterministic nature. We wanted something with instant block finality that was fast, tolerant of high latency, and censorship resistant.
Unlike @filecoin and others, the @Helium Network is comprised of many low power nodes running on consumer grade backhaul. Tolerance of latency and the ability to process messages asynchronously is a must.
#HoneyBadgerBFT met all these criteria. In the @Helium Network a new Consensus Group is elected every 35 blocks based on activity and #PoC performance. The new group runs a distributed key generation process, implemented from a paper written by @aniketpkate.
All transactions in the @Helium Network are encrypted. Each member of the #HoneyBadgerBFT group only has a shard of the complete private key, and a majority of group members are required to decrypt messages before validating them and adding them to blocks.
To dive deeper into the @Helium Consensus Protocol and the $HNT mining process that’s associated, make sure to check out our #developer documentation: bit.ly/3lLznNE
The Consensus Group rotates between more than 10,000 active members, making @Helium one of the most diverse censorship #blockchain networks that we know of. What other projects are doing interesting things with diversity and censorship resistance?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Following our thread on the work of a Challenger in Proof-of-Coverage (PoC), it’s only fair we take a look at the Challengees who are key to successfully transferring packets, completing PoC challenges and earning $HNT!
The role of the Challengee is to prove to the Challenger that they are actually creating network coverage that #LongFi devices can use. For successfully responding to these challenges, the Challengee is rewarded in newly minted $HNT.
Challengees receive encrypted multi-layer packets wirelessly, via RF. Each layer of the packet is encrypted for specific Challengees in a sequential path. When a Challengee receives a packet and can decrypt it, they send their proof back to the Challenger via the #p2p network.
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.
How exactly do Hotspots mine $HNT? You asked. We answer.
The amount of $HNT Hotspots mine depends on the type of “work” they perform based on the value to the network. This validation of network contribution is accomplished by a new work algorithm called Proof-of-Coverage (PoC).
There are 5 types of work a Hotspot can participate in:
1. PoC CHALLENGER: Hotspots are chosen by the network to issue “challenges”, or encrypted messages, over the Internet to a target group of Hotspots. Challenges are used by PoC to validate wireless coverage.
2. PoC CHALLENGEE: Hotspots validate nearby wireless coverage by broadcasting challenges received from challengers using Radio Frequency (RF). The amount of $HNT each Hotspot earns depends on whether any of these RF broadcasts are received by other nearby Hotspots.