fix(kona): use configurable message expiry window in MessageGraph

[digorithm]

Summary

• Add message_expiry_window: u64 parameter to MessageGraph::derive() instead of using hardcoded MESSAGE_EXPIRY_WINDOW constant
• Load DependencySet from preimage oracle local key 8 in BootInfo
• Thread expiry window from BootInfo through SuperchainConsolidator to MessageGraph
• Add tests verifying custom expiry window behavior (expired and within-window cases)

Motivation

MessageGraph::check_single_dependency() was using the hardcoded MESSAGE_EXPIRY_WINDOW constant (7 days) instead of the configurable value from the DependencySet. The Go FPP host already serves a DependencySet (with configurable overrideMessageExpiryWindow) via the preimage oracle at local key 8, but Kona's BootInfo didn't load it. This prevented acceptance tests that configure custom expiry windows (e.g., TestInteropFaultProofs_MessageExpiry) from working correctly with Kona's fault proof program.

Closes #19636

Test plan

• All 11 existing MessageGraph tests updated to pass MESSAGE_EXPIRY_WINDOW explicitly — behavior identical to before
• New test test_derive_and_resolve_graph_message_expired_custom_window — proves custom 10s window triggers expiry
• New test test_derive_and_resolve_graph_message_not_expired_within_custom_window — proves boundary correctness
• cargo test --package kona-interop --all-features — 31 tests pass
• cargo test --package kona-proof-interop — 30 tests pass
• Default behavior preserved: DependencySet::get_message_expiry_window() falls back to MESSAGE_EXPIRY_WINDOW when no override is set

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

[digorithm]

Just a note: while working on this fix, I noticed two constants defining "default message expiry window" with different values:

Constant: MESSAGE_EXPIRY_WINDOW
Location: interop/src/constants.rs
Value: 604,800s (7 days)
Used by: DependencySet::get_message_expiry_window() fallback; matches Go's params.MessageExpiryTimeSecondsInterop
────────────────────────────────────────
Constant: DEFAULT_INTEROP_MESSAGE_EXPIRY_WINDOW
Location: genesis/src/rollup.rs
Value: 3,600s (1 hour)
Used by: Default for RollupConfig.interop_message_expiry_window; used in registry test configs; no Go equivalent

These seem to represent the same concept, but the values don't match. Feels like the 7-day value matches the ecosystem's default. The 1-hour value may be an error or an unfinished migration, correct me if I'm wrong though.

The RollupConfig.interop_message_expiry_window field may also be dead code because it's never read by any production logic. If this makes sense and we all agree, then this should be investigated and reconciled in a follow-up.

cc @ajsutton

[codecov]

Codecov Report

❌ Patch coverage is 74.73684% with 24 lines in your changes missing coverage. Please review.
✅ Project coverage is 75.8%. Comparing base (a645419) to head (effa8d4).
⚠️ Report is 5 commits behind head on develop.

Files with missing lines	Patch %	Lines
rust/kona/bin/host/src/interop/local_kv.rs	0.0%	8 Missing ⚠️
rust/kona/bin/host/src/interop/cfg.rs	0.0%	7 Missing ⚠️
rust/kona/crates/proof/proof-interop/src/boot.rs	0.0%	7 Missing ⚠️
...na/crates/proof/proof-interop/src/consolidation.rs	0.0%	1 Missing ⚠️
rust/kona/crates/protocol/interop/src/graph.rs	98.5%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #19765      +/-   ##
===========================================
+ Coverage     75.5%    75.8%    +0.3%     
===========================================
  Files          194      486     +292     
  Lines        11272    61341   +50069     
===========================================
+ Hits          8512    46547   +38035     
- Misses        2616    14794   +12178     
+ Partials       144        0     -144     

Flag	Coverage Δ
cannon-go-tests-64	?
contracts-bedrock-tests	?
unit	75.8% <74.7%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...st/kona/crates/proof/proof-interop/src/provider.rs	68.2% <100.0%> (ø)
...na/crates/proof/proof-interop/src/consolidation.rs	0.0% <0.0%> (ø)
rust/kona/crates/protocol/interop/src/graph.rs	94.3% <98.5%> (ø)
rust/kona/bin/host/src/interop/cfg.rs	29.8% <0.0%> (ø)
rust/kona/crates/proof/proof-interop/src/boot.rs	2.5% <0.0%> (ø)
rust/kona/bin/host/src/interop/local_kv.rs	0.0% <0.0%> (ø)

... and 674 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ajsutton]

Historically kona has tried to put all the config in the rollup config - this is not a great choice but I think it's why the old 1 hour timeout was around. We should just remove that - it should be 7 days by default and come from the dependency set config.

I think to get things passing you'll need to update kona-host to be able to return the dependency set - it doesn't currently have anything that handles the new DEPENDENCY_SET local key. that's causing the tests to hang forever.

Claude says:

The relevant files that would need updates:

• rust/kona/bin/host/src/interop/cfg.rs — add dependency_set field + CLI arg to InteropHost
• rust/kona/bin/host/src/interop/local_kv.rs — add key 8 handling in InteropLocalInputs

Without those changes, requesting key 8 from kona-host will fail, and BootInfo::load() will return an error at the new deserialization step.

[ajsutton]

hmm, there's a definite chance that kona-host doesn't support this yet which is why we're hitting a 2 hour timeout on tests (loading from the preimage oracle just retries forever because there is no good way out if you can't get a preimage you need).

[digorithm]

Historically kona has tried to put all the config in the rollup config - this is not a great choice but I think it's why the old 1 hour timeout was around. We should just remove that - it should be 7 days by default and come from the dependency set config.

I think to get things passing you'll need to update kona-host to be able to return the dependency set - it doesn't currently have anything that handles the new DEPENDENCY_SET local key. that's causing the tests to hang forever.

Claude says:

The relevant files that would need updates:

• rust/kona/bin/host/src/interop/cfg.rs — add dependency_set field + CLI arg to InteropHost
• rust/kona/bin/host/src/interop/local_kv.rs — add key 8 handling in InteropLocalInputs

Without those changes, requesting key 8 from kona-host will fail, and BootInfo::load() will return an error at the new deserialization step.

Oh, that makes sense. Let me look into that.

[digorithm]

@ajsutton Added your suggestion, but I'll keep the removal of the 1-hour hardcoded config in a follow-up PR. Removing DEFAULT_INTEROP_MESSAGE_EXPIRY_WINDOW and the RollupConfig.interop_message_expiry_window field touches the genesis/rollup config types, which could affect serialization compatibility and registry test configs. That's a different scope from this fix, imo (should be a short and quick separate PR).

[wiz-inc-a178a98b5d]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	1  1  2
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	-
Software Management Findings	-
Total	1  1  2

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.