[proposal] fetch ERC1056 events till a specific block

Is your feature request related to a problem? Please describe. No

Describe the solution you’d like Reading / Caching of ERC1056 events should be possible from the latest block to some older block. For a cache based use-case, the solution would already store the events from the ERC1056 contracts. Whenever a user requests a DID-Doc, the resolver should sync / fetch events from the last synced block to latest block.

This makes the changeLog to have a property something like stopBlockNumber. While executing wrapDidDocument the changeLog could then possibly pull events between the latest block and specified stopBlockNumber. Thus if there is no specified stopBlockNumber, then it pull all the events from the blockchain.

Describe alternatives you’ve considered NA

Additional context NA

[mirceanis]

Yes, that’s the idea. The resolver would not care that the provider is caching events or not.

[nichonien]

The whole point of DIDs is to not require trust between organizations and their users I completely agree with you on this and have quoted it earlier as well I agree with you, the resolver should build the cache internally in order to make it more transparent and trustful.

The two main reason for having “external” cache are :

1. The caching could be a possible requirement for certain use-case or businesses, so I see it as an option.
2. If did:ethr resolver has internal caching, organisations would be bound to manage different cache for different purposes.

You understood the proposal right, we are just brainstorming for an optimal approach.