While debugging rollkit #1036 I came across a potential DOS vector.
Since celestia-node calls the blocking method BroadcastTx
on celestia-core which itself blocks
on transaction subscription events, a potential
adversary can repeatedly trigger a maliciously blocking transactions so that the RPC endpoint has to queue other valid transaction,
timing them out as well. This is a potential DOS vector.
Example of a malicious transaction - submit a max size blob - this seems to timeout on testnet with:
2024/01/26 01:56:14 code = Unknown desc = timed out waiting for tx to be included in a block