createdContractAddress intermittently shows a different contract address from the one deployed on the network
See original GitHub issuecreatedContractAddress
in txutils
will sometimes show the correct contract address but sometimes show a different contract address from the one that actually gets deployed.
Any ideas on why this is happening? You can test it out on a private testnet and about 10-20% of the time the contract address does not match the one that gets deployed.
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
createdContractAddress intermittently shows a different contract ...
createdContractAddress intermittently shows a different contract address from the one deployed on the network.
Read more >Recover ETH in a smart contract - solidity
I've seen this too many times already. This is a scam, unfortunately, the funds are lost. Only the scammer can retrieve those funds....
Read more >Calling the set() function (with web3js) of a solidity contract is ...
When I call the contract's set() function, the resulting transaction is at a newly created contract address instead of the contract address ......
Read more >HackPedia: 16 Solidity Hacks/Vulnerabilities, their Fixes and ...
This attack can occur when a contract sends ether to an unknown address. ... that the attacker has withdrawn all (bar 1) ether...
Read more >ethereum/solidity - Gitter
If I have 4 contracts and one inherits from the others I don't need ... put a just created contract address onto the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
it doesnt - you need to fill in that info yourself
eth-lightwallet currently does not handle any persistence or network - this is a good thing as everyone has different solutions for this
@kumavis “it doesnt - you need to fill in that info yourself”
https://github.com/ethereum/wiki/wiki/JavaScript-API#web3ethsendtransaction
Only from is required. Using this code:
function sendEth() { var fromAddr = document.getElementById('addr').innerHTML var toAddr = document.getElementById('sendTo').value var valueEth = document.getElementById('sendValueAmount').value var value = parseFloat(valueEth)*1.0e18 web3.eth.sendTransaction({from: fromAddr, to: toAddr, value: value}, function (err, txhash) { console.log('error: ' + err) console.log('txhash: ' + txhash) }) }
It’s returning tx and eth sent, but it send to a random address? Multiple txs in geth console as well?
I’ve written here : https://stackoverflow.com/questions/46741374/web3-eth-sendtransaction-sending-to-random-address