Helium🎈 Profile picture
22 Nov, 12 tweets, 3 min read
This week the @helium Network was severely tested. The core developers and Helium community have worked together to address multiple challenges that have resulted from its unprecedented growth.
A more detailed, engineering-specific post-mortem will be published later this week, but we wanted to provide initial details on these incidents so everyone could have some early context on what happened.
First, BIG THANKS to everyone for their contributions and their patience through the past week. A core strength of this Network is that it’s built by the people: Hotspot owners, Validator operators, device owners, developers, manufacturers, and mods make the Network resilient.
Second, during these challenges, $HNT was always safe, and during the disruptions, data transfer was largely unaffected. Robust data transfer was designed into the Helium Network from day one and will be continuously improved and updated by the core developers and the community.
Both last week and this weekend’s outages resulted from large-sized blocks that Hotspots and Validators could not agree upon and ingest into the chain. These blocks were filled with transactions from faulty state channels that process data transfer packets for Discovery Mode.
The Network was able to recover from last week’s chain halt after Validators deployed new fail-safe measures to prevent large blocks from being proposed and prevent new faulty state channels from reoccurring.
These changes were rapidly developed and deployed by core developers and the community. Read the full details on the Engineering Blog: bit.ly/3CF1jdS.
This weekend a second large block made up of remaining Discovery Mode state channels had already formed before the fixes were applied. Helium App developers have since decided to disable Discovery Mode until further notice.
In addition to these changes, new firmware releases were made available to all Hotspot Makers to ensure their Hotspot fleets could sync, participate in Proof of Coverage, and transfer device data. Read about the releases on the Engineering Blog: bit.ly/3CDFtaM.
The community and the HIP-19 process has approved a variety of Hotspot vendors, all of which provide diversity and resilience to the Network. These full blockchain nodes are affected differently by software updates and organic network expansion to 300K nodes and beyond.
The core developers commit to supporting all currently approved Hotspots with core blockchain and miner updates until the Light Hotspot software upgrade is available for manufacturers to implement and migrate their fleets.
These early days of building the Network are challenging. We have learned a lot very quickly over the last two years and have made significant enhancements to ensure all continues to run smoothly and make for a stronger and more resilient Network for the next several decades.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Helium🎈

Helium🎈 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @helium

10 Sep
Helium Explains: The @helium Token Image
The @helium Network connects #IoT (and soon 5G) devices in ways never before possible and at a fraction of the cost of cellular, without users needing to deploy and maintain wireless infrastructure. Image
The Network's range is optimized for devices running on @helium #LongFi, a combination of #LoRaWAN and the Helium Blockchain. This opens up a number of use cases including asset tracking, supply chain logistics, agricultural #tech, & more, up to 10 miles+ from nearby Hotspots. Image
Read 8 tweets
4 Apr
Helium Explains: The @helium Token Image
The @helium Token is the native cryptocurrency and protocol token of the Helium Blockchain. Its symbol is $HNT. The first $HNT was produced on July 29th, 2019 at 09:43pm UTC as part of the Network's genesis block. Prior to this date, there was no premine of $HNT. Image
The @helium Token is designed to serve the needs of two primary parties on #ThePeoplesNetwork:
1. Hotspot owners, who mine $HNT for providing and maintaining coverage.
2. Enterprises and developers, who connect #IoT devices and applications to the Network using Data Credits. Image
Read 7 tweets
19 Mar
Helium Explains: $HNT Mining Rewards
Hotspots earn $HNT for building and securing network infrastructure and transferring device data. The amount of $HNT distributed to Hotspots depends on the type of “work” they perform based on the value to the network. Here’s a full breakdown of $HNT mining rewards.
Hotspots are chosen as a Challenger by the network to issue Challenges (encrypted messages over the internet) to a selected Hotspot, receiving 0.95% of token rewards for doing so. Hotspots can issue challenges to any location around the world 🌎, not just to local Hotspots.
Read 7 tweets
16 Oct 20
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.
Let’s take a walk back in time, shall we? We first read @socrates1024 #HoneyBadgerBFT paper in 2018. Our implementation was similar to @ethereum, using the GHOST protocol and @bitcoin #NakamotoConsensus to select a winner for each block.
Read 10 tweets
15 Oct 20
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.
Read 6 tweets
14 Oct 20
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.
Read 10 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Thank you for your support!

Follow Us on Twitter!

:(