EPIC: OP finality contract

[bap2pecs]

• replace query_grpc() and query_raw() once query_grpc() is released by CosmWasm STD
• OP consumer: enforce timestamped pub rand at finality sig submission babylon-contract#69
• ensure there is no gap at randomness submission
• ensure the finality provider is not slashed at EOTS submission
• ensure the finality provider has voting power / activated at EOTS submission
• allow configuring min_pub_rand
• babylonchain/babylon-contract#194
• babylonchain/babylon-contract#175
• babylonchain/babylon-contract#157
• babylonchain/babylon-contract#145
• babylonchain/babylon-contract#209
• babylonchain/babylon-contract#186
• babylonchain/babylon-contract#203
• babylonchain/babylon-contract#152
• babylonchain/babylon-contract#208

[bap2pecs]

@bap2pecs commented on 2024-07-09:

https://github.com/babylonchain/babylon-contract/blob/main/contracts/btc-staking/src/finality.rs#L59-L67

@maurolacy it seems we allow gap at randomness submission. should we enforce consecutive randomness in the storage? is it b/c we allow FP to go offline for an extended period of time so there is no need to enforce catching up?

[bap2pecs]

@SebastianElvis i don't have access to the old repo. but I just kept them for reference here. feel free to remove them