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

Investigate bytecode metadata and service APIs for tooling around transactions #3116

Open
ma2bd opened this issue Jan 13, 2025 · 0 comments
Open
Assignees
Labels
question Further information is requested

Comments

@ma2bd
Copy link
Contributor

ma2bd commented Jan 13, 2025

Block explorers should be able to make sense of transactions (operations and messages) in blocks.
However, the (presumably BCS-based) binary format is application-specific.

One seemingly easy solution would be to add APIs to the service bytecode for JSON<>BCS conversions.

We should also let bytecode authors share additional information when they upload their code. Notably, the URL of the source code. Eventually reproducible builds could be checked by the community.

@ma2bd ma2bd added the question Further information is requested label Jan 13, 2025
@ma2bd ma2bd assigned ma2bd and jvff Jan 13, 2025
@ma2bd ma2bd added this to Web3 SDK Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: No status
Development

No branches or pull requests

2 participants