Notice: the skywire whitelist is deprecated since April 1st 2023.
We have transitioned to a new system with daily reward distribution
- The rules in this article may change at any time, depending on if there are problems
- We will attempt to address any issues reported via @skywire Telegram channel
The required minimum Skywire version will be incremented periodically.
All information about rewards will be published here. Please ask for clarification in the @skywire Telegram channel if some things appear to not be covered. Join @SkywirePSA for public service announcements (PSA) regarding the skywire network.
Reward distribution notifications are on telegram @skywire_reward.
408000 Skycoin are distributed annually to those visors which meet the mimimum uptime and the other requirements listed below
A total of up to ~1117.808 Skycoin are distributed daily; evenly divided among those eligible participants on the basis of having met uptime for the previous day.
-
Minimum skywire version v1.3.8 - Cutoff July 1st 2023
-
The visor must be an ARM architecture SBC running on approved hardware
-
Visors must be running on the skywire production deployment
-
Up to 8 (eight) visors may each receive 1 reward share per location (ip address)
-
75% uptime per day is required to be eligible to receive rewards
-
A valid skycoin address must be set for the visor
-
The visor must be connected to the DMSG network
-
Transports can be established to the visor
-
The visor responds to pings - needed for latency-based rewards
-
The visor produces transport bandwidth logs - needed for bandwidth-based rewards
View the version of skywire you are running with:
skywire-cli -v
skywire-visor -v
The new reward system requires Skywire v1.3.8
Requirement established 5-25-2023
Rewards Cutoff date for updating 7-1-2023
The deployment your visor is running on can be verified by comparing the services configured in the visor's .json config against conf.skywire.skycoin.com It will be automatically updated any time a config is generated or regenerated.
Daily uptime statistics for all visors may be accessed via the
- uptime tracker or using skywire-cli
skywire-cli ut -n0 -k <public-key>
The skycoin address to be rewarded can be set from the cli:
skywire-cli reward <skycoin-address>
or via the hypervisor UI.
the example above shows the genesis address for the skycoin blockchain. Please do not use the genesis address.
For any given visor, the system survey and transport bandwidth logs should be downloaded hourly over dmsghttp.
This can be verified by examinimg the visor's logging:
Note: the transport bandwidth logs will only exist if it was generated; i.e. if there were transports to that visor which handled traffic.
Note: the system survey (node-info.json) will only exist if the reward address is set.
If your visor is not generating such logging, please reach out to us on telegram @skywire for assistance
If the visor is not able to meet the other requirements, that is usually not the fault of the user nor is it something the user is expected to troubleshoot at this time. Please ask for assistance on telegram @skywire
The skycoin reward address may be set for each visor using skywire-cli or for all visors connected to a hypervisor from the hypervisor UI
The skycoin reward address is in a text file contained in the "local" folder (local_path in the skywire config file) i.e local/reward.txt.
The skycoin reward address is also included with the system survey and served, along with transport logs, via dmsghttp.
The system survey is fetched hourly with skywire-cli log; along with transport bandwidth logs.
Once collected from the nodes, the surveys for those visors which met uptime are checked to verify hardware and other requirements, etc.
The system survey is only made available to those keys which are whitelisted for survey collection, but is additionally available to any hypervisor or dmsgpty_whitelist keys set inthe config for a given visor.
The public keys which require to be whitelisted in order to collect the surveys, for the purpose of reward eligibility verification, should populate in the visor's config automatically when the config is generated with visors of at least version 1.3.8.
VM's, servers or personal computers are not permitted to collect rewards
The following hardware is eligible for rewards:
- Prime
- 2G-IOT
- 4G-IOT
- i96
- Lite
- Lite2
- One
- One-Plus
- PC
- PC-Plus
- PC2
- Plus
- Plus2
- Plus2E
- RK3399
- Win
- Win-Plus
- Zero
- Zero LTS
- Zero-Plus
- Zero-Plus2
- 3
- 1-Model-A+
- 1-Model-B+
- 2-Model-B
- 3-Model-B
- 3-Model-B+
- 4-Model-B
- Compute Module 3
- Compute Module 4
- Zero-W
- Zero
- Tinkerboard
- BPI-D1
- BPI-G1
- BPI-M1
- BPI-M1+
- BPI-M2
- BPI-M2+
- BPI-M2-Berry
- BPI-M2M
- BPI-M2U
- BPI-M64
- BPI-R2
- BPI-R3
- BPI-Zero
- X2
- Cubietruck
- Cubietruck-Plus
- 1
- 2
- 4
- Developer Board IV
- 4
- Le-Potato-AML-S905X-CC
- Renegade-ROC-RK3328-CC
- Tritium-ALL-H3-CC
- MiQi
- NanoPi
- 2
- 2-Fire
- A64
- K2
- M1
- M1-plus
- M2
- M2A
- M3
- M4
- NEO
- NEO-Air
- NEO-Core
- NEO-Core2
- NEO2
- NEO2-Black
- S2
- Smart4418
- C2
- C4
- HC1
- HC2
- MC1
- XU4
- Lime1
- Lime2
- Lime2-eMMC
- LimeA33
- Micro
- Pine-A64
- Pinebook-A64
- Sopine-A64
- Rock64
- ROCKPro64
- Rockpi 4
- Rockpi S
- Rockpi E
- Rockpi N10
- CuBox-i
- CuBox-Pulse
- Humming-Board
- Humming-Board-Pulse
- ClearCloud-8K
- ClearFog-A38
- ClearFog-GT-8K
- Blu
- Bricks
- Dual
- Neo
- Quad
- X86
- X96 mini
- A95X F1 Smart TV Box
- ROCK Pi S
- ZXV10 B860H
If you would like to use other boards please contact the team first for approval ; only the boards on the list are guaranteed to be eligible for rewards.