Yeah two decimal points would be great. Since the range from 1-200 misses will still be shown as 99%.
For true competitiveness and quality service.
2 Likes
@SCENE @cop4200 thank you for opening up the discussion about the decimal points on the validators uptime.
For 2 decimal placing, every 0.01% corresponds to 2 blocks missed.
For 1 decimal placing, every, 0.1% corresponds to 20 blocks missed.
We have added #12 Changing uptime percentage to show 2 decimal placings to the Monday board.
3 Likes
If I may, it would be nice to also display only the votes a validator could vote on, depending on the birth date of a validator.
For example, if a validator was born after the proposal #7 voting start, it would show only #0/2, #1/2 or #2/2.
Thanks.
@FrenchXCore
Thank you for your hardwork!
1 Like
Talking about uptime, could you please also consider taking snapshots of missed blocks once per 20,000 blocks and then using this number to calculate the longterm uptime?
This will be a true representation of long term performance rather then just the last 27.7 hours.
Updates 17-2-22
Improvements made to the Function X explorer:
As requested, we have taken into consideration, a validator’s birth date and adjusted the denominator of each validator’s participation. @FrenchXCore . I will be shifting #9 into the launch log of the public monday board.
The browser now displays 1 more decimal place @cop4200 . I think that should suffice. will be moving #12 to the launch log.
For those who have yet to vote for the Kronos Research proposal please do so here.
I’d just like to share a joke while we’re on governance and its a tech joke. 404 and 403 errors went to vote in the last US presidential campaign. 404 voted for Trump. And 403?
For-bidden
4 Likes
And when you think about it, Trump said only 404 voted 403 !!! LOOOOL !
Thanks for that joke : didn’t know it !
Greetings to all. We are finally ready to present our logo (@LuckyFX):
Validator: fxvaloper1zn0p7rqp2s702r4aua98gdtlwp6gza904h2dls
7 Likes
Update 20-2-22
The latest EGF proposal guidelines have been added to a separate gitbook.
For future references, i will create a directory within the FunctionX-EGF-Proposal-Guidelines folder to track all applicants who have drafted the proposal guidelines. @Superbit123
I have added your logo in @Ardent . for future validator logo updates, do kindly follow the instructions in the readme file in this repo. @peteyg @RockPool @FrenchXCore
5 Likes
Update 23-2-22
-
ENS has been deployed on f(x)Core Testnet. You may find more information here.
-
I have made some changes to the Gitbook and amended some details like snapshot file names and did some reformatting.
-
Future applicants will fork the repo, put their project application in the applications folder. then we can proceed to track the progress and any reports. I’ve added a placeholder here. More information can be found in FunctionX Github. @Superbit123
4 Likes
Updates 24-2-22
Kronos have submitted their proposal and is for all to see on our public github. They are the first team to submit their proposal to the public Function X Github EGF section to be stored under the new scheme.
3 Likes
Update 25-2-22
Have updated the governance proposal information on our techinical documentation. Do use it to get up to speed about the entire proposal process and details. Governance Proposal Information | Function X Docs
4 Likes
Updates 8-3-22
Validator rewards /status info/creation date queries
Hi fellow validators! I’ve wrote a script to query and generate reports for rewards, validator info_status amongst other things.
You can view the repo here. Pardon me that this was done in a rush and its basically running OS commands, returning the data in a json file and filtering the necessary info. Will look at building APIs so that it will be easier to query on-chain data in the future but feel free to use this for now.
Tech stack: 1) python 2) fxcore CLI needed. Do feel free to fork the repo and improve on it! @kenorb @FrenchXCore @ClaudioxBarros @cop4200
Alternatively, I can run the report for you guys and it will generate csv files such as those here.
Also, i have made some amendments to the EGF process and funds request. this is very important for those who want to request for funds in the future.
To protect the integrity of the ecosystem and all its users, EGF requests can only be made based on the milestone working on.
- For eg. if your project has the following specs: Milestone 1 ($3,000) & Milestone 2 ($4,000).
- The submission of your EGF proposal (on-chain) should only request for $3,000.
- Once you have completed Milestone 1, then you may submit another EGF proposal (on-chain) for $4,000
5 Likes
@FxWorldValidator Please check your (FxWorld) validator, it’s missing some blocks.
Hi Guys. The provider has some network issue.
“We have identified the reason behind the network interruption in our Duesseldorf data center, which is affecting some of our servers in Duesseldorf. The problem is at a construction site at the highway A46. During digging a cable with 288 fibers was cut, but the workers did not recognize and filled up the hole afterwards, so now they have to dig again to find the actual place of damage. No change of given ETA. Next update will be published in 1 hour.”
1 Like
We are working to solve this problem.
2 Likes
The problem is solved. Big thanks to @ClaudioxBarros !
4 Likes
Update 29-4-22
Validator rewards /status info/creation date queries
hi everyone, ive realized there was too much info in the previous csv file generations so ive filtered the unnecessary info out. just need to run python index.py and youll get the data you need.
it is really not elegant. but the code will do. You can view the repo here
New Monday Product Release Records Board (Monthly)
Great news! if you think the product pipeline had too much info, well there’s something for you!
New view of the monday board in a monthly view.
2 Likes