We updated the Starknet streams to index and serve reverted transactions. By default, the streams will not include these transaction and developers needs to explicitly request them.

There are three ways to receive reverted transactions:

• from transactions, by setting the includeReverted option to true. In this case, the transactions data will include all requested transactions, including reverted ones.
• from events, by setting the includeReverted option to true. In this case, the events data will include events from reverted transactions (usually only the fees Transfer event).
• from messages, by setting the includeReverted option to true. This works similarly to events, but for L2 to L1 messages.