Peersky

@kevincheng96 bump

> Better for ID fields to have no semantic connection with the data they describe. If we used the hashing scheme that you were initially considering, for example, it could...

@SamWilsn thanks for previous input. Could you please review new changes, when you have time? I've addressed all of items since last time we spoke

@abcoathup Im not really sure how to fix the [HTMLProofer CI error](https://github.com/ethereum/ERCs/actions/runs/9993266603/job/27620237667?pr=542), it seems that it might look for a wrong directory path (erc/eip?), could you let me know if...

# Peeramid Labs Application Project Lead: Tim Pechersky ( @peersky ) Contact info: [email protected] L2 recipient address: `0x20cbb26dd8DDE03edCFE35Ca0DF76c97734f7346` ## What makes your Team best-suited to execute this Mission? At Peeramid...

@danfinlay I missed this in my notifications log, sorry for delayed response. I agree that this adds encoding/packing difficulty, it would be much better if solidity/evm itself provided ways of...

It would make sense for me if eq/neq operations compare address.codeHash, allowing in runtime to detect whether addresses contain equal bytecode.

> Hi @peersky This suggestion makes the contracts too generic, with an increased gas cost and bloated code, since instead of using the generated dispatcher by solc to determine the...

> Maybe I misunderstand something: for instance, you replaced `validateUserOp()` with `beforeCall()`. How would the wallet know what `beforeCall()` should do? Do you intend 4337 wallets to implement erc 7746...

> @peersky although the ERC-4337 is still in `Draft` stage, it has been pretty stable for a long time and is not expected to be changed unless there is a...