pull down to refresh

Here's what I did: I created a robot. I accepted a seller's offer. I did nothing once the qr code appeared. I checked the open offers page and it wasn't there.
Now, I got bored pretty quickly and deleted the robot. Maybe you can only use this delaying tactic for a short period of time? I don't know.
Here's what I did: I created a robot. I accepted a seller's offer. I did nothing once the qr code appeared. I checked the open offers page and it wasn't there.
Now, I got bored pretty quickly and deleted the robot. Maybe you can only use this delaying tactic for a short period of time? I don't know.
It should just keep the order public until any taker lock the bond. Please contact your coordinator if you notice such behaviour again!
reply
Yes. This makes perfect sense. Is this a new policy that was implemented as a result of the situation described by the OP? It seems like an obvious solution. I can't believe it always hasn't been this way.
reply
Yeah, there was one user that attacked the orderbook by hiding orders similar to his. He used a script that created new robots and took orders in a loop without paying the bond.
I say one user, because the currency, payment method and amounts hidden were always the same.
Since version 0.7.5 this attack does not work anymore since the orders remain public until the bond is payed.
reply
It's logical.
reply