Dexaran

>while all of your arguments seem to be reasonable, the fact of the existence of erc1363 (and eip4524) means they are not enough I have pointed out what was not...

I personally have no objections against ERC-1363 but if it is going to be supported I would recommend to re-define the logic of `transfer` function of ERC-20 so that in...

>The EIP process is about ecosystem consensus and there seems to be demand for EIP-1363 while others are not yet finalized. That's great but it's as insecure as ERC-20. So...

@TrejGun can you show the code of `isContract()`? Is it the function from Address lib? I recall there was a change of its logic and I'd like to review which...

this one doesn't have .isContract() implemented https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/Address.sol it seems

Initially we were using a method for identifying which address is a EOA and which one is a contract that I proposed in 2017. We were assemblying the code and...

I don't think there is any significant difference

ERC-223 is now "Final". Can be used in production (after 6 years of discussions I don't believe we can discover something "new" about this standard). Here you can track the...

btw here is a script that calculates the amount of "Lost" ERC-20 tokens https://dexaran.github.io/erc20-losses Now with improved UX

Probably later. I predict that OZ staff will reply "we analyzed the chain and there are no ERC-223 contracts so we are not interested" as they did before. So it's...