The Transformers Smart Contract 3.

Contract execution
Preparation
A tradable, operational node and an account with a specific quantity of TTOS coins are needed according to the deployment contract in order to pay service fees that are incurred throughout the deployment procedure. The binary code of the contract, known as Bytecode or Calldata in the Remix IDE and represented as a string of hexadecimal numbers (as illustrated in the following picture), is also necessary for the deployment of smart contracts.
A folder contract will be created in the program's level directory to launch the transformers application. You must insert the binary code produced by the contract into the contract file within the directory prior to running the command to deploy the contract.
Contract Deployment​
Run the following command to run the node in menu mode

./tfs_v0.32.x_xxxx_testnet - m

1. Node Running Menu Options 8. Deploy Contract
2. Select the type of virtual machine running the contract.
3. According to the prompts, enter the contract name, version and compliant standards in sequence.
   The contract binary code, source code, ABI, and other information need to be saved in the form of a text file on the host.
   Please be aware of the following information before proceeding:
   To read the information column of a file type, you need to enter the file path or use default rules to read it.
   In advance, place the binary source code in the contract file. You can read the information from the file directly by selecting option 0. If the contract file does not exist, skip the contract reading operation.
   The default reading rules for files are as follows:

Contract source codes: ./contract/source.sol
ABI: ./contract/abi.json
User Documentation: ./contract/userdoc.json
Operation Documentation: ./contract/devdoc.json
Compilation options: ./contract/compiler_options.json
Source code compilation bytecode mapping: ./contract/srcmap.txt
Bytecode mapping during source code runtime: srcmap_runtime.txt
Metadata: ./contract/metadata.json
Custom Data: ./contract/otherdata.json
Contract Bytecode: ./contract/contract

1. If the contract constructor has passed-in parameters, you need to enter the Parameters binary code required for deployment (if the binary code stored in the contract file is Calldata, skip directly). Otherwise,enter 0 to skip.
   Contract Execution​
   Preparation​
   Just like the contract deployment, the execution of the contract can only be performed on the node temporarily. Before executing the contract, prepare the deployer's wallet address and the transaction hash generated by the deployment contract.
   Contract Execution​
   Node Running Menu 9. Call contract
   Enter the wallet address of the contract deployer, which is the wallet address of the deployment contract node.
   Enter the transaction hash when running contract deployment.
   Enter the input required to run the contract.
   Enter the tip to be paid to the contract deployment address. 0 can be entered, but if the tip is not 0, the tip must not be less than the gas fee.
   Enter the fees to be paid to the contract.