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.

Sign up for GitHub

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

Jump to bottom

A developer can broadcast their contract bytecode to L1 #214

Closed
iAmMichaelConnor opened this issue Apr 8, 2023 · 1 comment
Closed

A developer can broadcast their contract bytecode to L1 #214

iAmMichaelConnor opened this issue Apr 8, 2023 · 1 comment
Labels
T-feature-request Type: Adding a brand new feature (not to be confused with improving an existing feature).

Comments

@iAmMichaelConnor
Copy link
Contributor

iAmMichaelConnor commented Apr 8, 2023 •
edited
Loading

Currently, bytecode is only shared via web2.
For public functions (and private functions which we'd like to be broadcast to the world) broadcasting via L1 is a neat data availability approach.
@LHerskind LHerskind added this to A3 Mar 7, 2023
@iAmMichaelConnor iAmMichaelConnor converted this from a draft issue Apr 8, 2023
@iAmMichaelConnor iAmMichaelConnor added the T-feature-request Type: Adding a brand new feature (not to be confused with improving an existing feature). label Apr 8, 2023
@LHerskind
Copy link
Contributor

This is fixed in #41

@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Apr 11, 2023
@iAmMichaelConnor iAmMichaelConnor removed this from A3 Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-feature-request Type: Adding a brand new feature (not to be confused with improving an existing feature).
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LHerskind @iAmMichaelConnor