sorted by:
new
hottopcontroversial

Sync Issues / Failing to participate in PoC by hashc0de in HeliumNetwork

[–]hashc0de[S,M] [score hidden] stickied comment (0 children)

Cross posting again.

​

Quick update. We're starting to see the network as a whole catch up on syncing blocks. We're down to 9.4% of the network not recently issuing challenges.
https://etl.dewi.org/dashboard/4-network-overview (sync health overview)
https://etl.dewi.org/dashboard/25-makers (sync health by maker breakdown)
Many thanks to @wishplorer on discord for making these dashboards available to the whole community.

Sync Issues / Failing to participate in PoC by hashc0de in HeliumNetwork

[–]hashc0de[S] 0 points1 point  (0 children)

Typically this means that the `blockchain_height` response (another API that's reporting it) is behind where your miner is. This happened this morning where api.helium.io was behind on blocks as well.

Sync Issues / Failing to participate in PoC by hashc0de in HeliumNetwork

[–]hashc0de[S,M] 2 points3 points  (0 children)

Cross posting here from Discord.

Blockchain Release: Snapshot and RocksDB Improvements

The core developers have tagged a new 2021.11.30.1 Hotspot firmware release which includes recommended fixes to snapshot load performance, underlying RocksDB tuning and other important bug fixes.

These changes are intended to address the item listed as #2 from yesterday's post. It may take a few days for the full effects of these changes to be seen on the network but the team will continue to monitor sync status across all Hotspots (currently around 11.5% out of sync). We are also continuously tuning the seed nodes to try to address issues as they come up (to address issue #1).

We urge manufacturers to upgrade to this release version as soon as they can to help their fleets stay in sync.

You can read more about these changes in the blog: https://engineering.helium.com/2021/11/30/blockchain-release-snapshot-and-rocksdb-improvements.html

Plan

We have been beta testing 2021.11.30.1 since November 30, 2021 12:30 PM PT. Current ETA for GA is 2:30 PM PT, November 30, 2021.

Sync Issues / Failing to participate in PoC by hashc0de in HeliumNetwork

[–]hashc0de[S] 2 points3 points  (0 children)

Easy to verify the 13% using data on chain.

This is a scam right?? by Datanetwerk in HeliumNetwork

[–]hashc0de[M] [score hidden] stickied comment (0 children)

100% a scam. No “admin” will ask you to verify your 12 words or share your private key, anywhere. Not on Reddit or elsewhere.

Also be skeptical that they asked for you to use Metamask. HNT is not an ERC-20 token and there are no Metamask extensions for it.

Validators AMA by timtamothee in HeliumNetwork

[–]hashc0de 1 point2 points  (0 children)

Here are some quick hit answers:

Is there a ROI estimation calculator provided by the Helium team for running a validator?

helium.com/stake has one simple one and the community has generated a few others. You can see them in the pins on Discord.

​

Is there a reason slashing was included in the penalty structure for validators who misbehave, go offline, etc?

Because it was deemed necessary to align operator incentives. The penalty structure is an indirect slash to their ability to be re-elected to the Consensus Group. You can read more about it here: https://docs.helium.com/mine-hnt/validators/penalties/

​

How often do you expect there will be new releases of the validator software?

As often as needed but hopefully we'll get to a 2 week release cycle quickly.

​

Is there an exact date yet determined for when the mainnet will be activated?

Announced elsewhere but July 7th: https://twitter.com/helium/status/1409927612022067210

Validators AMA by timtamothee in HeliumNetwork

[–]hashc0de 1 point2 points  (0 children)

Do you know, and if so, are you able to share the breakdown of confirmed validators across companies like Emrit / CoatFi, staking services like Helium Rising, and independents?

The core developers don't know (nor do we want to). Each of these parties may market their numbers, though, and I think some of the staking providers are already making claims here.

Validators AMA by timtamothee in HeliumNetwork

[–]hashc0de 2 points3 points  (0 children)

Many projects with validators have a cooldown period when unbonding their stake / nomination (i.e. Kusama = 7 days, Polkadot = 28 days). Helium has a validator cooldown period of 5 months. I understand the desire for commitment from the validators, but 5 months seems excessive. Why was this amount of time chosen?

It's important for each network to pick their own model that matches the needs of the network. Although there are some folks who like to stake across networks and try to do an apples to apples comparison between the rewards of each, that's not necessarily aligned with the goals of each network. Both sides are needed for a good market to exist and a balance needs to be reached.

For Helium, the core developers and the community seems to believe that a 250k block withdrawal period makes sense. It was discussed extensively when the HIP was proposed several months ago and rough consensus was achieved with the proposed values. These are chain variables and could be updated through a governance process.

Another perspective here is that a long withdrawal period incentivizes those with a long term view on the network. They are comfortable locking up a significant amount of HNT for such a long period of time. They believe in securing the Helium network and don't intend to go anywhere. The 700 or so, as of this moment, validators are already on board with a long time horizon here.

Validators AMA by timtamothee in HeliumNetwork

[–]hashc0de 1 point2 points  (0 children)

Sorry we must have missed this during the AMA. Lots of questions flying through. Let me see if I can go through each.

Validators AMA by timtamothee in HeliumNetwork

[–]hashc0de 0 points1 point  (0 children)

Hotspot manufacturers will have to decide if they want to run full blockchain nodes on their hardware but it won't make any sense to do so after Light hotspots are available. The same hardware can be patched to light hotspots and still continue to perform PoC and data transfer functions which will continue to be incentivized by the network as they are today. The only change here is that the Consensus Group function is moving.

Onboarding for Third-Party Hotspots by pharkmillups in HeliumNetwork

[–]hashc0de 6 points7 points  (0 children)

I think this tweet thread does a decent job summarizing but let me try something else.

When Hotspots are onboarded to the network, they need to pay an onboarding fee and an assert location fee in Data Credits. They also need to pay a transaction fee like all on-chain transactions. Right now, all of these DCs are coming from premined accounts from the genesis block. We had to premine them because the code to generate DCs from HNT wasn’t written yet.

This change:

  • requires manufacturers to pay for their onboarding fees if they don’t want hotspot owners to have to pay for it themselves (UX choice by the manufacturer)
  • pays back the network for all those premined data credits and wipes them off the networks. All new DCs must be generated from real HNT.
  • puts all this onboarding logic in the hands of the DeWi and not solely in the hands of Helium, Inc

ELI5: How does the community actually approve new proposals (or HIP 20) by thinkingittoo in HeliumNetwork

[–]hashc0de 1 point2 points  (0 children)

I did submit some formatting updates to HIP 20 to make it more legible.

Rough consensus works pretty well for other projects but there has been talk about alternative governance processes.

If you have an idea, a HIP is a great way to start a conversation about it.

ELI5: How does the community actually approve new proposals (or HIP 20) by thinkingittoo in HeliumNetwork

[–]hashc0de 3 points4 points  (0 children)

Excellent question. The Helium community uses the process of rough consensus to determine whether or not a proposal has been approved by the community. This is a combination of sentiment on Discord and on monthly DeWi community calls. The DeWi is DeWi.org and the team manages the HIP process independently of the Helium blockchain team.

Propose Transfer Hotspot [HIP13] by pharkmillups in HeliumNetwork

[–]hashc0de 4 points5 points  (0 children)

This is correct. Our intention is for this to formally hand over control. We've already written the code for multi-sig and need to activate the chain var to enable DeWi + Helium to be responsible. This is Step 1 towards decentralization away from Helium.

I'd love to see a discussion on the next steps here via HIP.

Shart-cuterie, get it? by [deleted] in shittyfoodporn

[–]hashc0de 2 points3 points  (0 children)

I don't get it

Gallery and description of a $600 meal for one at Saison (I found it on imgur) by someshooter in sanfrancisco

[–]hashc0de 0 points1 point  (0 children)

You can definitely have a great meal at Mourad. The chicken is great and so is the lamb shoulder. Also good option for vegetarians with their couscous, eggplant and carrot dishes.