Muhammad Altabba

Hi @fipso, I tested with `geth` and it worked well with me by printing the block number. However, you need to remember to close the connection at the end of...

Closing this issue as could not replicate and it might be the case described here: https://github.com/web3/web3.js/issues/7323#issuecomment-2492406796 However, if this issue persists, kindly re-open the issue the provide more information. (By...

Thanky @amrzakii2000 for opening the issue. Actually, Heroku ended the version that Qutuf was using. And now there must be new configuration for a newer Heroku version, which I did...

Done at another MR

It turns out only registered facets functions of a diamonds proxy would be callable. And `getName` is not available in the proxy contract. So, no issues with web3.js. Calling methods...

Thanks @frangio, Oh, sorry, I mixed things up in the description as I just wrot this fast to keep in mind the follow-up work. And this will be revisited thoroughly...

For some reason, the following was not implemented: > Additionally, some cases need to be handled. According to: https://blog.soliditylang.org/2021/04/21/custom-errors/ there are special selectors: [UPDATED] 0x4e487b71 which is the ‘selector’ for...

This issue was resolved in the latest version `3.0.0`. They added `// @ts-expect-error` before the problematic lines in order for the TypeScript Compiler to not complain.

The following is unrelated, but the code is around: https://github.com/web3/web3.js/issues/6328