You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2022. It is now read-only.
Due to this issue, using a wrapper function that returns an hdwallet-provider in truffle-config fails. To fix that, we had implemented a hack that consisted in evaluating that function to obtain a single instance, and set it as a global provider.
Based on reports from users on zos 2.1.0, truffle 5.0.2, and hdwallet-provider 1.0.2, that is no longer working. Using the wrapper function causes "replacement transaction underpriced" errors, while removing it fixes the issue.
We need to check whether the difference is in zos, truffle, or hdwallet-provider, and re-enable caching the single instance of the provider, since the issue has been open on the provider for over 4 months and there are no signs of fixing.
The text was updated successfully, but these errors were encountered:
@spalladino do we have more info about this issue? I've tested it with zos versions 2.1.0, 2.1.2 and 2.2.0 but I can't reproduce it neither on testnets (rinkeby, ropsten at least) nor on mainnet 😞 (using [email protected] and [email protected])
Due to this issue, using a wrapper function that returns an hdwallet-provider in truffle-config fails. To fix that, we had implemented a hack that consisted in evaluating that function to obtain a single instance, and set it as a global provider.
Based on reports from users on zos 2.1.0, truffle 5.0.2, and hdwallet-provider 1.0.2, that is no longer working. Using the wrapper function causes "replacement transaction underpriced" errors, while removing it fixes the issue.
We need to check whether the difference is in zos, truffle, or hdwallet-provider, and re-enable caching the single instance of the provider, since the issue has been open on the provider for over 4 months and there are no signs of fixing.
The text was updated successfully, but these errors were encountered: