Welcome to the edeXa ERC-20 Token repository! This repository contains the smart contract and related resources for the edeXa company's ERC-20 token. The edeXa token is built on the EVM blockchain and follows the ERC-20 token standard.
Token Name: edeXa
Token Symbol: EDX
Total Supply: Max Supply 10,000,000,000 EDX. Circulating supply may change due to mint/burn functionality.
Decimals: 18
The smart contract for the edeXa ERC-20 Token is implemented in Solidity programming language. The contract follows the ERC-20 standard, which defines a set of functions and events that allow for seamless integration with various wallets, exchanges, and other smart contracts.
The main contract file is edeXa.sol. It contains the implementation of the token contract, including functions for transferring tokens, checking balances, and managing approvals. The contract also includes additional features such as pausing and burning tokens.
The Maximum supply of our token is initially set to 10 billion. However, please note that the curent supply of the token may be subject to change. The token contract includes the functionality to adjust the current supply if necessary, ensuring flexibility and adaptability. Any changes to the total supply will be communicated transparently and in accordance with the token's governance framework. It is important to consult the latest updates and official communications to stay informed about any adjustments made to the current supply.
The edeXa ERC-20 Token smart contract can be deployed on the Ethereum blockchain using tools such as Remix, Truffle, or Hardhat. Before deployment, ensure you have the necessary dependencies installed and a compatible Ethereum development environment set up.
To deploy the token contract, follow these steps:
Compile the smart contract: Use your preferred development tool to compile the edeXa.sol file. Make sure there are no compilation errors and that the bytecode and ABI are generated successfully.
Select the desired Ethereum network: Determine the Ethereum network (e.g., mainnet, testnet, or a local development network) where you want to deploy the token contract. Configure your development tool to connect to the desired network.
Set the deployment parameters: Specify the deployment parameters such as the token name, symbol, total supply, and other optional parameters defined in the constructor of the edeXa.sol contract.
Deploy the contract: Trigger the deployment process using your development tool. Review the transaction details and confirm the deployment. Once the deployment is successful, note the deployed contract address for further reference.
The edeXa ERC-20 Token is designed to serve as a utility token within the edeXa ecosystem. Token holders can use EDX tokens for various purposes, including:
The edeXa Business Blockchain network has implemented a unique rewards system to incentivize participation from Businesses to secure edeXa Public Blockchain. Unlike other blockchain projects, we do not rely on a proof of stake model. Instead, we use a PoA consensus mechanism to verify transactions on the network and add blocks to edeXa Public Blockchain. Businesses which are a part of our validation network, can earn rewards in the form of EDX tokens.
edeXa.sol: The main smart contract file containing the implementation of the edeXa ERC-20 Token. LICENSE: The license file governing the usage and distribution of the smart contract code. README.md: This readme file providing an overview of the edeXa ERC-20 Token repository.
The edeXa ERC-20 Token smart contract is released under the MIT License. You are free to use, modify, and distribute the code in accordance with the terms and conditions specified in the license.
For more information, please refer to the license file included in this repository.
The edeXa ERC-20 Token repository and its associated smart contract are provided as-is, without any warranties or guarantees. The code is provided for informational and educational purposes only. Use the code at your own risk. The edeXa company and the contributors to this repository shall not be held liable for any damages or losses arising from the use