3

we've been seeing inconsistent errors when we broadcast to our full node. We use the latest block as our branch when broadcasting but still encounter this:

Operation ooAZXxx9q5f5Kn4vpCuGG8EdTADL29gYbH8sjWw6jJ2VLErJ9B5 is branched on a block BLrjupXkEqWF2r282WJTuTXw4JwekFpTA9r1mAfn34LjVbXatJt which is too old - Hash: ooAZXxx9q5f5Kn4vpCuGG8EdTADL29gYbH8sjWw6jJ2VLErJ9B5

We've noticed that sometimes this means that transaction will never make it on chain, but there are other instances where it does make it on chain when we see this response.

Any suggestions on how to prevent this in the first place since we don't truly know what to mark this transaction (failed or succeeded) when we see this error which is giving us inconsistencies in our transaction statuses.

6
  • It's recommended not to use the latest block (aka head candidate) hash as operation branch, because of reorgs. I guess that Tezos node does not make the difference if the branch hash is outdated (i.e. >120 levels old) or orphaned (terminal chain branch) thus the message might be misleading. Jun 4 at 20:14
  • Got it @MichaelZaikin. Do you have a recommendation of how many blocks behind I should be grabbing the hash from?
    – user5867
    Jun 5 at 0:41
  • 1
    People used 55 when the operation TTL was 60 because stuck operations could not be replaced without restarting the node. With Tenderbake, three blocks behind should be enough since now the block finality is two confirmations. mainnet.visualtez.com/chains/main/blocks/head~3 Jun 5 at 6:55
  • @RodrigoQuelhas so actually tried using 5 block behind chain and still got the same error. It’s not consistent when it happens either.
    – user5867
    Jun 6 at 0:50
  • 1
    Thanks @RodrigoQuelhas, this helped
    – user5867
    Jun 15 at 18:50

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.