You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The focus contract address alpha feature is presumably intended to simplify client filtering behavior: only events corresponding to a particular Move package are allowed through the top-level worker process
However, the underlying implementation appears to filter based on the public entry function rather than by the event address. E.g. if a project composes on top of another and invokes the underlying package via a wrapped function call, then the wrapping package's events (which are also the wrapped package's events) get removed
Instead, it is suggested that filtration rely on the address of emitted event types, or alternatively, the focus_contract_addresses be renamed to something like entry_function_address with an additional event_type_address
cc @banool @CapCap @CRBl69
Description
The focus contract address alpha feature is presumably intended to simplify client filtering behavior: only events corresponding to a particular Move package are allowed through the top-level worker process
However, the underlying implementation appears to filter based on the public entry function rather than by the event address. E.g. if a project composes on top of another and invokes the underlying package via a wrapped function call, then the wrapping package's events (which are also the wrapped package's events) get removed
Instead, it is suggested that filtration rely on the address of emitted event types, or alternatively, the
focus_contract_addresses
be renamed to something likeentry_function_address
with an additionalevent_type_address
Repro
The text was updated successfully, but these errors were encountered: