feat: (txsink) add tx sink deny list implementation and add new server component for it #1782
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What ❔
TxSinkDenyList
component and can be added when launch the server.For running server with the deny list tx sink, should execute
And in the env files (i.e. dev.env) should add
TX_SINK_DINY_LIST="deny addresses separated by comma"
Why ❔
We need a mechanism to be able to block some addresses has potential attack/hack risks through L2 transactions, i.e. blocking fund withdraw from L2 to L1 or other factors.
Checklist
zk fmt
andzk lint
.zk spellcheck
.zk linkcheck
.