Integrate L2 block tags with derive block operations #879
Description
Background
Currently, derive block operations and L2 block tags (e.g., safe, finalized) are handled separately. We want to unify them so that derived blocks can be properly tagged based on their derivation status.
Goals
- Tag L2 blocks with appropriate status during derivation:
- unsafe - block produced but not yet derived from L1
- safe - block derived from L1 data
- finalized - block derived from finalized L1 data
- Expose block tags via RPC for downstream consumers
Benefits
- Clearer block status for bridges and external services
- Consistent with Optimism's block tag semantics
- Enables safer cross-chain operations by distinguishing derivation states