10k: Token supply will be 10.000. The entire token supply will be generated during deploy and sent to Token Owner wallet. You can't increase or reduce supply later.

Fixed Supply: The entire token supply will be generated during deploy and sent to Token Owner wallet. You can't increase or reduce supply later.

Capped Supply: You can define an initial supply to sent to Token Owner's wallet. You can increase or reduce supply later by minting or burning tokens (if allowed). You won't be able to generate more tokens than the defined supply cap.

Unlimited Supply: You can define an initial supply to sent to Token Owner's wallet. You can increase or reduce supply later by minting or burning tokens (if allowed). You will be able to generate unlimited tokens without an upper limit.

It takes us less than 7 working days (excluding Sat-Sun) in most cases to complete projects, if we all have the content from you.

Once you complete the purchase, we will email you with an approximate time frame required.

None: Token doesn't need an access type because of there are not actions that needs privileges.

Ownable: Token will have an Owner. The account you use to deploy the Token will be owner by default and will be able to mint new tokens or call the finish minting function or set the burn fee. You can transfer token ownership to addresses or Smart Contract.

Role Based: Token will have Roles. Accounts with "MINTER" role will be able to mint new tokens. Accounts with "ADMIN" role will be able to add or remove roles to minters or other admins. The account you use to deploy the Token will be ADMIN and MINTER by default. In addition the Token will have the Ownable behaviour too.

Mint: It depends on Token Access Type. If you choose Ownable Access only Token Owner will be able to mint new tokens. If you choose Role Based Access only addresses with MINTER role will be able to mint new tokens. In both cases, if you choose a Capped supply no one won't be able to mint more tokens than the defined cap. By choosing Unlimited supply instead, you will be able to generate unlimited tokens.

Burn: Everyone will be able to burn tokens he held. A third party can burn tokens from other addresses only after an approval. Nobody, not even the Token Owner, will be able to burn tokens from other addresses without approval.

Selecting a Pausable token grants exclusive pause and unpause privileges to the token owner.
NOTE: Pausable is a key feature for adding an emergency stop to smart contracts. It requires users to trust the project team, who should document their privileged roles and usage circumstances.

The Anti Whale protection mechanism permits setting a maximum percentage of total supply users can hold. The owner retains the ability to adjust this percentage or deactivate it. Additionally, certain accounts can be exempted from the anti whale protection mechanism.

A Liquidity Pool pair (i.g. an UniswapV2 Pair) will automatically be created on Uniswap or PancakeSwap during token deployment. The token owner can define an initial supply amount for the liquidity pool and decide whether to permanently lock LP tokens in the token contract or receive them in their wallet.

A token reduces its supply over time, leading to limited currency in circulation and increasing value. This supply reduction occurs through transaction fees, with each transaction incurring an automatic fee burn. Owners can adjust the burn fee and exempt certain accounts from deflation mechanisms.

A taxable token levies a fee on every transaction and transfers it to a specified wallet. The owner has the ability to adjust the tax rate and exempt certain accounts from the taxation process.

Many tokens are permanently lost in Smart Contracts. Each Ethereum contract poses a potential risk for ERC20tokens. Recovery is impossible, resulting in financial losses for users.
Token Recover enables the contract owner to retrieve any ERC20 or NFT (ERC721) token sent into the contract in error and transfer them to a receiver.

There is no way to execute code on a receiver/spender contract after an ERC20transfer, transferFrom or approve so, to perform an action, it is required to send another transaction.
This introduces complexity in UI development and friction on adoption as users must wait for the first transaction to be executed and then submit the second one. They must also pay GAS twice.

ERC1363 makes tokens capable of performing actions more easily and working without the use of any off-chain listener. It allows to make a callback on a receiver/spender contract, after a transfer or an approval, in a single transaction.

ERC1363 tokens can be used for specific utilities in all cases that require a callback to be executed after a transfer or an approval received. ERC1363 is also useful for avoiding token loss or token locking in contracts by verifying the recipient contract's ability to handle tokens.