Integrating Location Optimization into the Whive Protocol
For the past 5 months since the launch of the Whive Protocol and Network on 02/02/2020 about 5 million WHIVE coins have been mined by nodes from about 10+ countries around the World.
The countries included in order of hash-power: China, United States, Germany, Bulgaria, Kenya, United Kingdom, Rwanda, Romania, France, Netherlands, Japan and Canada.
In order to ensure more equitable distribution of the WHIVE tokens around the World based on the Solar Reliability Indices(SRIs) as outlined in our upcoming green-paper we came up with following optimization schemes.
*Processor optimization score (ps)
*Timezone optimization score (ts)
*Location optimization score (ls)
The 3 scores are added together to form the total reward score (rs) which determines the probability with which a node will be allowed to generate a viable yespower block hash on the network. For instance, if a node scores a total reward score of 20% it will have a 20% chance of being allowed to generate a viable yespower block hash on the network. Indeed, nodes with favorable processors and in favorable timezones and locations will always score higher than nodes with less desired timezones and locations.
Favorability is based on computations that best approximate mobility in computer processing power and the Solar Reliability Indexes (SRIs) for nodes on the Whive network.
The SRI parameter indicates the amount of Photo-Voltaic (PV) power capture potential of Solar energy on a global scale as depicted in Figure 1. Africa is depicted as the region with the highest PV power potential in the World. Hence, why the Whive protocol primarily focuses on this region.
Testers ran the script below for checking Machine Processor and Location Optimization:
SCRIPT: https://github.com/whiveio/YesPowerAlgo_Seniors_Project/blob/locator/optimizer.c
Sample results were as follows:
MACHINE 1: Windows Laptop in Nairobi with 4 of 4 processors online
Latitude: -1.284100
Longitude: 36.815500
Original Process Reward: 15
Timezone Reward: 40
Location Reward: 70
Process Reward: 7
Total Percentage Reward: 43
Randomizer: 13
Create YP Hash: Success
The odds of creating a Yespower hash to mine a block for this machine is 43%
—
MACHINE 2: Windows Server in Rwanda with 64 of 64 processors online
Latitude: -1.950110
Longitude: 30.058800
Original Process Reward: 15
Timezone Reward: 40
Location Reward: 70
Process Reward: 0
Total Percentage Reward: 41
Randomizer: 50
Create YP Hash: Failure
The odds of creating a Yespower hash to mine a block for this machine is 41%
—
MACHINE 3: Windows Node in the United States with 4 of 4 processors online
Latitude: 42.976700
Longitude: -78.795900
Original Process Reward: 15
Timezone Reward: 10
Location Reward: 0
Process Reward: 7
Total Percentage Reward: 3
Randomizer: 59
The odds of creating a Yespower hash to mine a block for this machine is 3%
—
MACHINE 4: Raspberry PI in Nairobi with 4 of 4 processors online
Latitude: -1.284100
Longitude: 36.815500
Original Process Reward: 70
Timezone Reward: 40
Location Reward: 70
Process Reward: 35
Total Percentage Reward: 52
Randomizer: 9
Create YP Hash: Success
As you can see from the results above the smaller ARM computing devices running LINUX such as Machine 4 located in Nairobi Kenya had the best results with a score of 52 meaning the node has a 52% of generating a yespower hash during that permutation. Machine 3 based in the U.S. has only 3% chance of generating a yespower hash for every permutation.
The location optimization algorithm favors the African locations vis a vis the American Timezones; which should result in more adoption of smaller computing solar powered nodes across Africa where sustainable and equitable adoption of renewable energy is mostly needed!
To understand more about the Timezone and Processor optimizations implemented in the Whive protocol, Read This.
In the meantime, share your results for the above script in the comments below; they shall go a long way in improving our algorithm and utility of the Whive protocol.
Many thanks to our vibrant community who helped produce these results and made optimizing the algorithm possible!
If you still don’t know whats going on. Don’t worry! Read more about the Whive protocol here.
Join the fun at the Community group chat here, to ask all those burning questions.
