The member ( where the quota needs to be kept track of ) of the pinning request can be figured out from the transaction itself ( the sender of the transaction is either a member , or the contract address that emmitted the event is a member of the consortium )
The member ( where the quota needs to be kept track of ) of the pinning request can be figured out from the transaction itself ( the sender of the transaction is either a member , or the contract address that emmitted the event is a member of the consortium )
This logic can all be inspected from the proxy.
Skipping this saves gas cost on the event.