Truffle Migration To BSC Testnet Not Working

Hi

Hope youā€™re all well, iā€™m at a stage now where iā€™m trying to migrate this to the BSC Testnet, I have made the following changes in the truffle-config.js file

bscTestnet: {

  provider: () => new HDWalletProvider(mnemonic, `https://speedy-nodes-nyc.moralis.io/bcf0017bb895dcaaa02ec143/bsc/testnet`),

  network_id: 97,       // Ropsten's id

  gas: 5500000,        // Ropsten has a lower block limit than mainnet

  confirmations: 10,    // # 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 )

},

I have used the wallet provider to get an account which I have filled with 1 BNB but when I type truffle migrate or doing the reset all i get back is

Compiling your contractsā€¦

Everything is up to date, there is nothing to compile.

Any advise?

Hi

Ok so in the truffle-config.js I have the following - version: ā€œ^0.8.0ā€ which is uncommented

The reply i get from the terminal is

  • Fetching solc version list from solc-bin. Attempt #1

and thatā€™s it :-/

Hi @Baz

You can use the --reset option to run all your migrations from the beginning

truffle migrate --reset --compile-all --network bscTestnet

Let me know how it will work for you

Hi thanks for the reply i really appreciate it, iā€™ve just tried that and am getting exactly the same issue

Compiling your contractsā€¦

Everything is up to date, there is nothing to compile.

  • Fetching solc version list from solc-bin. Attempt #1

@Baz
I think I got it. Please share the full code of truffle-config.js .

Please take a look at and format your code :raised_hands:

/**

 * 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:

 *

 * trufflesuite.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 HDWalletProvider = require('@truffle/hdwallet-provider');

//

// const fs = require('fs');

const mnemonic = require("./secrets.json").mnemonic

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)

    // },

    // 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])

    // websocket: 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.

    bscTestnet: {

      provider: () => new HDWalletProvider(mnemonic, `https://speedy-nodes-nyc.moralis.io/bcf0017bb895dcaaa02ec143/bsc/testnet`),

      network_id: 97,       // Ropsten's id

      gas: 5500000,        // Ropsten has a lower block limit than mainnet

      confirmations: 10,    // # 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.8.7",    // 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"

      // }

    }

  },

  // Truffle DB is currently disabled by default; to enable it, change enabled:

  // false to enabled: true. The default storage location can also be

  // overridden by specifying the adapter settings, as shown in the commented code below.

  //

  // NOTE: It is not possible to migrate your contracts to truffle DB and you should

  // make a backup of your artifacts to a safe location before enabling this feature.

  //

  // After you backed up your artifacts you can utilize db by running migrate as follows: 

  // $ truffle migrate --reset --compile-all

  //

  // db: {

    // enabled: false,

    // host: "127.0.0.1",

    // adapter: {

    //   name: "sqlite",

    //   settings: {

    //     directory: ".db"

    //   }

    // }

  // }

};

That is my truffle-config.js file, thanks for taking the time to look into this

@Baz

Does it throw you any errors?

Looks like it canā€™t fetch solidity compiler. Try to change code to:

compilers: {

    solc: {},

  },

If it will not help. Try to download it manually:

Follow this tutorial: https://www.trufflesuite.com/docs/truffle/reference/configuration#external-compilers

Have it work correctly when you deployed the contract previously? Or itā€™s a first time?

Hi, it doesnā€™t throw any errors and this is the first time, I honestly thought this would be the easy part lol

deploy.js => 1_deploy.js!!!
In Truffle, deployment scripts are named with numerical prefixes to control the order in which they are executed. This prefixing system ensures that dependencies between contracts are respected during deployment. Hereā€™s a detailed explanation and example:

Understanding the Numerical Prefix in Truffle Deployment Scripts

Truffle uses the migrations directory to manage deployment scripts. Each script file must start with a numerical prefix to indicate the order in which it should be executed. The numbering convention helps Truffle execute the migration files in sequence.

Why Use Numerical Prefixes?

Order of Execution: Contracts that depend on other contracts being deployed first must have higher numerical prefixes.

Modularity: Allows breaking down the deployment process into manageable steps.

Clarity: Provides a clear, organized structure for the deployment process.