Search Results

If the total supply is 1000 tokens, in the contract is stored as 1000. If you set decimals to 2, then you can split 1 token into smaller units. The minimal unit is 0.01 token. … If the total supply is 1000 tokens it is stored in the contract as 100009. The two extra ceros are because of the decimals. …

Yes, you can have as many tokens as you want, and create them on demand. You can create a token factory contract, and use it to deploy contract for new tokens. a. … Yes, you can lock all transactions for a token without affecting other tokens. If a token support ERC20 you have to block the operations transfer and transferFrom. …

No contract returns ethers/tokens automatically, you have to program something in the contract to do it. It depends on your crowdsale implementation. … to return remaining tokens uint remaining = token.balanceOf(this); token.transfer(owner, remaining); You can change owner for the destination address, and token is the crowdsale token. …

In geth version of PoA "Clique" you set the total of coins in the genesis blocks and no other coins will be mined ever. Validators get the transaction fee, but there's no reward for block creation.

An approach is to store the time of the last transaction and when needed calculate the balance based on the time elapsed. Those changes aren't stored in the contract until a transfer modifies the bala …

As of 2022-05-18 14:35:00 UTC the Tether USDT contract has a total of 4,568,883 holders. It will consume 4,568,883 x 32 bytes = 146,204,256 bytes = 139.43 Mbytes.

They wrote SAVE YAM! 🍠 with details of the error totalSupply = initSupply.mul(yamsScalingFactor); should have been: totalSupply = initSupply.mul(yamsScalingFactor).div(BASE); Line on github: http …

You can emit a new event with the required information event TransferWithPrice(address sender, address recipient, uint tokenId, uint price);

Yes, usually the token contract will reject a transfer with a non zero value. For a contract method to receive ethers it should be marked as payable, but the transfer method does not have such modif …

If tokens are not assigned to someone they cannot be used for anything, it is like they didn't exist at all. …

To allow the crowdsale contract to create new tokens you set it as the owner of the token contract. The owner of the token can create new tokens through mint function. … At the end of the crowdsale minting of new tokens is disabled and ownership is transfered to the owner of the crowdsale (I suppose a team account) so they can act in the case of an emergency. …

The account calling mint will be assigned the new created tokens. …

The problem is with _tranfer(this, msg.sender, amount); For this to work you need this to have at least amount tokens in this balance. But nowhere in your contract there is assignment for that. …

Normally your contract will only handle tokens with full precision (with 18 decimals in your case). … The frontend allows the user to enter the amount of tokens, 0.1 for example, and it will convert to 0.1 * 10^18 when sending the transaction to the contract. …

From your link the issue is that you override _transfer in RETNToken function _transfer(address _from, address _to, uint _value) internal { require (_to != 0x0); // …