You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are "initializing" the BitcoinLightClient contract with a number and hash given by the sequencer, this is fine for full nodes, as they pull the blocks themselves and supply the hash to the STF themselves. But on the batch proof this is a problem as bitcoin block headers does not include a block number.
One simple solution is to hard code the height and hash in Citrea genesis just like #1151.
There might be better solutions so leaving that as decision needed for now.
The text was updated successfully, but these errors were encountered:
This is sort of a research question.
Right now we are "initializing" the BitcoinLightClient contract with a number and hash given by the sequencer, this is fine for full nodes, as they pull the blocks themselves and supply the hash to the STF themselves. But on the batch proof this is a problem as bitcoin block headers does not include a block number.
One simple solution is to hard code the height and hash in Citrea genesis just like #1151.
There might be better solutions so leaving that as decision needed for now.
The text was updated successfully, but these errors were encountered: