These are chat archives for Nethereum/Nethereum
@phoxha - That's possible as long as you have a corresponding parameter to allow for that.
I've defined my transfer as: transfer(address _to, uint256 _value, string test)
The catch being the ERC20 standard interface accepts two parameters only (address, uint256), so you'll be doing this by means of an overrides, and users need to explicitly call the function with an additional parameter to enter a message.
Indeed, tinkering with the standard will make it incompatible with ecosystem tools.
My example defined an override to accept an extra string param which raises an event, so MyCrypto etc will still be able to access the standard ERC20 transfer function. :D
Calling from MyCrypto (signature 0xa9059cbb):
But yea, possibly a better way is to define a separate transfer, something like "transferWithMessage". :D
Assets/DecodeData.cs(44,3): error CS0012: The type 'NBitcoin.IRandom' is defined in an assembly that is not referenced. Consider adding a reference to assembly 'NBitcoin, Version=184.108.40.206, Culture=neutral, PublicKeyToken=null'