Optimise log filtering for revealed events and bounty ID

[SkandaBhat]

• Create an issue on github asking the accuracy of bloom filter
• fetch data based on filter (index) in log query
• fetch events from indexed epoch
• For revealed data, verify duplicates.

[SkandaBhat]

@SamAg19 can you please add how we can fetch these data from contracts?

[Yashk767]

fetch events from indexed epoch

• Fetching revealData -
  In contracts v1, epoch is not indexed in reveal event, only stakerId is indexed.
  So logs should be filtered based on stakerId. Will implement this.

• Fetching bountyId -
  We get bountyId from slashed event logs and we already do log filtering based on indexed bounty hunter.
  It is already implemented, so no change here.

@ashish10677 @SkandaBhat

[Yashk767]

fetch events from indexed epoch

• Fetching revealData -
  In contracts v1, epoch is not indexed in reveal event, only stakerId is indexed.
  So logs should be filtered based on stakerId. Will implement this.
• Fetching bountyId -
  We get bountyId from slashed event logs and we already do log filtering based on indexed bounty hunter.
  It is already implemented, so no change here.

@ashish10677 @SkandaBhat

From the reveal event logs, we need to fetch all the revealed values and the respective influences for a epoch.
To perform this we don't need stakerId , we only need epoch, right?
On contracts stakerId is indexed, epoch is not.

I don't think we can filter reveal logs here.

@SkandaBhat @ashish10677

[SkandaBhat]

This will be implemented in v2, since support for indexed epochs is available only for v2 contracts. cc: @hrishikeshio @Yashk767 @SamAg19