-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add protection tools to offer #5051
Add protection tools to offer #5051
Commits on Jan 4, 2021
-
Do not shutDown with CloseConnectionReason.PEER_BANNED if we received a
CloseConnectionMessage as it would trigger a wrong log on the peers side, that he got banned.
Configuration menu - View commit details
-
Copy full SHA for b013503 - Browse repository at this point
Copy the full SHA b013503View commit details -
Configuration menu - View commit details
-
Copy full SHA for 456d1f8 - Browse repository at this point
Copy the full SHA 456d1f8View commit details -
Improve logging of received data
The numbers did not match up from delivered response size and items as we did not count in the overhead of the ProtectedStorageEntry (pub key+sig) and did estimate the size with taking only first item and multiplying it. A measurement resulted in 20 ms costs for the exact calculation (toProtoMessage().getSerializedSize() has some costs). I guess that is acceptable to get correct metrics.
Configuration menu - View commit details
-
Copy full SHA for a7127d4 - Browse repository at this point
Copy the full SHA a7127d4View commit details -
Configuration menu - View commit details
-
Copy full SHA for ac8711c - Browse repository at this point
Copy the full SHA ac8711cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1ef086a - Browse repository at this point
Copy the full SHA 1ef086aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 79a0874 - Browse repository at this point
Copy the full SHA 79a0874View commit details -
Configuration menu - View commit details
-
Copy full SHA for e868050 - Browse repository at this point
Copy the full SHA e868050View commit details -
Configuration menu - View commit details
-
Copy full SHA for fbfd95b - Browse repository at this point
Copy the full SHA fbfd95bView commit details -
Configuration menu - View commit details
-
Copy full SHA for de5b69a - Browse repository at this point
Copy the full SHA de5b69aView commit details -
If we select TransferWise we switch to show all
currencies as TransferWise supports sending to most currencies.
Configuration menu - View commit details
-
Copy full SHA for e73b6b0 - Browse repository at this point
Copy the full SHA e73b6b0View commit details -
Add option in preferences to hide payment methods which are not part …
…of the users accounts. Default value is false, so same behaviour as before the change. If no payment account is setup then we also show all payment methods. In that case (no payment account) we disable the toggle as well as set it to false.
Configuration menu - View commit details
-
Copy full SHA for 82644fc - Browse repository at this point
Copy the full SHA 82644fcView commit details -
Extract methods for show all and edit entries.
Use isShowAllEntry methods instead of equals checks
Configuration menu - View commit details
-
Copy full SHA for 039d8fb - Browse repository at this point
Copy the full SHA 039d8fbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 645594f - Browse repository at this point
Copy the full SHA 645594fView commit details -
Configuration menu - View commit details
-
Copy full SHA for b0f54d4 - Browse repository at this point
Copy the full SHA b0f54d4View commit details -
Add denyApiTaker entry to extra field map.
We cannot add a field to OfferPayload as we use the hash for signing and any change would break compatibility between diff. versions. We also cannot rename one of the un-used fields as we use json for creating the contract hash and that would fail in the trade then.
Configuration menu - View commit details
-
Copy full SHA for 9a47a83 - Browse repository at this point
Copy the full SHA 9a47a83View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7a8e863 - Browse repository at this point
Copy the full SHA 7a8e863View commit details -
Configuration menu - View commit details
-
Copy full SHA for aaef64b - Browse repository at this point
Copy the full SHA aaef64bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 78282af - Browse repository at this point
Copy the full SHA 78282afView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0ae5006 - Browse repository at this point
Copy the full SHA 0ae5006View commit details -
Add support for isApiUser and check in OpenOfferManager
Calls from the API set the flag to true, from the desktop its false. If offer has denyApiUser enabled the offer availibility check fails. @ghubstan: I set the value in CoreApi and not directly in the CoreTradesService, so keep it more open that those sub domain classes can be used from desktop as well. Not sure if is not intended/permitted for some reason but I though that way we have more flexibility. Feel free to remove the param and set it directly in CoreTradesService if that class will never be used from non-api code.
Configuration menu - View commit details
-
Copy full SHA for 18e4a39 - Browse repository at this point
Copy the full SHA 18e4a39View commit details -
Refactor checks for take-able offers
Extract to OfferFilter method. Use enums for return values so the view can show the matching popups.
Configuration menu - View commit details
-
Copy full SHA for 400a736 - Browse repository at this point
Copy the full SHA 400a736View commit details -
Add
getOffersAvailableForTaker
method@ghubstan: If the `offerFilter.canTakeOffer` call can be included into `getOffers(String direction, String currencyCode)` and maybe also in `getOffer(String id)` we can remove the `getOffersAvailableForTaker` method.
Configuration menu - View commit details
-
Copy full SHA for 2a94810 - Browse repository at this point
Copy the full SHA 2a94810View commit details -
Configuration menu - View commit details
-
Copy full SHA for dacdd8f - Browse repository at this point
Copy the full SHA dacdd8fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7a76035 - Browse repository at this point
Copy the full SHA 7a76035View commit details -
Configuration menu - View commit details
-
Copy full SHA for e2d386e - Browse repository at this point
Copy the full SHA e2d386eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9d3fd03 - Browse repository at this point
Copy the full SHA 9d3fd03View commit details -
Configuration menu - View commit details
-
Copy full SHA for a49505d - Browse repository at this point
Copy the full SHA a49505dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 76022c0 - Browse repository at this point
Copy the full SHA 76022c0View commit details -
Remove OfferPayload.DENY_API_TAKER and use preferences
flag instead. If we would store the flag in the offer we would need to update all offers if the preferences flag changes.
Configuration menu - View commit details
-
Copy full SHA for 2695415 - Browse repository at this point
Copy the full SHA 2695415View commit details -
Configuration menu - View commit details
-
Copy full SHA for d402496 - Browse repository at this point
Copy the full SHA d402496View commit details -
I would not make sense that the API user has set the preferences to not accept API taker for their offers. This was from the older version where we used the offer to carry the flag. @ghubstan Api user cannot see if an maker has set the flag but will receive an error at offer availibility check.
Configuration menu - View commit details
-
Copy full SHA for c68c0ed - Browse repository at this point
Copy the full SHA c68c0edView commit details