MetaCoin example TronBox project
Network configuration is generally divided into development environment (development) and online formal production (production), but other test network environments can be added. In this example we use TronGrid, a test server which is reset daily:
module.exports = {
networks: {
development: {
from: 'TPL66VK2gCXNCD7EJg9pgJRfqcRazjhUZY',
privateKey: 'da146374a75310b9666e834ee4ad0866d6f4035967bfc76217c5a495fff9f0d0',
consume_user_resource_percent: 30,
fee_limit: 100000000,
fullNode: "https://api.trongrid.io:8090",
solidityNode: "https://api.trongrid.io:8091",
eventServer: "https://api.trongrid.io",
network_id: "*" // Match any network id
}
}
};
Below describes the meaning of each parameter in the network configuration:
from: Primary account address for contract deployment (base58)
privateKey: Private key corresponding to the contract deployment master account
consume_user_resource_percent: Parameters for deployment; can use default settings
fee_limit: Parameters for deployment; can use default settings
fullNode: The URL of a Tron full node. In the example, the url refers to a test environment which is reset daily.
solidityNode: The URL of solidity node synced with the full node above.
eventServer: The URL of the contract deployment destination event monitoring service (Need to be on same IP as the API server, otherwise the event callback cannot be monitored. For example, the API service address is http://127.0.0.1:8090, then the event listener service address is http://127.0.0.1:****)
network_id: Can use default settings
tronbox compile
tronbox migrate
tronbox test
First off, install the dependencies
npm install
To work properly, the Dapp needs to know the address where the MetaCoin contract has been deployed. You can set it manually in the code, but the easy way is to run
npm run migrate
It will execute the migration, retrieve the contract address and save it in the file src/js/metacoin-config.js
npm run dev
It automatically will open the Dapp in the default browser.