feat(protocol): remove banning address

[dantaik]

Banning an address serves as a preventative measure to restrict specific addresses from being targets of cross-message communication. Currently, I have not identified clear use cases for this feature. Considering that several auditors have inquired about which addresses should be banned, it may be prudent to eliminate this feature to prevent such recurring questions.

[openzeppelin-code]

feat(protocol): remove banning address

Generated at commit: 0d4135b22b96c0f000f8ce144b1a2997b79eab8b

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	2 2 0 3 39 46
Dependencies	Critical High Medium Low Note Total	0 0 0 0 0 0

---

For more details view the full report in OpenZeppelin Code Inspector

[adaki2004]

Banning an address serves as a preventative measure to restrict specific addresses from being targets of cross-message communication. Currently, I have not identified clear use cases for this feature. Considering that several auditors have inquired about which addresses should be banned, it may be prudent to eliminate this feature to prevent such recurring questions.

It was (mainly) about SignalService, right ? Not to construct a fake message on behalf of the bridge.
For now it is safe to remove IMO, but we need to be careful when we:

• Dont want bridge to be msg.sender: SignalService
• We want bridge to be msg.sender: ERC20Vaults (see onlyFromBridge)

For now, i think it is safe.