We have an engineer assigned to dig a bit more and if there's a fix, I'll let community know.
Hotspots that use Validators serviced by this Validator Operator will not be able to exclude Denylist Hotspots participating in proof-of-coverage, leading to some Denylisted Hotspots earning.The operator has been informed and will be fixing this in the next week or so. With the help of community, we've identified a Validator Operator with custom configuration overrides that is not able to pick up the Denylist list.Our target for this no later than next week.ģ️⃣ Some Hotspots on the Denylist earning? What’s going on?.There is a small bug that the team is investigating when chain sync is turned off, but once this bug is squashed, we can turn off chain syncing. The core team will be releasing a new Hotspot release this week for Makers that will re-enable mux.When will it be fix? These changes will be in a Validator Release, so once we have a release candidate and an activation date set, we’ll let the community know.Ģ️⃣ Light Hotspot Chain Syncing - When will chain sync be turned off?.It is currently selecting 14 witnesses first, then filtering for inactive (aka offline) Hotspots, often leading to When a hex is targeted for a Proof-of-Coverage challenge, the logic is backwards.This will be fixed in a Validator Release and is in review. Receipts out of order and the versioning mismatch can cause a number of proof-of-coverage receipts to be dropped, Hotspots not credited for their work, and leads to lowered Hotspot earnings. This is also contributing to receipt timing issues and receipts coming in out of order. BigEnigma found that the versioning (and thus challenger targeting) was mismatched between ledgers. The Proof-of-Coverage logic has versioning built in.The core team believes they have a good handle on the missing receipts and will be issuing several changes this week.ġ️⃣ Things we found (with the help of technical community, thanks BigEnigma!)
HELIUM TEST TIME CALC UPDATE
There is no update at this time but the activation will not be this week, and will be no sooner than late next week. The fix for this is part of a Validator release that is still in testing and requires chain variable activation. **A note about Hotspots in less dense areas seeing less Proof-of-Coverage Activity** To resolve this, you’ll need more Hotspots in your area to participate in Proof-of-Coverage. If your Hotspot is all alone in a hex without any neighbors that can hear you beacon, the only rewards your Hotspot may earn is Data transfer rewards only. Once the update is applied, flatlined Hotspots can take up to 7 days to come back to life.
HELIUM TEST TIME CALC INSTALL
Hotspots connected to the internet will automatically download and install this update. Makers have been notified of this release and will send the update over-the-air to their Hotspot fleet.
HELIUM TEST TIME CALC BLUETOOTH
A Hotspot can crash due to a latent bug in the bluetooth stack The team identified an issue where Hotspots were talking to both Mainnet and Testnet causing a Hotspot to run out of memory and freeze/flatline.įix 2.
There were two issues have been causing various crashes and out of memory errors on Hotspots that have been preventing them from participating in network and potentially causing "flatline" reports in the community.įix 1. A Hotspot Maker will need to deploy the update to their fleet of Hotspots (which can take several days! Keep an eye out on your maker’s discord or social media), then it can take 3-4 days for a Hotspot to beacon or witness and be rewarded.įlatlined Hotspots can take up to 7 days to come back to life with this bug fix. The core team has released a new Hotspot release to fix the flatline issue! Before explaining what the fix entails, I want set expectations that the flatline fix will not be *immediately* visible. Once these chain variables are activated, we expect to see a blockchain performance improvement and more Proof-of-Coverage receipts received, per block, over a period of several days. The goal is to get as close to 250 receipts back, instead of 170-180 we get today. Once the fix is in, Hotspots may beacon more frequently than the average 3-4 days, but we will have to wait and see how well this works once activated.
At this rate, the average Hotspot beacons every 3-4 days. Currently, 250 Challenges go out per block and about 170-180 receipts come back per block. A fix that should see more PoC receipts coming in per block. Keep in mind that PoC selection is still random, so any improvements (in terms of earnings) can take a while (days++) to see. Updates HIP15/17 values so that Hotspot in less-dense areas are not starved of rewards. In addition to enabling HIP 54, the chain variables also include improvements to proof-of-coverage: The core team is prepared to activate 6 chain variables related to HIP 54: H3Dex.
0 kommentar(er)
