-
Notifications
You must be signed in to change notification settings - Fork 71
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
Bisq Easy protocol improvements #1569
Bisq Easy protocol improvements #1569
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NACK
The use case where the seller sends the account data first triggers for the buyer the change to step 2 thus he cannot send the btc address.
c72703d
to
fbb8afd
Compare
* Remove logic to decide next step * Add all the combinations to cover explicitly all possible states a seller can encounter
* Add all the combinations to cover explicitly all possible states a buyer can encounter
fbb8afd
to
0b83d6f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
I do not have time atm for an in depth testing/review but the PR looks good to me.
When testing all scenarios its important to also test the cases that peers are offline at any state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Based on #1566