Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide stable ids for indexing of logs #5908

Open
IGI-111 opened this issue Apr 23, 2024 · 0 comments
Open

Provide stable ids for indexing of logs #5908

IGI-111 opened this issue Apr 23, 2024 · 0 comments
Labels
ABI Everything to do the ABI, especially the JSON representation compiler: frontend Everything to do with type checking, control flow analysis, and everything between parsing and IRgen compiler: parser Everything to do with the parser language feature Core language features visible to end users

Comments

@IGI-111
Copy link
Contributor

IGI-111 commented Apr 23, 2024

Indexers need a stable id for log receipts to continue working through contract updates. We need to provide a mechanism for the user to generate such stable ids.

At the minimum we should provide an annotation the user can add to a logged type that populates the ABI spec, but more likely it should be a trait that has to be implemented for any logged type.

@IGI-111 IGI-111 added language feature Core language features visible to end users ABI Everything to do the ABI, especially the JSON representation compiler: frontend Everything to do with type checking, control flow analysis, and everything between parsing and IRgen compiler: parser Everything to do with the parser labels Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ABI Everything to do the ABI, especially the JSON representation compiler: frontend Everything to do with type checking, control flow analysis, and everything between parsing and IRgen compiler: parser Everything to do with the parser language feature Core language features visible to end users
Projects
None yet
Development

No branches or pull requests

1 participant