Zeeshan Akram

> Process extrinsics rather than events, or alternatively, work back from event to extrinsic to recover metadata field (probably way easier) I think its possible to work back and extract...

I had a sneak peek at the Hydra for implementing the feature for extracting extrinsics payload parameters provided the event. And the good news is that Hydra already has support...

So seems like there are more scenarios for the `batch` calls, and the solution proposed here does not encompass those scenarios. e.g., there could have been consecutive batch calls in...

> 1. It has 0 impact on downstream dependencies, like Atlas, QN, CLI, tests... > 2. We truly believe this can be shipped without augmenting our QA plans 1. This...

Here is a feature specification highlighting all the required QN, metaprotocol & protobuf changes ## QN Changes Following schema changes would be added to query-node's [storage](https://github.com/zeeshanakram3/joystream/blob/2a94e3bb640fac13f16f005531f28f7d27fa127e/query-node/schemas/storage.graphql) related entities ```.gql ###...

> Pick an s3 client package and test against multiple cloud providers > Do we want to support more than one object store at a time? @mnaamani there is a...

# Proposal TBD

Certainly, custom resolvers(APIs) would save us from hacky solutions, but now we have workarounds for things where we felt the need for something not generated by templated hydra resolvers. So...

> Market cap could be added CRT entity and updated by the mappings. Sure, having derived `marketCap` property seems like good idea, it would avoid hassle of doing client side...

Integration tests will be added in #4815