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.

Sign up for GitHub

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

Jump to bottom

OP consumer: enforce timestamped pub rand at finality sig submission #69

Open

bap2pecs opened this issue Sep 25, 2024 · 0 comments

Collaborator

bap2pecs commented Sep 25, 2024

similar to https://github.com/babylonlabs-io/babylon/blob/a6f728b023145bea81d275f4e94fdbed60c36736/x/finality/keeper/msg_server.go#L105-L110 if at this height this FP does not have timestamped pub rand finality sig will be rejected

we need the same thing for the OP consumer chain

by runchao:

It's easier for OP contract -- everything in OP CW contract is timestamped by Babylon already and we can find out the epoch of each pub rand commit by querying babylon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment