bisq-network / bisq-network/bisq2
Handle better the case where market price deviation is too big
Open
improvement
trading
- Dominant language
- Java
- Stars
- 318
- Forks
- 120
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 43
Description
At the moment we throw an error and only the maker gets the reason of why the error happened in the first place. We should handle this better, perhaps allowing the maker to decide whether to proceed or not, so applying the same system as in #2017.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the requested behavior with issue #2017 and tracing how the current market-price-deviation error is handled. Clarify the maker's decision flow and define completion as letting the maker decide whether to proceed after the deviation is reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100