New answers tagged truffle-deployment
0
@alberto has it correct.
truffle(ropsten)> Migrations.new.estimateGas()
193243
0
truffle by default uses the first account from ganache network, why do you need to specify the from address? if its necessary make sure the account is in ganache's network.
here is my suggestion
development: {
host: "127.0.0.1", // Localhost (default: none)
port: 8545, // Standard Ethereum port (default: none)
...
0
To update an artifact, you can simply recompile the contract. But deployed smart contracts are immutable. That's their beauty. If you don't want to redeploy the contract, why you want to recompile it? You cannot simply update the artifact (recompile) and expect the deployed contract to update.
Edit:
The artifacts (also called ABI) are results of compilation ...
1
This turned out to be related to bytecode rather than the gas limit
Found this:
Ganache: out-of-gas during deployment
Saying:
The real reason (see the answer) is: apparently, there is a 24kB size restriction on the deployed bytecode (besides the gas limits).
So I read https://blog.polymath.network/solidity-tips-and-tricks-to-save-gas-and-reduce-bytecode-...
0
I somehow managed to work around it by calling each step in the script.
"deploy_test": "npm run reset_test_evm && npm run migrate -- --network test --reset && npm run snapshot_test_evm && npm run clean_contract_json",
"reset_test_evm": "node scripts/reset-test-evm.js",
"migrate": "...
Top 50 recent answers are included