Skip to content

Commit

Permalink
Fix spelling in 0015-beaconing-rewards.md (#64)
Browse files Browse the repository at this point in the history
Co-authored-by: Abhay Kumar <abhay@helium.com>
  • Loading branch information
Beasta and abhay authored Oct 24, 2020
1 parent 2b02b5c commit 7e7b498
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion 0015-beaconing-rewards.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Beaconing with the modified reward structure outlined below does a much better j
The existing PoC method and reward structure heavily rewards transmitters with minimal rewards for receivers while the vast majority of LoRaWAN usage is for unconfirmed uplinks, meaning hotspots mostly receive data.
This reward structure better rewards real coverage and encourages honest hotspot owners to see maximized rewards as they build towards efficient network topologies.

Beaconing, reardless of reward structures allows the elminination of Multi-hop PoC. Multihop PoC significantly more complex than beaconing requiring complex path building and path verification,
Beaconing, regardless of reward structures allows the elimination of Multi-hop PoC. Multihop PoC significantly more complex than beaconing requiring complex path building and path verification,
Significant overhread of building long paths that never complete (due to hop reliability being low). Large payload sizes that are a-typical for many LoRa applications and require higher datarates, etc.
A lot of implementation complexity is removed with beaconing and those CPU and ledger resources can be re-allocated to more beneficial purposes (like combating gaming/exploitation).

Expand Down

0 comments on commit 7e7b498

Please sign in to comment.