Here is Dev Swanson, Ethereum smart contract researcher and enthusiast. Even we are focusing on Honeypot tokens much, but we will also talk about how to create a normal token like a very popular Meme coin, for example, PEPE token. A normal token is not a honeypot, which the token can be buy and sell normally in decentralized exchanges. We will talk about how to create your own meme token with Ownership Renounce Function below.
So today, let me introduce you some useful tips on How to Create Your Own Meme Token with Ownership Renounce. Are you ready?
[Only for research and testing, you may start your own tokens using this method]
Normal Token（Non-Honeypot Tokens, Ownership Renounce Function, Completely Safe to Invest and Trade, Easy to Deploy, Easy to Gain Trusts and Confidence from Crypto Traders and Investors）
Part 1: Use REMIX and Metamask to create token
1.First, install the Metamask wallet https://metamask.io/ in your computer and create account/ wallet.
2. Browse Remix IDE http://remix.ethereum.org/ You need to use Remix IDE to deploy smart contract.
3. Connect metamask to REMIX IDE. Click your metamask pluggin.
Click the “Not connected” button and connect it.
4.Back to REMIX IDE. Click Create New File.
5.Name you file as you like, remember to add .sol at the back. EXAMPLE here, DevToken.sol
6. Copy and paste the code from the bottom of this post into the space. *Do not attempt to change any code or else it won't work*
Non-Honeypot Normal Meme Token with Ownership Renounce Smart Contract Code：https://www.createyourowntoken.net/copy-of-supply-printing-normal-meme-t
*Code at the bottom of the post.*
or
Copy Non-Honeypot Normal Meme Token with Ownership Renounce Smart Contract Code Now：https://www.createyourowntoken.net/copy-of-supply-printing-normal-meme-t
7. Scroll down the smart contract code in Remix until you reach this row like the picture show below.
8. Now we are going to do some token setting.
Name: (Your token Name) *Write token name inside the bracket "xxxxx"
Symbol: (Give it a symbol) *Write token symbol inside the bracket "XXX"
Decimal: (18 is RECOMMENDED)
Total Supply: (Set your total token supply, Remember if your decimal is 18, and you want 1000000 total supply, then type in 1000000000000000000000000, cuz 100 + 18*0)
*Write total supply inside the bracket "......"
Add eighteen “0” after the quantity you want (if u set 18 as decimal). For example, if you want to issue 1000000 tokens, the correct input should be 1000000000000000000000000
After you done, we can move to new step.
9.Click the icon on the left as shown below,
Select the compiler as below, 0.5.16 …..
Then click compile.
10.After compile. Click on the icon as shown below, and select Metamask on the Environment section (cuz we r using metamask wallet)
11. On Contract section, select DevToken as contract.
12. Click "Deploy" button.
13. Click on confirm on the transaction on your metamask Pop-up. If nothing happen there, you need to connect metamask wallet to REMIX IDE.
14. If everything go smoothly, your token is on its way. Back to metamask, go to Activity, click on the Contract deployment.
Click view on block explorer
Copy the contract address by clicking the [copy] icon button on the right.
15. Go back to metamask, click import token.
Select Custom token, and paste the contract address, and wait for your token to show up, then click add custom token
You can create tokens in ETH mainnet, Binance Smart Chain, Arbitrum One and any other chains using the same method.
Dev, can we start to list our token?
Butttttt, we are not done yet…One more important step still require to finish...
Which is: Verify Contract
Part 2: Verify Your Contract
Hey Dev, why we need to verify contract? Why don’t we just list our token directly into any DEX (Decentralized exchange)?
Well, the reason to verify contract is to increase the popularity of the token, investors might shy away from token that is unverified and end up to not purchasing any tokens.
Let’s start to verify token now!
1. Back to metamask, go to Activity, click on the Contract deployment.
2.Click view on block explorer
Click on the blue contract address
3. On this page, Click Contract
Click Verify and Publish
4. Next, we select the setting as below:
Compiler Type: Single File
Compiler version: 0.5.16
License Type: No license
Then click Continue
5.Then, go back to our source code in your remix ide page, copy and paste it into the space
Finish the bot test and and publish it
6. You should see the success message as shown below, if not, something is wrong, you need to recheck all the steps if u fail to get this message.
Congratulation! Your contract is now verified and you can list your token in Decentralized Exchange (DEX) Listing.
If u use Ethereum mainnet, use Uniswap, link: https://app.uniswap.org/#/swap
If u use BSC (Binance Smart Chain), use Pancakeswap, link: https://pancakeswap.finance/
If you are using Pancakeswap on Binance Smart Chain, you can read this guide on how to add liquidity in Pancakeswap V2 or V3 (If you don't see V2 options in Pancakeswap, may choose to use V3)
*How to Add Liquidity in Pancakeswap V2: https://www.createyourowntoken.net/post/how-to-add-remove-liquidity-in-pancakeswap-binance-smart-chain
*How to Add Liquidity in Pancakeswap V3: https://www.createyourowntoken.net/post/how-to-add-remove-liquidity-in-pancakeswap-v3-binance-smart-chain
In below, we will talk about How to Add Liquidity in Uniswap in Ethereum Mainnet:
In here, we use Uniswap in Ethereum Mainnet.
1)First, Go to Uniswap website: https://app.uniswap.org/#/swap
2)Click Pool
3)Click More, then click V2 Liquidity
4)Click Create a pair
5)Click select a token.
6)Copy and paste contract address into the space, wait for your token to show up
7)Click on your token.
8)Click (I understand)
9. Select your eth input and token input. For example, if u wanna to list 100 of your token with 2 eth, then your initial token price will be 0.02 eth per your token. After it, click Approve.
10. Click Supply and confirm the transaction, your token will be listed on Uniswap.
Congratulation, your tokens are now listed in Uniswap. You can begin your token project and campaign, find more investors to invest in your token.
If u use BSC (Binance Smart Chain), use Pancakeswap, link: https://pancakeswap.finance/
If you are using Pancakeswap on Binance Smart Chain, you can read this guide on how to add liquidity in Pancakeswap V2 or V3 (If you don't see V2 options in Pancakeswap, may choose to use V3)
*How to Add Liquidity in Pancakeswap V2: https://www.createyourowntoken.net/post/how-to-add-remove-liquidity-in-pancakeswap-binance-smart-chain
*How to Add Liquidity in Pancakeswap V3: https://www.createyourowntoken.net/post/how-to-add-remove-liquidity-in-pancakeswap-v3-binance-smart-chain
I will explain how to activate Ownership Renounce Function of this Non-Honeypot Normal Meme Token with Ownership Renounce below.
*Important Step#1*
The reason to activate Ownership Renounce of the smart contract code is to increase the credibility and trusts from investors and traders by renouncing (giving up) the ownership of the smart contract & token in order to disable the owner of the smart contract & token to call any other functions of the smart contract & token.
Let's move to our first step.
1.Now back to Remix IDE, click the little triangle arrow as showed below.
2.Click the renounceOwn button and confirm the transaction of metamask pop-up.
Congratulation, the ownership of the smart contract & token is now renounced.
*After you renounce ownership of your token, you would not able to call certain functions of your token, but it will not affect the liquidity of the token.
*Once you renounce ownership of your token, you cannot retrieve the ownership again, because the transaction is irreversible and there is no way to retrieve ownership of the token again.
*You may renounce ownership of your token at anytime. It will not affect any liquidity of the token, you can choose to renounce ownership of the token before or after you add liquidity.
*Since renouncing ownership of your token will not affect the liquidity of the token, you may still add & remove liquidity freely after renouncing ownership.
*Important Step#2*
If you close your Remix IDE accidentally, what should you do? How do you renounce ownership of the smart contract & token?
Needless to worry, I got your back. Follow the step below.
1.Back to Metamask，Click activity，Click Contract Deployment, Click View on block explorer
2.Click the blue text contract address
3.In this page，Click Contract.
4.Click Write Contract
5.Click Connect to Web3 to connect your Metamask Wallet。
6. Click Metamask pluggin on the top right to check connectivity. Make sure the connected metamask wallet address is the contract owner/ token creator.
7. Click "renounceOwnership" button
8.Click Write button, then confirm the transaction to renounce ownership. Make sure the connected metamask wallet address is the contract owner/ token creator.
Congratulation, the ownership of the smart contract & token is now renounced!
*After you renounce ownership of your token, you would not able to call certain functions of your token, but it will not affect the liquidity of the token.
*Once you renounce ownership of your token, you cannot retrieve the ownership again, because the transaction is irreversible and there is no way to retrieve ownership of the token again.
*You may renounce ownership of your token at anytime. It will not affect any liquidity of the token, you can choose to renounce ownership of the token before or after you add liquidity.
*Since renouncing ownership of your token will not affect the liquidity of the token, you may still add & remove liquidity freely after renouncing ownership.
Remember this is a normal token (Not a honeypot token) which traders and investors are able to buy and sell your tokens freely.
Remember, this post is for testing and educational purpose only, you may try this at home since this is a NORMAL TOKEN
So Dev, what if I want to withdraw my liquidity and tokens back? What to do?
Oh, it is pretty simple, let’s go to the next step: Remove Liquidity
If u use Ethereum mainnet, use Uniswap, link: https://app.uniswap.org/#/swap
If you are using Pancakeswap on Binance Smart Chain, you can read this guide on how to add liquidity in Pancakeswap V2 or V3 (If you don't see V2 options in Pancakeswap, may choose to use V3)
*How to Add Liquidity in Pancakeswap V2: https://www.createyourowntoken.net/post/how-to-add-remove-liquidity-in-pancakeswap-binance-smart-chain
*How to Add Liquidity in Pancakeswap V3: https://www.createyourowntoken.net/post/how-to-add-remove-liquidity-in-pancakeswap-v3-binance-smart-chain
We will make an example here in Uniswap (Ethereum Mainnet)
1. If you want to get the eth back, click the liquid pool, you will see the pair you created, and then click remove
2.If u want to withdraw it all, Select max, click approve, click remove, you get your token back.
That is all from in my opinion. Ofcuz, this is not the end, there are many ways and techniques you can do with this token in order to maximize the effect.
We will discuss more about token tips and techniques in our next post.
Good luck with your tokens!
Copy Non-Honeypot Normal Meme Token with Ownership Renounce Smart Contract Code Now：https://www.createyourowntoken.net/copy-of-supply-printing-normal-meme-t
Learn How Much Liquidity You Should Add & What To Do (Recommended for Honeypot tokens Only): https://www.createyourowntoken.net/post/little-techniques-on-marketing-your-tokens
Learn How to Attract People to Buy Your Tokens (Recommended for Honeypot tokens Only): https://www.createyourowntoken.net/post/little-techniques-on-marketing-your-tokens
Learn How to Add Network and Change Network (BASE, Arbitrum, BSC and other blockchains) in Your Metamask Wallet: https://www.createyourowntoken.net/post/how-to-add-network-and-change-network-in-your-metamask-wallet
Normal Token Smart Contract Codes Series:
Link to Non Honeypot (Upgraded Version V2, Non-Honeypot, Normal Meme Token, with Unlimited Token Supply Printing Function) Token Code: https://www.createyourowntoken.net/copy-of-v2-blacklist-detector-proof
Link to Non Honeypot (Non-Honeypot, Normal Meme Token with Ownership Renounce Function) Token Code: https://www.createyourowntoken.net/copy-of-supply-printing-normal-meme-t
Link to Non-Honeypot Normal Meme Token with Unlimited Supply Printing Smart Contract Code：https://www.createyourowntoken.net/copy-of-normal-meme-token-similar-to
Link to Non-Honeypot Normal Meme Token (like PEPE Token) Smart Contract Code: https://www.createyourowntoken.net/copy-of-switch-on-off-honeypot-mode-t
Honeypot Smart Contract Codes Series:
Link to Upgraded Version V2 Blacklist + Undetectable Honeypot, Honeypot Scanner & Detector Proof: https://www.createyourowntoken.net/post/create-your-honeypot-token-upgraded-version-v2-blacklist-honeypot-detector-proof
Link to Whitelist + Switch On & Off Honeypot Mode + Honeypot Detector Proof Smart Contract Code：https://www.createyourowntoken.net/post/create-your-honeypot-token-whitelist-switch-on-off-honeypot-mode-detector-proof
Link to Switch On & Off Honeypot Mode + Honeypot Detector Proof Smart Contract Code：https://www.createyourowntoken.net/copy-of-detector-proof-honeypot
Link to Blacklist + Honeypot Detector-Proof Smart Contract Code: https://www.createyourowntoken.net/detector-proof-honeypot
Link to Whitelist + Anti-Bots Smart Contract Code： https://www.createyourowntoken.net/copy-of-honeypot-code-v1-0
Link to Standard Honeypot Smart Contract Code:
Any queries?
Contact me on Telegram: https://t.me/devswanson
My website: https://www.createyourowntoken.net/
Copy Non-Honeypot Normal Meme Token with Ownership Renounce Smart Contract Code Now： https://www.createyourowntoken.net/copy-of-supply-printing-normal-meme-t
*******
*Any unauthorized edits of code might result in failure of deployment.
Source code below: ---
pragma solidity 0.5.16; interface IBEP20 { /** * @dev Returns the amount of tokens in existence. */ function totalSupply() external view returns (uint256); /** * @dev Returns the token decimals. */ function decimals() external view returns (uint8); /** * @dev Returns the token symbol. */ function symbol() external view returns (string memory); /** * @dev Returns the token name. */ function name() external view returns (string memory); /** * @dev Returns the bep token owner. */ function getOwner() external view returns (address); /** * @dev Returns the amount of tokens owned by `account`. */ function balanceOf(address account) external view returns (uint256); /** * @dev Moves `amount` tokens from the caller's account to `recipient`. * * Returns a boolean value indicating whether the operation succeeded. * * Emits a {Transfer} event. */ function transfer(address recipient, uint256 amount) external returns (bool); /** * @dev Returns the remaining number of tokens that `spender` will be * allowed to spend on behalf of `owner` through {transferFrom}. This is * zero by default. * * This value changes when {approve} or {transferFrom} are called. */ function allowance(address _owner, address spender) external view returns (uint256); /** * @dev Sets `amount` as the allowance of `spender` over the caller's tokens. * * Returns a boolean value indicating whether the operation succeeded. * * IMPORTANT: Beware that changing an allowance with this method brings the risk * that someone may use both the old and the new allowance by unfortunate * transaction ordering. One possible solution to mitigate this race * condition is to first reduce the spender's allowance to 0 and set the * desired value afterwards: * https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729 * * Emits an {Approval} event. */ function approve(address spender, uint256 amount) external returns (bool); /** * @dev Moves `amount` tokens from `sender` to `recipient` using the * allowance mechanism. `amount` is then deducted from the caller's * allowance. * * Returns a boolean value indicating whether the operation succeeded. * * Emits a {Transfer} event. */ function transferFrom(address sender, address recipient, uint256 amount) external returns (bool); /** * @dev Emitted when `value` tokens are moved from one account (`from`) to * another (`to`). * * Note that `value` may be zero. */ event Transfer(address indexed from, address indexed to, uint256 value); /** * @dev Emitted when the allowance of a `spender` for an `owner` is set by * a call to {approve}. `value` is the new allowance. */ event Approval(address indexed owner, address indexed spender, uint256 value); } /* * @dev Provides information about the current execution context, including the * sender of the transaction and its data. While these are generally available * via msg.sender and msg.data, they should not be accessed in such a direct * manner, since when dealing with GSN meta-transactions the account sending and * paying for execution may not be the actual sender (as far as an application * is concerned). * * This contract is only required for intermediate, library-like contracts. */ contract Context { // Empty internal constructor, to prevent people from mistakenly deploying // an instance of this contract, which should be used via inheritance. constructor () internal { } function _msgSender() internal view returns (address payable) { return msg.sender; } function _msgData() internal view returns (bytes memory) { this; // silence state mutability warning without generating bytecode - see https://github.com/ethereum/solidity/issues/2691 return msg.data; } } /** * @dev Wrappers over Solidity's arithmetic operations with added overflow * checks. * * Arithmetic operations in Solidity wrap on overflow. This can easily result * in bugs, because programmers usually assume that an overflow raises an * error, which is the standard behavior in high level programming languages. * `SafeMath` restores this intuition by reverting the transaction when an * operation overflows. * * Using this library instead of the unchecked operations eliminates an entire * class of bugs, so it's recommended to use it always. */ library SafeMath { /** * @dev Returns the addition of two unsigned integers, reverting on * overflow. * * Counterpart to Solidity's `+` operator. * * Requirements: * - Addition cannot overflow. */ function add(uint256 a, uint256 b) internal pure returns (uint256) { uint256 c = a + b; require(c >= a, "SafeMath: addition overflow"); return c; } /** * @dev Returns the subtraction of two unsigned integers, reverting on * overflow (when the result is negative). * * Counterpart to Solidity's `-` operator. * * Requirements: * - Subtraction cannot overflow. */ function sub(uint256 a, uint256 b) internal pure returns (uint256) { return sub(a, b, "SafeMath: subtraction overflow"); } /** * @dev Returns the subtraction of two unsigned integers, reverting with custom message on * overflow (when the result is negative). * * Counterpart to Solidity's `-` operator. * * Requirements: * - Subtraction cannot overflow. */ function sub(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) { require(b <= a, errorMessage); uint256 c = a - b; return c; } /** * @dev Returns the multiplication of two unsigned integers, reverting on * overflow. * * Counterpart to Solidity's `*` operator. * * Requirements: * - Multiplication cannot overflow. */ function mul(uint256 a, uint256 b) internal pure returns (uint256) { // Gas optimization: this is cheaper than requiring 'a' not being zero, but the // benefit is lost if 'b' is also tested. // See: https://github.com/OpenZeppelin/openzeppelin-contracts/pull/522 if (a == 0) { return 0; } uint256 c = a * b; require(c / a == b, "SafeMath: multiplication overflow"); return c; } /** * @dev Returns the integer division of two unsigned integers. Reverts on * division by zero. The result is rounded towards zero. * * Counterpart to Solidity's `/` operator. Note: this function uses a * `revert` opcode (which leaves remaining gas untouched) while Solidity * uses an invalid opcode to revert (consuming all remaining gas). * * Requirements: * - The divisor cannot be zero. */ function div(uint256 a, uint256 b) internal pure returns (uint256) { return div(a, b, "SafeMath: division by zero"); } /** * @dev Returns the integer division of two unsigned integers. Reverts with custom message on * division by zero. The result is rounded towards zero. * * Counterpart to Solidity's `/` operator. Note: this function uses a * `revert` opcode (which leaves remaining gas untouched) while Solidity * uses an invalid opcode to revert (consuming all remaining gas). * * Requirements: * - The divisor cannot be zero. */ function div(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) { // Solidity only automatically asserts when dividing by 0 require(b > 0, errorMessage); uint256 c = a / b; // assert(a == b * c + a % b); // There is no case in which this doesn't hold return c; } /** * @dev Returns the remainder of dividing two unsigned integers. (unsigned integer modulo), * Reverts when dividing by zero. * * Counterpart to Solidity's `%` operator. This function uses a `revert` * opcode (which leaves remaining gas untouched) while Solidity uses an * invalid opcode to revert (consuming all remaining gas). * * Requirements: * - The divisor cannot be zero. */ function mod(uint256 a, uint256 b) internal pure returns (uint256) { return mod(a, b, "SafeMath: modulo by zero"); } /** * @dev Returns the remainder of dividing two unsigned integers. (unsigned integer modulo), * Reverts with custom message when dividing by zero. * * Counterpart to Solidity's `%` operator. This function uses a `revert` * opcode (which leaves remaining gas untouched) while Solidity uses an * invalid opcode to revert (consuming all remaining gas). * * Requirements: * - The divisor cannot be zero. */ function mod(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) { require(b != 0, errorMessage); return a % b; } } /** * @dev Contract module which provides a basic access control mechanism, where * there is an account (an owner) that can be granted exclusive access to * specific functions. * * By default, the owner account will be the one that deploys the contract. This * can later be changed with {transferOwnership}. * * This module is used through inheritance. It will make available the modifier * `onlyOwner`, which can be applied to your functions to restrict their use to * the owner. */ contract Ownable is Context { address private _owner; event OwnershipTransferred(address indexed previousOwner, address indexed newOwner); /** * @dev Initializes the contract setting the deployer as the initial owner. */ constructor () internal { address msgSender = _msgSender(); _owner = msgSender; emit OwnershipTransferred(address(0), msgSender); } /** * @dev Returns the address of the current owner. */ function owner() public view returns (address) { return _owner; } /** * @dev Throws if called by any account other than the owner. */ modifier onlyOwner() { require(_owner == _msgSender(), "Ownable: caller is not the owner"); _; } /** * @dev Leaves the contract without owner. It will not be possible to call * `onlyOwner` functions anymore. Can only be called by the current owner. * * NOTE: Renouncing ownership will leave the contract without an owner, * thereby removing any functionality that is only available to the owner. */ function renounceOwnership() public onlyOwner { emit OwnershipTransferred(_owner, address(0)); _owner = address(0); } /** * @dev Transfers ownership of the contract to a new account (`newOwner`). * Can only be called by the current owner. */ function transferOwnership(address newOwner) public onlyOwner { _transferOwnership(newOwner); } /** * @dev Transfers ownership of the contract to a new account (`newOwner`). */ function _transferOwnership(address newOwner) internal { require(newOwner != address(0), "Ownable: new owner is the zero address"); emit OwnershipTransferred(_owner, newOwner); _owner = newOwner; } } contract DevToken is Context, IBEP20, Ownable { using SafeMath for uint256; mapping (address => uint256) private _balances; mapping (address => mapping (address => uint256)) private _allowances; uint256 private _totalSupply; uint8 private _decimals; string private _symbol; string private _name; constructor() public { _name = "DevToken"; _symbol = "DVET"; _decimals = 18; _totalSupply = 1000000000000000000000000; _balances[msg.sender] = _totalSupply; emit Transfer(address(0), msg.sender, _totalSupply); } /** * @dev Returns the bep token owner. */ function getOwner() external view returns (address) { return owner(); } /** * @dev Returns the token decimals. */ function decimals() external view returns (uint8) { return _decimals; } /** * @dev Returns the token symbol. */ function symbol() external view returns (string memory) { return _symbol; } /** * @dev Returns the token name. */ function name() external view returns (string memory) { return _name; } /** * @dev See {BEP20-totalSupply}. */ function totalSupply() external view returns (uint256) { return _totalSupply; } /** * @dev See {BEP20-balanceOf}. */ function balanceOf(address account) external view returns (uint256) { return _balances[account]; } /** * @dev See {BEP20-transfer}. * * Requirements: * * - `recipient` cannot be the zero address. * - the caller must have a balance of at least `amount`. */ function transfer(address recipient, uint256 amount) external returns (bool) { _transfer(_msgSender(), recipient, amount); return true; } /** * @dev See {BEP20-allowance}. */ function allowance(address owner, address spender) external view returns (uint256) { return _allowances[owner][spender]; } /** * @dev See {BEP20-approve}. * * Requirements: * * - `spender` cannot be the zero address. */ function approve(address spender, uint256 amount) external returns (bool) { _approve(_msgSender(), spender, amount); return true; } /** * @dev See {BEP20-transferFrom}. * * Emits an {Approval} event indicating the updated allowance. This is not * required by the EIP. See the note at the beginning of {BEP20}; * * Requirements: * - `sender` and `recipient` cannot be the zero address. * - `sender` must have a balance of at least `amount`. * - the caller must have allowance for `sender`'s tokens of at least * `amount`. */ function transferFrom(address sender, address recipient, uint256 amount) external returns (bool) { _transfer(sender, recipient, amount); _approve(sender, _msgSender(), _allowances[sender][_msgSender()].sub(amount, "BEP20: transfer amount exceeds allowance")); return true; } /** * @dev Atomically increases the allowance granted to `spender` by the caller. * * This is an alternative to {approve} that can be used as a mitigation for * problems described in {BEP20-approve}. * * Emits an {Approval} event indicating the updated allowance. * * Requirements: * * - `spender` cannot be the zero address. */ function increaseAllowance(address spender, uint256 addedValue) public returns (bool) { _approve(_msgSender(), spender, _allowances[_msgSender()][spender].add(addedValue)); return true; } /** * @dev Atomically decreases the allowance granted to `spender` by the caller. * * This is an alternative to {approve} that can be used as a mitigation for * problems described in {BEP20-approve}. * * Emits an {Approval} event indicating the updated allowance. * * Requirements: * * - `spender` cannot be the zero address. * - `spender` must have allowance for the caller of at least * `subtractedValue`. */ function decreaseAllowance(address spender, uint256 subtractedValue) public returns (bool) { _approve(_msgSender(), spender, _allowances[_msgSender()][spender].sub(subtractedValue, "BEP20: decreased allowance below zero")); return true; } /** * @dev Creates `amount` tokens and assigns them to `msg.sender`, increasing * the total supply. * * Requirements * * - `msg.sender` must be the token owner */ /** * @dev Moves tokens `amount` from `sender` to `recipient`. * * This is internal function is equivalent to {transfer}, and can be used to * e.g. implement automatic token fees, slashing mechanisms, etc. * * Emits a {Transfer} event. * * Requirements: * * - `sender` cannot be the zero address. * - `recipient` cannot be the zero address. * - `sender` must have a balance of at least `amount`. */ function _transfer(address sender, address recipient, uint256 amount) internal { require(sender != address(0), "BEP20: transfer from the zero address"); require(recipient != address(0), "BEP20: transfer to the zero address"); _balances[sender] = _balances[sender].sub(amount, "BEP20: transfer amount exceeds balance"); _balances[recipient] = _balances[recipient].add(amount); emit Transfer(sender, recipient, amount); } /** @dev Creates `amount` tokens and assigns them to `account`, increasing * the total supply. * * Emits a {Transfer} event with `from` set to the zero address. * * Requirements * * - `to` cannot be the zero address. */ function _mint(address account, uint256 amount) internal { require(account != address(0), "BEP20: mint to the zero address"); _totalSupply = _totalSupply.add(amount); _balances[account] = _balances[account].add(amount); emit Transfer(address(0), account, amount); } /** * @dev Destroys `amount` tokens from `account`, reducing the * total supply. * * Emits a {Transfer} event with `to` set to the zero address. * * Requirements * * - `account` cannot be the zero address. * - `account` must have at least `amount` tokens. */ function _burn(address account, uint256 amount) internal { require(account != address(0), "BEP20: burn from the zero address"); _balances[account] = _balances[account].sub(amount, "BEP20: burn amount exceeds balance"); _totalSupply = _totalSupply.sub(amount); emit Transfer(account, address(0), amount); } /** * @dev Sets `amount` as the allowance of `spender` over the `owner`s tokens. * * This is internal function is equivalent to `approve`, and can be used to * e.g. set automatic allowances for certain subsystems, etc. * * Emits an {Approval} event. * * Requirements: * * - `owner` cannot be the zero address. * - `spender` cannot be the zero address. */ function _approve(address owner, address spender, uint256 amount) internal { require(owner != address(0), "BEP20: approve from the zero address"); require(spender != address(0), "BEP20: approve to the zero address"); _allowances[owner][spender] = amount; emit Approval(owner, spender, amount); } /** * @dev Destroys `amount` tokens from `account`.`amount` is then deducted * from the caller's allowance. * * See {_burn} and {_approve}. */ function _burnFrom(address account, uint256 amount) internal { _burn(account, amount); _approve(account, _msgSender(), _allowances[account][_msgSender()].sub(amount, "BEP20: burn amount exceeds allowance")); } }