5

After waiting a while, my wallet did no longer allow to promote my transaction and forced me to reattach.

That forced me into reattaching the transaction, in the process I "doomed" three other non-zero transactions attached to mine. I waited over an hour with reattaching...

Why does my wallet not allow me to promote? Is there any reason - as long as a transaction can still confirm - to not promote them, even if they are already a few hours/days old? After all this doesn't "doom" transactions and requires far less POW.

2
  • Would you mind posting your transaction hash of the "original" so that we have a live example to explain on?
    – mihi
    Commented Dec 27, 2017 at 12:13
  • Can't find it anymore, I deleted the seed after donating the iota on it. I don't think this is necessary at all to have one Commented Dec 27, 2017 at 15:26

1 Answer 1

4

When you select a transction in your wallet, the wallet will ask your connected node if it considers the transaction bundle still consistent. A transaction bundle can become inconsistent if one of its two approving transactions (which were chosen at the time when you initially attached your transaction) are double-spends (or reattachments) of already confirmed transactions, or if they themselves are inconsistent because one of their appoving transactions are double-spends or attachmetns. That means that your transaction (and everything attached to it) is already "doomed" and the only way for you (and the other transactions attached to it) to get your transaction confirmed is to reattach.

(I have seen reports on slack where people claim that their transaction cannot be promoted although there was no obvious reattached transaction found in its approved transactions (down to the point where they got confirmed). So far I think this has not been able to be reproduced (since those people reattachedd their transaction before someone could have a look at it), but it could as well be that there is a bug in either the wallet or the full node that may result in wrong decisions in rare cases (perhaps try changing node when it happens the next time?). So far this is only speculation, though.)

5
  • I think the latter one was the case for me. I checked the trunk and batch transaction, wasn't a double spend apparently (at least the bundles weren't reattached anywhere). Commented Dec 27, 2017 at 15:28
  • It really seems to happen from time to time. My wallet forced me to instantly reattach this one today thetangle.org/bundle/… . Wanted to promote as POW took long (PC installed Updates in background). Digged in the explorer, no conflict found Commented Dec 28, 2017 at 23:26
  • thetangle.org/transaction/… (last of bundle)'s trunk points to thetangle.org/transaction/… whose branch points to thetangle.org/transaction/… whose trunk points to thetangle.org/transaction/… whose trunk ...
    – mihi
    Commented Dec 28, 2017 at 23:35
  • ... points to thetangle.org/transaction/… (a mineiota.com transaction whose reattachment got confirmed)
    – mihi
    Commented Dec 28, 2017 at 23:35
  • Okay, I didn't look back that far. The only question that stays is whether it confirmed before I had to reattach. We'll probably never know. Commented Dec 29, 2017 at 9:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.