Transfer and Approve events are slightly different from ERC20 standard wiki (missing _)

[yaronvel]

For example, you are using from instead of _from in Transfer event.
See wiki here.

It could cause problems when parsing events with web3.
However, I am guessing this standard is not strictly followed and devs cannot rely on it anyway.

[frangio]

Thanks for reporting @yaronvel!

I've noticed this before, but I don't think it's an issue. The argument names are not included in the actual event data. They're only used when decoding it at the application level. See web3's decode function. The event data is in two arrays which are "zipped" together with the names in ABI.

[yaronvel]

Yeah, it is very minor issue.
I encountered it when my truffle test failed for unknown field name. So it does have (minor) meaning.

Anyway, just wanted to let you know. As you are already aware of it, i will close the issue.

[frangio]

What do you mean with the unknown field name? Is it posible that it said <indexed> ?

[yaronvel]

If I use log.args._from.valueOf() it throws an exception as log.args._from is undefined.
So I have to use log.args.from.valueOf().
This is the full code:

        return tokenContract.transfer( reciver.address, amount, {from: sender.address} ).then(function(result){
            if( shouldFail ) {
                assert.fail("expecting transfer to fail");
            }
            
            assert.equal(result.logs.length, 1, "expected a single event");
            var log = result.logs[0];            
            assert.equal(log.event, "Transfer", "unexpected event");
            assert.equal(log.args.from.valueOf(), sender.address.valueOf(), "unexpected from address");
            assert.equal(log.args.to.valueOf(), reciver.address.valueOf(), "unexpected to address");
            assert.equal(log.args.value.valueOf(), amount.valueOf(), "unexpected amount");