-
Notifications
You must be signed in to change notification settings - Fork 662
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
Updates blst to version 0.3.12. Closes #3079 #3080
base: master
Are you sure you want to change the base?
Conversation
I think you'll need to run:
to fix the CI issue |
Thank you. Done. |
I think we're going to need to look into this a bit more closely... (this library feels like a bit of a wildcard). So this might take a little bit to merge. But thank you for opening this. |
This PR has become stale because it has been open for 30 days with no activity. Adding the |
I want to inform that I have been testing the port of avalanchego (and other ava-labs tools) to OpenBSD/adJ, that uses the library blst 0.3.12 on a system that is validating in testnet fuji. Three days ago I did validation for one day with succes, and yesterday I started a validation for one month. Transaction: https://subnets-test.avax.network/p-chain/tx/keQmoqe86iVJw2mf1uxrM6GuxBTwPJdoB2BKc9wFyofcNezTP How it looks in test.core.app: I made a (long) video showing how to install OpenBSD/adJ 7.5 in a virtual machine and how to start an avalanchego node with the ported tools: https://www.youtube.com/watch?v=vLL4V66ymP4 |
The goal of my test (running a validator in testnet 30 days) is to confirm if updating to blst version 0.3.12 and using OpenBSD/adJ doesn´t decrease stability or functionality, but my current lack of experience operating a validator is not helping. Several days ago I solved an issue with memory (increasing memory limit solved the problem) and few days ago the machine blocked (it could have relation with low disk space). Today I moved the validator to a different machine running OpenBSD/adJ 7.5 and with more disk space, since the new machine is behind a firewall I had to "discover" after long time the option Also today I discovered https://subnets-test.avax.network/validators/NodeID-6d4VNVPxnk8g4NHfFR2ombAz1W23454pw?validatorTab=health_check and how useful it is to diagnose some problems with a validator. Since I didn´t know several details needed to operate a validator the performance of my node doesn't look good: To improve the situation from the configuration/operation points of view is there a document that presents for example (1) need to use |
Why this should be merged
How this works
With updated sources I just ran:
How this was tested
Tested with avalanchego 1.11.10 ported to OpenBSD/adJ 7.5, running a node validating in testnet (see below comment of 31st July).
Details about the port of avalanchego 1.11.10 to OpenBSD/adJ that includes updating blst to version 0.3.12 at https://github.com/vtamara/avalanchego/wiki/Porting-avalanchego-1.11.10-to-OpenBSD-adJ-7.5
I also proposed and tested updating blst to vesion 0.3.12 in coreth, subnet-evm, avalanche-network-runner, and proposed updating in avalanche-cli.