Andrey Dolgolev

Okay finally: The problem of stream_boundary is that stream_boundary is not depend on data wich it requested.

> I think is must to add blockchain selector as well. And I assume for some contracts it might be useful to actually query for polygon AND/OR ethereum simultaneously @peersky...

Extended version: ```json { "output_statment": [ { "block_timestamp": { "type": "timestamp" } }, { "args": { "name": "to" } }, { "args": { "name": "from" } } ], "filter_block":{ "condition":...

Extend are little logic of map because it require more be the same keys ```json [ { "$match": { "data.args.from": "0x0000000000000000000000000000000000000000", "data.type": "event", "data.name": "Transfer", "data.address": "", "data.args.tokenId": { "$cast":...

We apply new field on dashboard resource: counted_events ```json { "id": "9a14bb46-215b-4878-ba4a-01b15489ed88", "resource_data": { "name": "Crypto Elephants secondary market activity", "subscriptions": [ { "subscription_id": "0869942d-3cd2-4ea5-9424-d0f3e1653173", "generic": [ {"name": "transactions_in"}, {"name":...

Change "subscriptions": [ frontend | "dashboard_subscriptions" backend to "subscription_settings": [

All store on s3. s3://events-data//data.json Json object with all data what we can set: ```json { method_1: { day: count: }, ....... volume_in: volume_out: } ```

One moment about: inputs: `"inputs"` -> `"input_schema"` `"value"` -> `"inputs"` outputs: `"output"` -> `"output_schema"` `"value"` -> `"output"` I agree rename `value` but `"output"` reserved, in genral now for generate from...

> I don't like how complex tasks are nested like this - what if we want to use output of `totalSupply` in multiple steps? I think it's best to associate...

Good idea add ability to set BUGOUT_TOKEN for automaticly aprrove query. It will help for internal usages.