the TransferBatch event emits the wrong address under certain conditions
The transferBatch event is emitted but does not emit the correct address in case a call is executed via blueprint on behalf of the publisher.
as we can see above, the msg.sender is the address that is emitted in the first parameter. But this is not true in all cases. To be more specific, during blue print execution a user is executing on behalf of a publisher, so having the msg sender be the first param of the event will be erroneous.
When executing via blueprint the event will emit the incorrect address.
manual reveiw
instead of use msg.sender, the code needs to use LibTractor._user() to make sure the correct address operator is emitted in event emission if the call is executed during blueprint when the caller executes call onhalf of the publisher.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.