-
Notifications
You must be signed in to change notification settings - Fork 20
Insights: babylonlabs-io/finality-provider
Overview
Could not load contribution data
Please try again later
1 Release published by 1 person
-
v0.14.3 Release v0.14.3
published
Jan 7, 2025
9 Pull requests merged by 3 people
-
fix: Broken links on operation guide
#272 merged
Jan 7, 2025 -
feat: export pop command
#262 merged
Jan 7, 2025 -
[backport] Update Changelog (#267)
#268 merged
Jan 7, 2025 -
Update Changelog
#267 merged
Jan 7, 2025 -
chore: change default config value
#266 merged
Jan 7, 2025 -
[backport] chore: Allow running of jailed fp (#260)
#265 merged
Jan 6, 2025 -
chore: Allow running of jailed fp
#260 merged
Jan 6, 2025 -
[backport] chore: Refactor to start from the last finalized height (#257)
#261 merged
Jan 3, 2025 -
chore: Refactor to start from the last finalized height
#257 merged
Jan 3, 2025
1 Pull request opened by 1 person
-
chore: backport #262 to v0.4.x and use old CLI
#271 opened
Jan 7, 2025
3 Issues closed by 1 person
-
Check default configs to be reasonable
#263 closed
Jan 7, 2025 -
FP should be able to start if jailed
#259 closed
Jan 6, 2025 -
Slow catch-up after long downtime
#253 closed
Jan 3, 2025
4 Issues opened by 2 people
-
Flacky test: TestFinalityProviderEditCmd
#270 opened
Jan 7, 2025 -
Flacky test: FuzzChainPoller_SkipHeight
#269 opened
Jan 7, 2025 -
Improve poller to poll batch of blocks at once
#264 opened
Jan 6, 2025 -
FP daemon startup fails if FP is jailed
#258 opened
Jan 2, 2025
1 Unresolved conversation
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Finality Provider should vote on latest block after unjail
#254 commented on
Jan 6, 2025 • 0 new comments