web3
Here are 1,754 public repositories matching this topic...
-
Updated
Nov 3, 2021
-
Updated
Nov 2, 2021
-
Updated
Nov 3, 2021 - JavaScript
-
Updated
Nov 2, 2021 - TypeScript
-
Updated
Oct 20, 2021 - JavaScript
-
Updated
May 8, 2019 - Swift
-
Updated
Nov 3, 2021 - Go
-
Updated
Nov 4, 2021 - TypeScript
Just to let you know you have a problem with ABIEncoderV2 if you are trying to call a function that returns a struct.
Call to a member function staticPartLength() on integer
-
Updated
Oct 18, 2021 - JavaScript
-
Updated
Nov 4, 2021 - JavaScript
-
Updated
Nov 2, 2021 - JavaScript
-
Updated
Feb 27, 2020 - Swift
-
Updated
Nov 4, 2021 - TypeScript
Is your feature request related to a problem? Please describe.
In our tests we frequently call out to 3rd party providers: Infura, Etherscan, Alchemy, various Gas Oracles and so on. These tests are mixed inside the unit test code. Sometimes these tests fail for 3rd party reasons (rate limiting, service down, 2 PRs opened at the same time causing nonce-reuse etc.) and they can cause confusio
-
Updated
Jun 16, 2020 - JavaScript
-
Updated
Nov 3, 2021 - JavaScript
-
Updated
Feb 8, 2018 - JavaScript
walletconnect always goes to rinkeby...
<UseWalletProvider
chainId={3}
connectors={{
walletconnect: {
rpcUrl:
'https://ropsten.infura.io/v3/7082b757ec2e4ebd8d47ca9518743623',
},
}}
>
...
onConnect={() => connect('walletconnect')}
But...
Response :
POST https://rinkeby.infura.io/v3/ 401 (Unauthorized
-
Updated
Sep 18, 2021 - PHP
-
Updated
Sep 17, 2021
-
Updated
Oct 7, 2021 - JavaScript
-
Updated
Jul 31, 2021 - Swift
When use formatToEthereumUnits from Web3.Utils it use decimals parameter, and after format BigInt it's may create many redundant zeros at the end. For example if 'decimals' parameter is 18 we have: 990000000000000 wei -> 0.000990000000000000 eth
At old repo already have similar issue:
BANKEX/web3swift#200
and some solution:
https://github.com/v57/web3swift/commi
-
Updated
Nov 3, 2021 - Rust
-
Updated
Oct 20, 2021 - JavaScript
Improve this page
Add a description, image, and links to the web3 topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the web3 topic, visit your repo's landing page and select "manage topics."
We should add explicit runtime errors that stop CLI execution when an obvious version mismatch is detected. No one (me neither) checks peer dependency-related errors from a package manager.
TC should bail if:
Each target package should be able to define custom conditions