Remove L1 related fields from L2BlockHeader

[eyusufatik]

May be done before or after #1766, does not matter.

The l1_hash and l1_height should be removed from soft confirmation and signed soft confirmation structures, because #1788 will now handle system transactions inside normal txs field of the soft confirmation.

[varun-doshi]

Please correct me if im wrong but i dont see l1_hash and l1_height in this structure:

#[derive(PartialEq, Eq, BorshDeserialize, BorshSerialize, Serialize, Deserialize)]
pub struct SignedSoftConfirmation<'txs, Tx: Clone> {
    l2_height: u64,
    hash: [u8; 32],
    prev_hash: [u8; 32],
    da_slot_height: u64,
    da_slot_hash: [u8; 32],
    da_slot_txs_commitment: [u8; 32],
    l1_fee_rate: u128,
    blobs: Cow<'txs, [Vec<u8>]>,
    txs: Cow<'txs, [Tx]>,
    signature: Vec<u8>,
    deposit_data: Vec<Vec<u8>>,
    pub_key: Vec<u8>,
    timestamp: u64,
}

[varun-doshi]

Removing the mentioned fields in the issue would mean that this function is not possible anymore. Would like to confirm if thats the intended direction?this is one of the functions that will have to be removed

citrea/crates/soft-confirmation-rule-enforcer/src/hooks.rs

Line 15 in 84e51db

fn apply_block_count_rule(

[eyusufatik]

Removing the mentioned fields in the issue would mean that this function is not possible anymore. Would like to confirm if thats the intended direction?this is one of the functions that will have to be removed

the SoftConfirmationRuleEnforcer can read the last L1 block hash from EVM and keep track through the value read