Skip to main content

Network Configuration

Migrating to TEN enables your dApp to leverage “programmable encryption.” Below are steps to help you transition smoothly.

Key Migration Steps​

  • Update your Hardhat deployment to support the --network ten option.
  • Add data protection logic to your view functions (if applicable).
  • Configure visibility rules for event logs and internal storage.
  • Add features that make use of secure, verifiable randomness using block.prevrandao or precise timestamping

1. Configuring Hardhat​

First, set up a Hardhat project if you haven't already.

1.1 Installing the TEN Hardhat Plugin​

To add TEN Network compatibility, install the ten-hardhat-plugin:

npm install ten-hardhat-plugin

You can use npm or yarn to install plugins.

1.2 Configuring hardhat.config.js​

Modify hardhat.config.js in your project’s root directory as follows:

import { HardhatUserConfig } from "hardhat/config";
import "@nomiclabs/hardhat-waffle";
import "ten-hardhat-plugin";

const { PK } = process.env;

module.exports = {
  solidity: "0.8.10",
  defaultNetwork: "ten",
  networks: {
    hardhat: {
      // Configuration for the Hardhat Network
    },
    ten: {
        url: "https://testnet.ten.xyz/v1/",
        chainId: 8443,
        useGateway: true,
        accounts: [ `0x${PK}` ]
    },
  },
};

export default config;

Note in the above the private key is taken from an environment variable, rather than being put directly into the configuration file. PKs should never be added directly into any files that might be subsequently made public, e.g. through a public source code control system. Once configured, you can start writing or migrating your smart contracts.