By default, we don't expose anything to Conduit.

Some transactions have complex/weird/sensitive/not-good-for-API-users details, and if we exposed them by default we might end up in trouble (maybe users trying to use them and complaining that they're impossible to work with; maybe users complaining that we broke compatibility if we then fix it; maybe actual security problems), so we err on the side of caution and require each transaction have an explicit implementation.

In this case (and other simple cases) there's an obviously reasonable way to represent the transaction, but I just delete / don't implement these methods a lot of the time if there's any ambiguity.

Usually, this only impacts webhooks trying to do something with the event.