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 was archived by the owner on Apr 22, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 22, 2024. It is now read-only.
Unable to truffle migrate using a custom web3 provider engine #340
Hi, I'm currently facing an issue while trying to deploy my contracts on a live network with truffle using a Ledger device.
Currently, I am able to connect to the device and properly sign and broadcast the first transaction, but it seems truffle is unable to resolve the transaction (while I can see the transaction confirmed).
I am 99% sure that the issue is coming from the web3 provider engine as I managed to deploy the contracts using the HDWallet provider, but I have no clue on what might be the difference in behavior.
I would like to know if someone else has such issues when using truffle + web3-provider-engine, or when trying to use a ledger device with truffle. Might not be the good place to ask this but honestly I cannot find people trying to do the same thing (I tried all ledger provider packages and have no results)
I am having the same issue. Works fine with ledger+ganache and HDWallet, but no luck when trying to hook into rinkeby with ledger. I'm not sure what's causing the issue, but I do have a really horrible workaround that makes it work for me: wait ~30 seconds before calling the eth_getTransactionReceipt:
web3Provider.sendAsync = (payload, callback) => {
if (payload.method == "eth_getTransactionReceipt") {
const waitUntil = new Date(new Date().getTime() + 30000);
while(waitUntil > new Date()){}
}
return web3Provider.send(payload, callback);
}
Activity
twt-- commentedon May 7, 2020
I am having the same issue. Works fine with ledger+ganache and HDWallet, but no luck when trying to hook into rinkeby with ledger. I'm not sure what's causing the issue, but I do have a really horrible workaround that makes it work for me: wait ~30 seconds before calling the
eth_getTransactionReceipt:mortimr commentedon May 7, 2020
Hi @twt--,
I managed to make it work by using the following Provider:
And by using the exact following versions (truffle version is important):