Skip to content
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.

fork network, local debug error "Numbers can only be safely stored up to 53 bits" #236

Open
brunsu opened this issue Oct 6, 2022 · 7 comments

Comments

@brunsu
Copy link

brunsu commented Oct 6, 2022

Here is the video I recorded reporting the error

2022-10-06.10.07.24.mp4

link: https://s21.aconvert.com/convert/p3r68-cdx67/84l4l-289cf.mp4

@brunsu
Copy link
Author

brunsu commented Oct 9, 2022

@xhulz

@xhulz
Copy link
Contributor

xhulz commented Oct 10, 2022

Hey @brunsu!

Thank you for open this issue :)

Let me check what is happening and I'll turn to you as soon as possible.

Cheers!

@xhulz
Copy link
Contributor

xhulz commented Oct 10, 2022

@brunsu some questions:

  • Are you using the HDWallet?
  • Are you trying to debug on local Ganache?

Thank you!

@brunsu
Copy link
Author

brunsu commented Oct 12, 2022

@brunsu some questions:

  • Are you using the HDWallet?
  • Are you trying to debug on local Ganache?

Thank you!

yes
I want to debug on local fork network ganache

@xhulz
Copy link
Contributor

xhulz commented Nov 2, 2022

Hey @brunsu,

Sorry for the delay. We have released a new version of the VSCode extension with some improvements and debug fixes. Could you please test it again?

Cheers!

@kevinbluer
Copy link
Member

Also @brunsu just for reference the fix @xhulz is referencing is in the v2.6.0 release (changelog). Unless you've changed the default behavior, the extension should automatically update itself with VS Code, but it could be worth checking the version via the extensions tab:

Screen Shot 2022-11-02 at 2 32 17 PM

@acuarica
Copy link
Contributor

Hi @brunsu thanks for reporting this. After further investigation, we realized that this issue is caused by a bug in Web3js when forking BSC network. We are using Web3js to interact with the underlying network. Take a look at web3/web3.js#3789 and web3/web3.js#3948 for discussions surrounding this issue. TL;DR; gasLimit is greater than 53 bits in some BSC transactions, that's the reason for the error and it's not going to be fixed in the current version of Web3js web3/web3.js#3789 (comment).

Nevertheless, we did some quick experiments when forking a BSC network. After bypassing this error, we found there is another issue, we get a missing trie node error coming from their RPC. We are going to discuss internally about how we are going to support BSC in the future. We'll keep you posted.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants