Make allocation and transfer instruction contexts cacheable/prefetchable #3593
Description
Motivation
Avoid extra workflow latency due to requiring
- executor observing the allocation contract-id
- executor querying the allocation context from the registry
- registry backend waiting to observe the allocation contract-id (and related contracts)
- registry backend responding with the choice context
Problems to consider
- how to enable caching
- how to communicate that a context is cacheable
- how to enable callers to deal with cache invalidation due to the context referencing stale contracts
- whether/how to update CIP-56
- how to roll-out the change
Discussion
FYI: @bame-da thanks for reporting this.
@waynecollier-da : I'm adding it to the token standard improvements. Would you mind prioritizing when you see that the time is ready?