Hi @OscBacon I've added this issue to our backlog and we'll keep you posted! Thanks for bringing it to our attention.

Hey @fainashalts any chance you could prioritize this more please?
My project is part of the superchain incubator and this is forcing us for now to stay on three anvil chains since we can't test subscribing to events.
Since supersim is using anvil under the hood it should be a matter of properly exposing both http and ws RPCs

@OscBacon yes sorry I wasn't more clear! our team will talk about this later today and figure out priority. 😄 backlog is just a pit stop. thank you for clarifying the need, very helpful for our discussion.

@OscBacon I believe that websockets should work for all the supersim chains. Do you mind sending me some steps I can follow to reproduce this issue?

Hey @tremarkley for sure!

supersim
# In another shell
wscat -c localhost:9546

wscat is a nifty too to send out requests to a WS server, like cat
Install with npm i -g wscat

For comparison, run wscat -c localhost:8545 to connect to the L1.

As you will see, expected behavior:

wscat -c localhost:8545
Connected (press CTRL+C to quit)

but with the L2:

wscat -c localhost:9546
error: Unexpected server response: 400

@OscBacon this fix is included on supersim version 0.1.0-alpha.48