0

I'm invoking a POST API that sends a transaction to the smart contract. To ensure the durability of the transaction, I'm using a nonce account. On creating the transaction for the SC, I've set the recentBlockhash equal to the nonce of the nonce account to ensure the durability of the transaction.

On Firefox, everything is working fine, and I'm using Phantom Wallet version '23.5.0.1'.

However, on Chrome, when I invoke the same API, Phantom Wallet sends a warning that the 'transaction expired.It is due to the change in the order of the instructions in transaction object, in Firefox the ordering is {nonce account, main instruction, and two system instructions}, whereas in Chrome the ordering changes.' If I ignore warning and proceed anyway, the API crashes, indicating that the 'Blockhash not found'. Here Phantom Wallet version '23.12.0'

I would like to understand why this behavior differs between the two browsers.

1
  • It sounds like something might have changed between those releases -- try reaching out directly to phantom dev support to see what they advise.
    – Jon C
    Sep 13, 2023 at 11:41

1 Answer 1

0

Apologies for the delay in response. If this difference still exists, please post on the Phantom developer discussions available here.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.