Skip to content
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

Differing status of transactions being confirmed between maker, taker, and arbitrator #2045

Closed
devinbileck opened this issue Dec 4, 2018 · 6 comments
Assignees

Comments

@devinbileck
Copy link
Member

After mentioning this to @ManfredKarrer, he clarified the confirmation is only available for the transactions of your own wallet. The peers transaction is unknown to you and BitcoinJ does not know the confirmation state.

However, as it is shown, this is confusing and I have wondered in the past why my trading peers transaction has not been confirmed. It would be ideal to have a UI solution. Even if that involves showing an icon indicating it is unknown.

Maker:
image

Taker:
image

Arbitrator:
image

@ManfredKarrer
Copy link
Member

We should find an icon representing the information that the confirmation state for the peers transaction is unknown (as expected).

@ripcurlx
Copy link
Contributor

ripcurlx commented Dec 4, 2018

@pedromvpg Could you come up with an icon for this use case?

@stale
Copy link

stale bot commented Mar 4, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@ManfredKarrer
Copy link
Member

I think that should still be kept open.

@stale
Copy link

stale bot commented Jun 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the was:dropped label Jun 2, 2019
@stale
Copy link

stale bot commented Jun 9, 2019

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@stale stale bot closed this as completed Jun 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants