Inexistant Transaction hash created from wallet [BUG]

[alexhaloETH]

On all of our instance of BlobArena we get the controller releasing incorrect/non existing transaction. there for

==================

Evidence

https://starkscan.co/search/0x5b63cdddaae6e95e8111ca1083818346685bd58fefc16fd68a2f87c24a03908

==================

What we did:
tried 3 different controller accounts
tried to log out and log back in
clean cache
tried our production - staging - development wesbites

all resulted into the same issue

==================

The reason why I think this issue is related to the controller is because I have tried 3 braavos accounts and they all work without giving out wrong transactions

==================

we are currently using the latest rpc (0.9) on the controller setup
The issue highlighted above is intermittent, sometimes it goes away for a couple of minutes sometimes it comes back, if it does comeback I make sure to straight away test he braavos wallet too in case I was using the braavos wallet at a time where the issue was chain related.

[tarrencev]

@alexhaloETH are you able to share the raw json rpc call? Controller does not generate transaction hashes, it only passes them back from the RPC which just returns the transaction hash the sequencer produces, so the network is receiving the transaction and then dropping it for some reason. We've seen a similar behavior for transactions that exceed resource bounds (for example, state diff size). Unfortunately it is hard for us to debug this one our side, since as you mentioned there is no trace of the transaction existing. If we can find the transaction payload for a failed transaction we can try debug it with Starkware

[alexhaloETH]

Its quite the intermittent issue, so i am unable to get the data you requested, for now i will close this and will reopen this once the issue comes back and then hopefully i can get you the right data.