New answers tagged

1

You're overlooking the mining step. Contract deployment is the result of a transaction, but first a transaction has to mine. In the interim, the first response from sending a transaction, which new DepositPaying(address(this)) does, is a transaction hash. That response doesn't indicate that the transaction is processed. Only that it was sent and assigned a ...


0

This ended up being a problem in the deployer. In order to give some context, this is what the relevant part of /deployment/deploy.js looked like at the time of the question: } else if (network == 'rinkeby') { // Overriding default config for rinkeby test net defaultConfigs.chainId = 4; // Setting private key for this network ...


1

I would suggest you register your contract with Ethereum Name System (ENS) during the deployment. Create an ENS name Update its ADDRESS record to point to the latest contract deployment during the deployment https://medium.com/the-ethereum-name-service/new-text-records-now-available-for-ens-names-in-manager-a0ebb9cda73a You can do this programmatically ...


1

When you compile your contracts inside a truffle project, only the modified ones get compiled, if a build exists yet (if you want to recompile all contracts, run truffle compile --all). From the command line, there is no options to just deploy one specific contract, but you can use the flags --f <number> and --to <number> to specify which ...


1

Yes, the migration has failed. This error means you have insufficient Ethers to deploy your contract, you should therefore redeploy with the correct amount of ETH.


2

The msg.sender is always the address of the entity who called the current contract. When a contract calls another contract the msg.sender changes. Let me give you some examples. Assuming we have a EOA (Externally Owned Account) A and contracts B and C. When A calls B the msg.sender in B is A's public address. If contract B also calls contract C, msg.sender ...


0

If you are using Remix and MetaMask (ass your tags imply), then it should be calculated for you automatically (they use the eth_estimateGas RPC call under the hood). If that is the case, you should not manually enter a gasLimit of 500,000 and instead use their estimated gas. As a note, any gas that is unused in the transaction is returned to you. For example,...


0

First things first, let's dive into the issue a bit more. A linked library isn't just another contract deployed in the same ecosystem, it needs to be actively linked to the contract that uses it, as the link above (to the Truffle code for doing so) demonstrates. Buidler does not currently (mid-July 2020) have a native shortcut for doing this. An issue has ...


Top 50 recent answers are included