Skip to content

Actions: Hydra-Chain/hydragon-core-contracts

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
493 workflow runs
493 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

76 150 validator spot limit Solidity CI #68: Pull request #19 synchronize by SamBorisov
May 27, 2024 09:48 1m 19s 76-150-validator-spot-limit
76-150-validator-spot-limit
May 27, 2024 09:48 1m 19s
76 150 validator spot limit Solidity CI #67: Pull request #19 synchronize by SamBorisov
May 22, 2024 09:09 57s 76-150-validator-spot-limit
76-150-validator-spot-limit
May 22, 2024 09:09 57s
76 150 validator spot limit Solidity CI #66: Pull request #19 opened by SamBorisov
May 22, 2024 08:44 1m 16s 76-150-validator-spot-limit
76-150-validator-spot-limit
May 22, 2024 08:44 1m 16s
new ban mechanism based on validator participation (#17) Solidity CI #65: Commit a7b6b39 pushed by Vitomir2
May 22, 2024 07:03 1m 14s main
main
May 22, 2024 07:03 1m 14s
new ban mechanism based on validator participation Solidity CI #64: Pull request #17 synchronize by Vitomir2
May 21, 2024 10:40 1m 6s 125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
May 21, 2024 10:40 1m 6s
new ban mechanism based on validator participation Solidity CI #63: Pull request #17 synchronize by R-Santev
May 21, 2024 07:37 1m 0s 125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
May 21, 2024 07:37 1m 0s
new ban mechanism based on validator participation Solidity CI #62: Pull request #17 synchronize by Vitomir2
May 20, 2024 15:45 59s 125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
May 20, 2024 15:45 59s
add modifier when needed + tests (#18) Solidity CI #61: Commit d6b5170 pushed by SamBorisov
May 17, 2024 10:41 1m 2s main
main
May 17, 2024 10:41 1m 2s
add modifier when needed + tests Solidity CI #60: Pull request #18 synchronize by SamBorisov
May 17, 2024 09:30 1m 3s 133-reward-pool-functions-are-not-protected-by-validator-set
133-reward-pool-functions-are-not-protected-by-validator-set
May 17, 2024 09:30 1m 3s
add modifier when needed + tests Solidity CI #59: Pull request #18 opened by SamBorisov
May 16, 2024 14:56 1m 19s 133-reward-pool-functions-are-not-protected-by-validator-set
133-reward-pool-functions-are-not-protected-by-validator-set
May 16, 2024 14:56 1m 19s
new ban mechanism based on validator participation Solidity CI #58: Pull request #17 synchronize by Vitomir2
May 16, 2024 12:56 1m 15s 125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
May 16, 2024 12:56 1m 15s
new ban mechanism based on validator participation Solidity CI #57: Pull request #17 opened by Vitomir2
May 16, 2024 12:51 1m 14s 125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
125-implement-a-mechanism-to-measure-the-participation-of-every-validator-based-on-uptime-data-provided-to-the-rewardpool-so-a-validator-can-be-banned-in-case-offline-for-more-than-72-hours
May 16, 2024 12:51 1m 14s
use address parameters instead of msg.sender (#15) Solidity CI #56: Commit 181359c pushed by Vitomir2
May 14, 2024 07:52 1m 6s main
main
May 14, 2024 07:52 1m 6s
new ban validator functionality (#12) Solidity CI #55: Commit de4d60b pushed by Vitomir2
May 14, 2024 07:51 1m 15s main
main
May 14, 2024 07:51 1m 15s
new ban validator functionality Solidity CI #54: Pull request #12 synchronize by Vitomir2
May 14, 2024 07:22 1m 14s 113-dao-manual-ban-until-block-x
113-dao-manual-ban-until-block-x
May 14, 2024 07:22 1m 14s
use address parameters instead of msg.sender Solidity CI #53: Pull request #15 opened by Vitomir2
May 14, 2024 06:38 1m 22s 14-found-vulnerabilities-in-some-requirements-in-balancestatesol-and-liquidstakingsol
14-found-vulnerabilities-in-some-requirements-in-balancestatesol-and-liquidstakingsol
May 14, 2024 06:38 1m 22s
new ban validator functionality Solidity CI #52: Pull request #12 synchronize by Vitomir2
May 13, 2024 12:39 1m 13s 113-dao-manual-ban-until-block-x
113-dao-manual-ban-until-block-x
May 13, 2024 12:39 1m 13s
new ban validator functionality Solidity CI #51: Pull request #12 synchronize by Vitomir2
May 10, 2024 12:47 1m 11s 113-dao-manual-ban-until-block-x
113-dao-manual-ban-until-block-x
May 10, 2024 12:47 1m 11s
124 add functions in the contracts that allow minstake and mindelegat… Solidity CI #50: Commit 5420121 pushed by SamBorisov
May 10, 2024 08:28 1m 11s main
main
May 10, 2024 08:28 1m 11s
124 add functions in the contracts that allow minstake and mindelegation to be changeable by the governor Solidity CI #49: Pull request #11 synchronize by SamBorisov
May 10, 2024 08:26 1m 21s 124-add-functions-in-the-contracts-that-allow-minstake-and-mindelegation-to-be-changeable-by-the-governor
124-add-functions-in-the-contracts-that-allow-minstake-and-mindelegation-to-be-changeable-by-the-governor
May 10, 2024 08:26 1m 21s
124 add functions in the contracts that allow minstake and mindelegation to be changeable by the governor Solidity CI #48: Pull request #11 synchronize by SamBorisov
May 10, 2024 08:20 1m 22s 124-add-functions-in-the-contracts-that-allow-minstake-and-mindelegation-to-be-changeable-by-the-governor
124-add-functions-in-the-contracts-that-allow-minstake-and-mindelegation-to-be-changeable-by-the-governor
May 10, 2024 08:20 1m 22s
124 add functions in the contracts that allow minstake and mindelegation to be changeable by the governor Solidity CI #47: Pull request #11 synchronize by SamBorisov
May 9, 2024 17:16 1m 16s 124-add-functions-in-the-contracts-that-allow-minstake-and-mindelegation-to-be-changeable-by-the-governor
124-add-functions-in-the-contracts-that-allow-minstake-and-mindelegation-to-be-changeable-by-the-governor
May 9, 2024 17:16 1m 16s
78 7 day cooldown period on all withdrawals (#10) Solidity CI #46: Commit 5c1c312 pushed by SamBorisov
May 9, 2024 14:48 1m 14s main
main
May 9, 2024 14:48 1m 14s
78 7 day cooldown period on all withdrawals Solidity CI #45: Pull request #10 synchronize by SamBorisov
May 9, 2024 14:19 1m 16s 78-7-day-cooldown-period-on-all-withdrawals
78-7-day-cooldown-period-on-all-withdrawals
May 9, 2024 14:19 1m 16s
78 7 day cooldown period on all withdrawals Solidity CI #44: Pull request #10 synchronize by SamBorisov
May 9, 2024 13:45 1m 15s 78-7-day-cooldown-period-on-all-withdrawals
78-7-day-cooldown-period-on-all-withdrawals
May 9, 2024 13:45 1m 15s
ProTip! You can narrow down the results and go further in time using created:<2024-05-09 or the other filters available.