-
Notifications
You must be signed in to change notification settings - Fork 18
Issues: babylonchain/finality-provider
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
flag provided but not defined: -L/opt/homebrew/opt/openssl@3/lib
#363
opened May 31, 2024 by
dflottery
In-memory Merkle tree and proof generation for public randomness commitments
#362
opened May 30, 2024 by
SebastianElvis
CI should check running
proto-gen
result in no uncommitted changes
#353
opened May 23, 2024 by
bap2pecs
need better error msg when e2e fails due to
babylond
process is not killed in previous runs
#345
opened May 22, 2024 by
bap2pecs
Finality provider instance fails to start if finalized epoch < registered epoch
#327
opened May 16, 2024 by
gusin13
Account sequence mismatch errors after chain halt and full mempool
bug
Something isn't working
#320
opened May 13, 2024 by
KonradStaniec
Lack of filtering of different chain id,fpcli list-finality-providers show confusing info
#293
opened Apr 22, 2024 by
whyrulike
Add Refactoring, improve performance an reliability
fpcli edit-finality-provider
to edit fp description
optimization
#274
opened Mar 21, 2024 by
gusin13
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.