# Feature request: manually set max time to execute trade **URL:** \ **Category:** Development\ **Created:** [January 13, 2019, 11:10pm UTC](https://bisq.community/t/feature-request-manually-set-max-time-to-execute-trade/6915 "2019-01-13T23:10:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![KramerAssMan](https://bisq.community/letter_avatar/kramerassman/32/6_22734026db12803ebb3e059622ac3534.png) [@KramerAssMan](https://bisq.community/u/KramerAssMan)\ **Post date:** [January 13, 2019, 11:10pm UTC](https://bisq.community/t/feature-request-manually-set-max-time-to-execute-trade/6915/1 "2019-01-13T23:10:53Z")
Having a 24-hour window to execute (or alternatively, to abandon) a trade creates a lot of risk for those selling cryptocurrencies, because the prices are so volatile. Sure, you can price that risk, but buyers won’t necessarily understand why prices are 10-30% higher than other markets, and they’ll probably just bail on Bisq if that is the solution. One alternative would be to let the seller limit the amount of time available to execute a trade. For example, on [localbitcoins.com](http://localbitcoins.com), this defaults to 90 minutes. Even this is too long in many cases. Bitmex did some research on this (obviously they have a vested interest in discouraging the use of any DEX at the expense of their service, but that does not ipso facto invalidate their arguments): > **[Atomic Swaps and Distributed Exchanges: The Inadvertent Call Option | BitMEX...](https://blog.bitmex.com/atomic-swaps-and-distributed-exchanges-the-inadvertent-call-option/)** > > Abstract: In this piece, we look at a common problem facing both distributed exchanges and cross-chain atomic swaps: what we call the “inadvertent call option.” Non-custodial fully-distributed trading systems often inadvertently create an... This has also been raised on this forum: > [@Bitmex research about "inadvertent call option" in Bisq](https://bisq.community/t/bitmex-research-about-inadvertent-call-option-in-bisq/6870): > > Bitmex research has published an interesting article: [https://blog.bitmex.com/atomic-swaps-and-distributed-exchanges-the-inadvertent-call-option/](https://blog.bitmex.com/atomic-swaps-and-distributed-exchanges-the-inadvertent-call-option/) Here are my comments to the article: They made some mistakes when they descibed the trade protocol but for the option trade topic that is not relevant. E.g. there is only one atomic deposit tx where the funds of both traders (trade amount + security deposits of buyer and seller) go in. When a maker creates an offer no funds are locked up but only r… ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/6_22734026db12803ebb3e059622ac3534.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [January 14, 2019, 6:13am UTC](https://bisq.community/t/feature-request-manually-set-max-time-to-execute-trade/6915/2 "2019-01-14T06:13:28Z")
@KramerAssMan , Thanks for your input. The best if you are interested with this idea is probably to submit it as a proposal on Bisq’s github -\> [https://github.com/bisq-network/proposals](https://github.com/bisq-network/proposals) It will then be discussed. And may be implemented if there is a majority of contributors in favor of it. ---
**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\ **Post date:** [January 14, 2019, 6:21am UTC](https://bisq.community/t/feature-request-manually-set-max-time-to-execute-trade/6915/3 "2019-01-14T06:21:29Z")
This is why you can set a custom security deposit to as high as you want, to mitigate the risk. Trader is obligated to followup on the trade when he takes the offer and if he doesn’t the other trader can get his security deposit as a collateral. This feature could still be useful, but higher security deposits should solve this problem just as well.