{"action":"opened","issue":{"url":"https://api.github.com/repos/iotaledger/wallet/issues/1148","repository_url":"https://api.github.com/repos/iotaledger/wallet","labels_url":"https://api.github.com/repos/iotaledger/wallet/issues/1148/labels{/name}","comments_url":"https://api.github.com/repos/iotaledger/wallet/issues/1148/comments","events_url":"https://api.github.com/repos/iotaledger/wallet/issues/1148/events","html_url":"https://github.com/iotaledger/wallet/issues/1148","id":299202058,"number":1148,"title":"wallet feature request: double spending check during the reattach/promote","user":{"login":"xiongzm","id":3974899,"avatar_url":"https://avatars1.githubusercontent.com/u/3974899?v=4","gravatar_id":"","url":"https://api.github.com/users/xiongzm","html_url":"https://github.com/xiongzm","followers_url":"https://api.github.com/users/xiongzm/followers","following_url":"https://api.github.com/users/xiongzm/following{/other_user}","gists_url":"https://api.github.com/users/xiongzm/gists{/gist_id}","starred_url":"https://api.github.com/users/xiongzm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xiongzm/subscriptions","organizations_url":"https://api.github.com/users/xiongzm/orgs","repos_url":"https://api.github.com/users/xiongzm/repos","events_url":"https://api.github.com/users/xiongzm/events{/privacy}","received_events_url":"https://api.github.com/users/xiongzm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-22T02:35:56Z","updated_at":"2018-02-22T02:35:56Z","closed_at":null,"author_association":"NONE","body":"\r\nIt seems that the wallet right now can detect the double spending when the node can detect it, however, at some cases the wallet/IRI can't detect the potential double spending, for example, the double spending is ongoing within a very short time window with different full node connection, those different full nodes don't have the exact same full tx history because of the different local view, so right now double spending was done and the other node didn't detect the double spending. One of the double spending was confirmed, and of course the other double spending won't be confirmed. But the average people don't know the details of the double spending, he will repeat conduct reattachment and promote, that won't take any effect for the confirmation and that double spending won't be confirmed forever. \r\n\r\nSo I request the wallet feature: before the actual reattachment and promote start, please check whether the tx is a double spending tx, if that is a double spending, warn the user and stop the further reattachment.\r\n\r\nThe following is an actual case on the tangle that I described the above: https://thetangle.org/address/9UDCMLBAZERCRQUIHBOHMUNTPNRGDCEU9KSXKPJYSGLV9MYQOLFWZHNOFEQUXCDMILXFTKBWEYBVVBXNW\r\n"}}
{"actor":{"display_login":"xiongzm"}}