If we config the cache options in the config file, then it will be overwritten.

Following
https://web3js.readthedocs.io/en/v1.3.0/web3-utils.html?highlight=BN#bn

Run:
new BN('0xea').toString();

Expected behavior

"234"

Actual behavior

"3450"

PS: web3.utils.toBN('0xea') returns "234" correctly

In this error message:

Error: There was a timeout while attempting to connect to the network.
       Check to see that your provider is valid.
       If you have a slow internet connection, try configuring a longer timeout in your Truffle config. Use the networks[networ

🧐 Motivation
Create simple ERC20 and ERC777 presets with fixed supply.
The benefits are:

• Easy to deploy (including from Remix).
• No access control (for minting/pausing), and hence no governance required.
• Can be verified easily on public networks and then are verified for all.

📝 Details

Community members are creating their own simple ERC20 tokens, so it would be good if they

If A is a constant that divides 2**256 (so basically of the form 2**N), then the two expressions should be the same. mod(mul(X, Y), A) costs 10 and mulmod(X, Y, A) costs 8 (excluding the shorter deploy code.)

Describe the bug
From Issue #6441.
In the "Info & Help" page, a large fox icon occupies enough vertical space that the "Help" portion of "Info & Help" is pushed off the bottom & requires scrolling.

Current:

Better:
![image](https://user-images.githubusercontent.com/563406/

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

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

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the