It is very common across crypto api providers for endpoints to optionally include objects in the mempool, by passing a parameter. While it may be difficult to achieve, I think it makes sense to expose this capability in the /events api. Perhaps it shouldn't be done in core... but it's definitely the sort of capability we'd want from an "api as product" standpoint.
It is very common across crypto api providers for endpoints to optionally include objects in the mempool, by passing a parameter. While it may be difficult to achieve, I think it makes sense to expose this capability in the
/eventsapi. Perhaps it shouldn't be done in core... but it's definitely the sort of capability we'd want from an "api as product" standpoint.