Skip to content
Discussion options

You must be logged in to vote

I overlooked the fact that the example I picked on etherscan had Optimization Enabled: Yes with 200 runs, once I did that solc --optimize --optimize-runs=200 --bin contract.sol -o contract_out, I got my SORA contract output to match (mostly, excluding what I assume is metadata) the bytecode on etherscan. It's also clear now the bytecode shown is of the specific contract that was deployed (of which there can only be one), which is also shown by Contract Name: SORA on etherscan. That's it, answer found.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by AhmedDusuki
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant