I couldn't find better place to ask, but why EOS Token Smart Contract implements `symbol` attribute as `bytes32` (https://etherscan.io/token/0x86fa049857e0209aa7d9e616f7eb3b3b78ecfdb0#readContract) meanwhile ERC20 says it should be `string` (https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20.md#symbol) ?
I couldn't find better place to ask, but why EOS Token Smart Contract implements
symbolattribute asbytes32(https://etherscan.io/token/0x86fa049857e0209aa7d9e616f7eb3b3b78ecfdb0#readContract) meanwhile ERC20 says it should bestring(https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20.md#symbol) ?