Emergency processing can be blocked in Pull Pattern
The main reason for the emergency processing mechanism is that there is a chance that some token transfers might be blocked. For example, a sender or a receiver is in the USDC blacklist. Emergency processing saves from this problem by not transferring tribute token back to the user (if there is some) and rejecting the proposal.\\n```\\nif (!emergencyProcessing) {\\n    require(\\n        proposal.tributeToken.transfer(proposal.proposer, proposal.tributeOffered),\\n        "failing vote token transfer failed"\\n    );\\n```\\n\\nThe problem is that there is still a deposit transfer back to the sponsor and it could be potentially blocked too. If that happens, proposal can't be processed and the LAO is blocked.
Implementing pull pattern for all token withdrawals would solve the problem. The alternative solution would be to also keep the deposit tokens in the LAO, but that makes sponsoring the proposal more risky for the sponsor.
```\\nif (!emergencyProcessing) {\\n    require(\\n        proposal.tributeToken.transfer(proposal.proposer, proposal.tributeOffered),\\n        "failing vote token transfer failed"\\n    );\\n```\\n