Hellobloc

verbatim is dangerous and should not be added to solidity at will. At least it needs a lot of restrictions, such as declaring it in the compilation configuration before it...

@fvictorio I feel like you don't seem to understand what I mean. First of all this is definitely not a problem that can be found with a quick review, it's...

I feel like it shouldn't throw the question to the source code verifier. Actually I feel there is a solution to generate a new invalid value ending for `verbatim`, I...

Many thanks to @sealer3 for the specific description of these issues. just like @sealer3 mentioned here，blockscout also mentions the need for verified bytecode in this [issue](https://github.com/blockscout/blockscout-rs/issues/531)

@kuzdogan Awesome research, we also noticed that etherscan does not show any error report in APIs just like you mentioned above and we already reported it to Etherscan, but they...

@marcocastignoli Checking the selfdestruct in the bytecode may not be useful, as the linked library can be used to self-destruct。

Is it okay to store the bytecode and feed it back to user, and then get the runtime code to check when someone requests the source code of a contract?...

@marcocastignoli Checking linked libraries is too complicated, and there may be recursive calls, which may introduce other risks, such as two linked libraries calling each other, which would be a...

Try to change the below code to a higher rate, i think they just give a outdated genesis? https://github.com/axelarnetwork/axelarate-community/blob/main/resources/mainnet/genesis.json#L298-L302 ``` "commission": { "rate": "0.000000000000000000", "max_rate": "0.000000000000000000", "max_change_rate": "0.000000000000000000" }, ```...

@nddeluca