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 default strategy is:
For each v1 event below, create a v2 event with a different name (Event suffix stripped) and emit a v2 event together with each v1 event emitting.
@bowenyang007@lightmark I don't foresee this immediately affecting Econia indexing, because Econia v4 (mainnet release) relies on custom v1 events and writesets only - there is no dependency on framework events
Of course the performance enhancement of v2 events is understandable, but the Econia package is also 63k and upgrading events will probably not happen. Rather I'd expect future releases (e.g. protocol rebuilds) will simply use v2 events going forward
As I understand it, v1 and v2 event indexing will be both be supported but protocols that opt for v2 style will see superior performance - is this correct? Or will v1 events be incompatibly deprecated?
v1 and v2 event indexing will be both be supported.
But the framework v1 emitting will be removed once most people in the community switch to tracking v2 only.
thepomeranian
changed the title
[AIP-X][Discussion] Refactor Aptos Framework Events with Module Events
[AIP-71][Discussion] Refactor Aptos Framework Events with Module Events
Mar 12, 2024
AIP Discussion
The default strategy is:
For each v1 event below, create a v2 event with a different name (
Event
suffix stripped) and emit a v2 event together with each v1 event emitting.Read more about it here: Link to AIP
The text was updated successfully, but these errors were encountered: