Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

Orderbook bomb [DoS] #298

Closed
dcousens opened this issue Nov 1, 2015 · 2 comments
Closed

Orderbook bomb [DoS] #298

dcousens opened this issue Nov 1, 2015 · 2 comments
Milestone

Comments

@dcousens
Copy link

dcousens commented Nov 1, 2015

!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook!orderbook

1 message for me, m * n responses from others.

We should probably penalize users who do things like this?

@dcousens
Copy link
Author

dcousens commented Nov 1, 2015

Perhaps we could [at least] rate limit !orderbook commands, given their broadcast nature.
We should probably also penalize users if a command is unexpected and repeated.

@AdamISZ
Copy link
Member

AdamISZ commented Dec 14, 2015

See #361 - this addresses this issue, BUT only in the very limited sense as mentioned in #343 , namely, "prevent crash/DOS in case of someone's bug". Attempting to address this in terms of punishing bad behaving counteparties is in the scope of 0.2.0 according to the taxonomy of that issue, because it doesn't make too much sense as long as counterparties are almost entirely 'weightless', as they are today.

@AdamISZ AdamISZ closed this as completed Dec 14, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants