-
Notifications
You must be signed in to change notification settings - Fork 44
Pyrmont scenario testing #59
Comments
Status update on some of the tasks:
|
Block sync from genesis works as expected for all clients - some are not done yet but are close (I see no reason it would fail now). Checkpoint Sync works as expected on Teku and Lodestar, both pre and post altair. The relevant issues have been marked as done. |
Stress test with a period of non-finality was successful. > 66% of validators are back online now and the chain has started to finalize again as expected. |
|
Validator deposit performed using the standard tools available to the public (via launchpad website). Validator deposit was successful and the activation process can be seen here: https://pyrmont.beaconcha.in/validator/0xb27b062330beea9679d2b87aa21e3de17604c76b99da43912aab32c233c0162c9914c03af4df436ab61db9ee227ac810#deposits |
Successfully validated and published voluntary exit for validator 0x800bdd6914ff67ee008931dfe6eefa0f50a780a3d9aa805896b2f18468ada69d4105e1699cf880ce4bbab72cd5465aeb Current epoch: 67240, Exit epoch: 67245, Withdrawable epoch: 67501 |
Validator exit was successful. |
Prymont NTP related test results can be found here: https://hackmd.io/@cyWB-JD1SlKJ7C6tELEC6Q/HkyKNa2MK |
Attestor slashing (double) was performed for this validator with the data:
Attestor slashing (surround) was performed for this validator with the data:
Slashing for both validators was successful and the behaviour seen so far has been expected. |
Now that the Altair fork is complete and stable on Pyrmont, we are inducing a number of behaviors on the soon-to-be-deprecated Pyrmont.
The following list are the low hanging fruit. Feel free to do additional tests.
Original doc
The text was updated successfully, but these errors were encountered: