EPIC: OP finality-provider

[bap2pecs]

@bap2pecs cloned issue babylonchain/pm-integration#3 on 2024-06-20:

• OP: QueryBlocks babylonchain/finality-provider#497
• fix flaky test TestOpMultipleFinalityProviders (see chore: use cosmos blocks in consumer query babylonchain/finality-provider#509)
• OP: QueryLatestFinalizedBlock and QueryIsBlockFinalized babylonchain/finality-provider#498
• OP: QueryFinalityProviderHasPower babylonchain/finality-provider#496
• OP: QueryActivatedHeight redesign babylonchain/finality-provider#432
• OP: fix fast sync segfault (flaky test) babylonchain/finality-provider#508
• OP: fix flaky data race in e2e tests babylonchain/finality-provider#528
• OP: investigate fast sync related segfault in e2e tests babylonchain/finality-provider#529
• fpd CLI should support OP consumer chain finality-provider#72
• (low-pri) use websocket instead of http RPC calls when polling L2 block header
• rename NewClientController to NewBabylonController as well as a few other names

[bap2pecs]

@SebastianElvis commented on 2024-06-26:

QueryFinalityProviderVotingPower sounds good to me

The proposed QueryActivatedHeight might not work as the start_height is not necessarily the height that BTC delegation becomes active. To become active, it needs to satisfy 1) the staking tx is k-deep in Bitcoin, i.e., start_height + k and 2) it receives a quorum number of covenant committee signatures

[bap2pecs]

@bap2pecs commented on 2024-06-30:

note that for QueryFinalityProviderVotingPower, one problem is if we always return 1, it will cause issue

2024-06-29T17:15:40.891-0400	FATAL	service/fp_manager.go:110	terminating the finality-provider instance due to critical error	{"pk": "12b1058e00115ea41f28582db7fb684c03113933c630ffbfb5baea91beec6cc1", "error": "reached max failed cycles with err: failed to get inclusion proof of public randomness 983078c40dea8dfb765005d207092437f867bc881e1e45220cf15bfff2b056cd for FP 12b1058e00115ea41f28582db7fb684c03113933c630ffbfb5baea91beec6cc1 for block 2: public randomness proof not found"}

github.com/babylonchain/finality-provider/finality-provider/service.(*FinalityProviderManager).monitorCriticalErr

	/Users/zidong/Documents/Projects/babylon-finality-provider/finality-provider/service/fp_manager.go:110

FAIL	github.com/babylonchain/finality-provider/itest/opstackl2	58.684s

FAIL

due to submission loop trying to submit sig for a height missing PR. so we added https://github.com/babylonchain/babylon-contract/pull/196 and used it in QueryFinalityProviderVotingPower (see babylonchain/finality-provider#447)