Classifies a tokenized-deposit transfer's finality risk from supplied L2-batch and L1-finalization state: soft (unsubmitted), batched (submitted to L1, not yet final), or l1_final. Returns reorg-window risk and a safe-to-release verdict against a corridor policy cutoff.
Generic Optimistic/Batched L2 ModelDraft-Pinned, Not Linea-ConfirmedClassifies Supplied State Only
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
What this does NOT prove
This kernel never observes a chain or an RPC endpoint. Its three-tier ranking is a generic optimistic/batched L2-to-L1 model; Linea-specific published finality windows were not found at SLI-WAVE-1's STEP-0 re-verify (2026-07-13) and this classification is draft-pinned, not a claim of conformance to Linea's own published finality guarantees.
–
Finality Tier
–
Reorg Risk
Rationale
⚠ DECISION-SUPPORT DRAFT. Draft-pinned classification; does not observe the chain.
OpenChainGraph v0.4 artifact · execution_hash:
–
See also
This check reports three states. It cannot express the position where a validity proof has been accepted but the settlement-layer block carrying it is not yet finalised, which is a real and distinct state because validity-proof finality is two gates rather than one timer. ART-492 Settlement Finality Classifier is vendor neutral, takes the window and finality parameters as inputs, and reports that in-between position as proven_unfinalized. This page stays live and unchanged, so receipts it has already produced remain verifiable.
Ask your agent
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `check_linea_l2_finality_window`. Task: Classify a tokenized-deposit transfer’s finality risk given L2-batch to L1-settlement timing: soft (unsubmitted), batched (submitted, not yet final), or l1_final tier, reorg-window risk, and a safe-to-release verdict against a corridor policy cutoff.
Call it with arguments: {"policy_parameters":{"l2_block":1234567,"batch_submission_status":"submitted","l1_finalization_status":"finalized","corridor_cutoff":"batched","asset_type":"tokenized_deposit"}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string, or re-run the in-page WebMCP tool `check_linea_l2_finality_window`.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-290-check-linea-l2-finality-window.html#p=v1.H4sIAAAAAAAA_wGcAGP_eyJsMl9ibG9jayI6MTIzNDU2NywiYmF0Y2hfc3VibWlzc2lvbl9zdGF0dXMiOiJzdWJtaXR0ZWQiLCJsMV9maW5hbGl6YXRpb25fc3RhdHVzIjoiZmluYWxpemVkIiwiY29ycmlkb3JfY3V0b2ZmIjoiYmF0Y2hlZCIsImFzc2V0X3R5cGUiOiJ0b2tlbml6ZWRfZGVwb3NpdCJ92akn3pwAAAA