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

UI issue in context menu on the Transactions tab of the QT wallet #6124

Open
kxcd opened this issue Jul 17, 2024 · 2 comments
Open

UI issue in context menu on the Transactions tab of the QT wallet #6124

kxcd opened this issue Jul 17, 2024 · 2 comments
Assignees

Comments

@kxcd
Copy link

kxcd commented Jul 17, 2024

When receiving a transaction in the QT wallet, before an ISD_Lock is detected (ie unconfirmed TX), if one right clicks on the transaction, the context menu that appears has the Resend Transaction option enabled, this seems weird to me, since this wallet cannot rebroadcast this transaction and instead needs to wait for it to be confirmed, or am I misunderstanding something?

Expected behavior

Too see this option disabled for incoming transactions. It should only be enabled for TXes this wallet has sent and that are neither ISD locked, NOR chainlocked.

Actual behavior

The bad stuff, it's enabled and clicking it doesn't appear to do anything at least in the UI.

To reproduce

Send this wallet a TX and observe the context menu before the ISD hits.

System information

Discovered on Windows QT wallet, v20.1.1.

I didn't check the debug.log.

image

@knst
Copy link
Collaborator

knst commented Jul 17, 2024

wallet cannot rebroadcast this transaction and instead needs to wait for it to be confirmed

Wallet can re-broadcast transaction. By default re-broadcasting intervals are pretty long for security reasons (random between 1 and 3 hours), so, if you click this button it would quitely (without any gui alerts) just re-transmit transaction to know peers immediately.

It can be useful, if you sent transaction, but you don't see it on other peers, no IS lock on it, etc - maybe the peers who received your transaction just censured it or went to offline, or your node has been with poor connection, etc

@babi-1097
Copy link

When a transaction is received but not yet confirmed, it means it is still waiting to be included in a block on the blockchain.
Specific to certain cryptocurrencies like Dash, this lock signifies that a transaction has been verified and locked by the network, providing near-instant confirmation.
Your wallet does not have the ability to rebroadcast an incoming transaction because it was not originally broadcasted by your wallet.
The transaction simply needs to be confirmed by the network which is out of your wallet's transaction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants