56 expiry time issue for certification

[ninokeldishvili]

No description provided.

[Siddharth2207]

• From my debugging session, for arbitrum sepolia network, the issue isn't expiry time, but the transaction reverts with FutureReferenceBlock error .
• I tried to reproduce the revert transaction in foundry fork environment, replaying it with the same calldata that I received from the webapp, and the transaction succeed. So as far as I can tell there is no issue with the contract.
• Here is the calldata I replayed at block number 81155171.

{
data: "0x86eb6bb80000000000000000000000000000000000000000000000000000000066f84b270000000000000000000000000000000000000000000000000000000004d654630000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000140000000000000000000000000000000000000000000000000000000000000000"
from: "0x669845c29D9B1A64FFF66a55aA13EB4adB889a88"
to: "0xadd2dbd7f89c7521b7c88d406d2e74ea3091d927"
}

where to address is the OffchainAssetReceiptVault instance.

[thedavidmeister]

i'm going to close this because the expiry time doesn't fail locally, as @ninokeldishvili and @Siddharth2207 pointed out

it's likely due to using the incorrect block times from the RPC for L2

https://docs.arbitrum.io/build-decentralized-apps/arbitrum-vs-ethereum/block-numbers-and-time#block-numbers-arbitrum-vs-ethereum