Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update mobile-proof-of-coverage.mdx for 0.75 speedtest multiplier (HIP98) #1930

Merged
merged 1 commit into from
Jan 15, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 13 additions & 12 deletions docs/network-mobile/mobile-proof-of-coverage.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ This new algorithm uses the location of the Radio to calculate MOBILE Rewards ba
res12 hexes receiving coverage from a given Radio.

The MOBILE Rewards Oracle will calculate a coverage model for each Radio by considering the physical
location, antenna direction, radio max transmit power, and Obstruction Data Oracle inputs to
location, antenna direction, radio max transmit power to
calculate the number of res12 hexes receiving coverage from each Radio.

Depending on the number of res12 hexes and the resulting signal power in each, the MOBILE Rewards
Expand Down Expand Up @@ -375,7 +375,7 @@ Test results must be collected before a Moving Average can be calculated.

:::info Speed test impact on Radio rewards

Each 5G Hotspot is given a `speedtest multiplier` of either `0.0`, `0.25`, `0.5` or `1.0`.
Each 5G Hotspot is given a `speedtest multiplier` of either `0.0`, `0.25`, `0.5`, `0.75` or `1.0`.

This multiplier is applied to all connected Radios in rewards calculations.

Expand All @@ -395,7 +395,8 @@ Speed Test results are categorized into one of four Tiers - `Acceptable`, `Degra

| Speed Test Tier | Speedtest Multiplier | Requirement (speeds in Mbps, latency in ms) |
| :-------------: | :------------------: | :----------------------------------------------------------- |
| **Acceptable** | `1.00x` | `100+` Download, **AND** `10+` Upload, **AND** `<50` Latency |
| **Good** | `1.00x` | `100+` Download, **AND** `10+` Upload, **AND** `<50` Latency |
| **Acceptable** | `0.75x` | `75+` Download, **AND** `8+` Upload, **AND** `<60` Latency |
| **Degraded** | `0.50x` | `50+` Download, **AND** `5+` Upload, **AND** `<75` Latency |
| **Poor** | `0.25x` | `30+` Download, **AND** `2+` Upload, **AND** `<100` Latency |
| **Fail** | `0.00x` | `<30` Download, **OR** `<2` Upload, **OR** `>100` Latency |
Expand Down Expand Up @@ -424,20 +425,20 @@ rewards.
<TabItem value="all_acceptable" label="✅ All Acceptable" default>

```bash
Download 200 -> `Acceptable`
Upload 40 -> `Acceptable`
Latency 15 -> `Acceptable`
Download 200 -> `Good`
Upload 40 -> `Good`
Latency 15 -> `Good`
---------------------------------
Speed Test Tier -> `Acceptable` -> 1.0x Multiplier
Speed Test Tier -> `Good` -> 1.0x Multiplier
```

</TabItem>
<TabItem value="degraded upload" label="❎ Degraded Upload" default>

```bash
Download 200 -> `Acceptable`
Download 200 -> `Good`
Upload 6 -> `Degraded`
Latency 15 -> `Acceptable`
Latency 15 -> `Good`
---------------------------------
Speed Test Tier -> `Degraded` -> 0.5x Multiplier
```
Expand All @@ -448,7 +449,7 @@ Speed Test Tier -> `Degraded` -> 0.5x Multiplier
```bash
Download 40 -> `Poor`
Upload 6 -> `Degraded`
Latency 15 -> `Acceptable`
Latency 15 -> `Good`
---------------------------------
Speed Test Tier -> `Poor` -> 0.25x Multiplier
```
Expand All @@ -457,8 +458,8 @@ Speed Test Tier -> `Poor` -> 0.25x Multiplier
<TabItem value="failed_latency" label="🆘 Failed Latency" default>

```bash
Download 200 -> `Acceptable`
Upload 40 -> `Acceptable`
Download 200 -> `Good`
Upload 40 -> `Good`
Latency 150 -> `Fail`
---------------------------------
Speed Test Tier -> `Fail` -> 0.0x Multiplier
Expand Down