truffle初始化的項目在部署(migrate)的時候出現invalid opcode的異常

異常重現

最近在使用truffle框架與Ganache開發以太坊合約的時候,採用默認配置的時候(僅修改端口爲7545),部署時會出現invalid opcode異常如下圖:
異常截圖

項目初始化

通過命令truffle unbox webpack進行項目初始化
項目目錄如下:
項目目錄

配置文件truffle-config.js詳情

/**
 * Use this file to configure your truffle project. It's seeded with some
 * common settings for different networks and features like migrations,
 * compilation and testing. Uncomment the ones you need or modify
 * them to suit your project as necessary.
 *
 * More information about configuration can be found at:
 *
 * truffleframework.com/docs/advanced/configuration
 *
 * To deploy via Infura you'll need a wallet provider (like truffle-hdwallet-provider)
 * to sign your transactions before they're sent to a remote public node. Infura accounts
 * are available for free at: infura.io/register.
 *
 * You'll also need a mnemonic - the twelve word phrase the wallet uses to generate
 * public/private key pairs. If you're publishing your code to GitHub make sure you load this
 * phrase from a file you've .gitignored so it doesn't accidentally become public.
 *
 */

// const HDWallet = require('truffle-hdwallet-provider');
// const infuraKey = "fj4jll3k.....";
//
// const fs = require('fs');
// const mnemonic = fs.readFileSync(".secret").toString().trim();

module.exports = {
  /**
   * Networks define how you connect to your ethereum client and let you set the
   * defaults web3 uses to send transactions. If you don't specify one truffle
   * will spin up a development blockchain for you on port 9545 when you
   * run `develop` or `test`. You can ask a truffle command to use a specific
   * network from the command line, e.g
   *
   * $ truffle test --network <network-name>
   */

  networks: {
    // Useful for testing. The `development` name is special - truffle uses it by default
    // if it's defined here and no other network is specified at the command line.
    // You should run a client (like ganache-cli, geth or parity) in a separate terminal
    // tab if you use this network and you must also set the `host`, `port` and `network_id`
    // options below to some value.
    //
    // development: {
    //  host: "127.0.0.1",     // Localhost (default: none)
    //  port: 8545,            // Standard Ethereum port (default: none)
    //  network_id: "*",       // Any network (default: none)
    // },
    
    develop: {
      port: 7545
    },

    // Another network with more advanced options...
    // advanced: {
      // port: 8777,             // Custom port
      // network_id: 1342,       // Custom network
      // gas: 8500000,           // Gas sent with each transaction (default: ~6700000)
      // gasPrice: 20000000000,  // 20 gwei (in wei) (default: 100 gwei)
      // from: <address>,        // Account to send txs from (default: accounts[0])
      // websockets: true        // Enable EventEmitter interface for web3 (default: false)
    // },

    // Useful for deploying to a public network.
    // NB: It's important to wrap the provider as a function.
    // ropsten: {
      // provider: () => new HDWalletProvider(mnemonic, `https://ropsten.infura.io/v3/YOUR-PROJECT-ID`),
      // network_id: 3,       // Ropsten's id
      // gas: 5500000,        // Ropsten has a lower block limit than mainnet
      // confirmations: 2,    // # of confs to wait between deployments. (default: 0)
      // timeoutBlocks: 200,  // # of blocks before a deployment times out  (minimum/default: 50)
      // skipDryRun: true     // Skip dry run before migrations? (default: false for public nets )
    // },

    // Useful for private networks
    // private: {
      // provider: () => new HDWalletProvider(mnemonic, `https://network.io`),
      // network_id: 2111,   // This network is yours, in the cloud.
      // production: true    // Treats this network as if it was a public net. (default: false)
    // }
  },

  // Set default mocha options here, use special reporters etc.
  mocha: {
    // timeout: 100000
  },

  // Configure your compilers
  compilers: {
    // solc: {
    //   version: "0.5.1",    // Fetch exact version from solc-bin (default: truffle's version)
    //   docker: true,        // Use "0.5.1" you've installed locally with docker (default: false)
    //   settings: {          // See the solidity docs for advice about optimization and evmVersion
    //    optimizer: {
    //      enabled: false,
    //      runs: 200
    //    },
    //    evmVersion: "byzantium"
    //   }
    // }
  }
}

最初猜想

  1. truffle有自帶的solidity編譯器
  2. 修改truffle配置文件中節點端口即可完成部署

異常修復過程

懷疑是truffle本身帶有的solidity編譯器編譯出來的opcode不符合規範(換句話說,evm無法識別)

自定義solidity編譯器

將以上truffle-config.js配置文件的第91-101行註釋打開!

solc: {
  version: "0.5.1",    // Fetch exact version from solc-bin (default: truffle's version)
  docker: false,        // Use "0.5.1" you've installed locally with docker (default: false)
  settings: {          // See the solidity docs for advice about optimization and evmVersion
   optimizer: {
     enabled: false,
     runs: 200
   },
   evmVersion: "byzantium"
  }
}

同時,要注意其中的docker: true配置,將其改爲false(如果您的機器裝了docker,就可以不改)
這個時候truffle就會幫你下載對應的編譯器然後編譯。此時編譯後的合約,就可以被evm識別並部署成功。

發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章