From 7e7b49852837afc08ea8d058d5d79f79d6dfeb2c Mon Sep 17 00:00:00 2001 From: Barry Blaha <6305836+Beasta@users.noreply.github.com> Date: Sat, 24 Oct 2020 15:46:18 -0700 Subject: [PATCH] Fix spelling in 0015-beaconing-rewards.md (#64) Co-authored-by: Abhay Kumar --- 0015-beaconing-rewards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0015-beaconing-rewards.md b/0015-beaconing-rewards.md index 1605f9452..ba616d8cd 100644 --- a/0015-beaconing-rewards.md +++ b/0015-beaconing-rewards.md @@ -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).