i really appreciate for this good example of ico contract.
i just have a question about how can i know method signature.
i recognized that you use '0xd7bb99ba ' as a payable signature
and it makes walking 'contribute()' and it can be exchange Token.
but this time i just wonder if i make a new function for payable function,
how can i know method signature?

I want you to great ico contract
@Talaatsmb

please how do i use this

Hi,

I deployed the tokens (Sale and Token) from my Account2 via Remix online compiler but when I try to send some ethers from my Account1 to the Sale contract I get in MetaMask:
"Gas limit set dangerously high. Approving this transaction is likely to fail." And the transaction really fails.
Any idea what might be wrong?

I am using Ropsten Testnet

Hey,

Tried asking on couple of places but no luck, could you please help me, since polygon scan or etherscan are not open sourced I can not check how they work internally?

I have a erc-1155 contract that manages 2 erc-20 tokens, both with 6 decimals. I am trying to set uri, in format "https://some-url/{id}.json".
According to docs, clients should be able to replace {id} with tokenId and that should be standardized.
However, there is no impact on mumbai polyscan, decimals are not shown in transfers (for 10 with decimals 6, it is showing 10000000).
My expectations were if i specify metadata with "decimals": 6, that mumbai polyscan would recognize this, and show values properly.

My question is, are these expectations correct, or is this not possible? Or is this not possible only on mumbai polyscan?

My metadata looks like this:
{
"name": "Test token",
"decimals": 6,
"description": "Test token"
}

Thanks in advance

Originally posted by @skosito in ethereum/EIPs#1155 (comment)