brock 🤖⚡

Adds doc-comments to lib functions. branched from #66 -- that should be merged first.

should we expose bundle & block timestamps?

1

Idea: expose three new timestamps in `/transactions` and `/blocks` * `block.witnessed_at` * `transaction.received_at` * `transaction.sent_to_miners_at` @jiangjinyuan already made an issue about block timetamps: https://github.com/flashbots/mev-blocks/issues/7 Returning the timestamp at which a...

* adds timestamps `received_at` and `sent_to_miners_at` to transaction response in `/transactions` and `/blocks` * adds timestamp `witnessed_at` in `/blocks` response * redundant fields `eao_address` and `eoa_address` in `/transactions/` response to...

- implement classes to represent structs - add `.serialize()` method for each class to replace respective munger call

Abstract offset away and let users query over limits > maxLimit

Bundle Status API

2

Presently, searchers on mev-share are unable to learn anything about their bundle after it is sent, other than the fact that it was received by the API. A bundle targeting...