Ethereum

It is currently difficult to see if this API is implemented at all and what the API actually is from the docs, for which there are none. It should be here I think(?): https://geth.ethereum.org/docs/rpc/ns-eth

🎉 Description

The ECDSA contract has a function toEthSignedMessage(bytes32), but we should have a function that works for any length of a bytes array:

function toEthSignedMessage(bytes s) pure internal returns (bytes32) {
  return keccak256(
    "\x19Ethereum Signed Message:\n",
    uintToBytes(s.length),
    s);
}

Where uintToBytes is implemented from an ideally

Looking at the list of Yul transformations in the documentation, I noticed a few slight differences between the list at https://docs.soliditylang.org/en/latest/yul.html#optimization-step-sequence and the list at https://docs.soliditylang.org/en/latest/internals/optimizer.html#optimizer-steps:

• In the second list, change FunctionalInliner to ExpressionInliner, just like in the first list.

Issue

The "Full Example" of using @truffle/contract to interact with contracts should include an example of listening to an event with a filter.

In the past, it used to be possible to pass a filter object on indexed event parameters when listening to an event, as seen for example [here](https://ethereum.

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

The cpp-ethereum homepage is not exactly helpful... http://cpp-ethereum.org/ which just takes you to here: http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum/ which only helps with building and installing.. and the only useful link is the "Running" which is only this: "Running eth without any argument will synchronise your node to the public blockchain. It is also possible to create or

On the dex branch of scaffold-eth, the readme file describes the smart contract wallet challenge instead of the one for building a DEX.

Add custom clj-kondo hooks for macroses to ensure that lint rules are followed inside them.

Macros to be handled:

• fx/defn - similarly to defn with check on metadata for ::events
• fx/merge - seems like it could be lint'ed as thread macro, plus warn on limitations
• defview
• letsubs - lint as let + check on types for