Generating deployed bytecode
- Dominant language
- C++
- Stars
- 25.7k
- Forks
- 6.2k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 29
Description
With geth supporting code overrides in many RPC calls, I would very much like to use them during development as it is much easier for me to test on a life network than dealing with any of the Solidity development frameworks. However, despite multiple attempts, so far I haven't been able to find a way to have solidity generate the deployed bytecode, i.e. the bytecode as it would look on-chain after copying, replacing immutables, running all constructors etc.
Did I overlook something or is this not possible with Solidity at the moment? Are there any other methods people use to generate bytecode for overloading in RPC calls?
Contributor guide
Research direction
Start by reviewing the Solidity compiler's existing bytecode outputs and the handling of constructors and immutables. Compare those outputs with the deployed bytecode needed for geth code overrides, including post-construction changes. Done means establishing whether this output is supported and, if not, defining the compiler change or documentation needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, solidity
- Domain
- blockchain, compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100