I sent payment using funds from an unconfirmed transaction and now I'm stuck!

[lokster72]

Hi, any help will be greatly appreciated.

I RECEIVED a payment.  When it was still an unconfirmed transaction I use part of it, to MAKE a payment.  I think it is this connection that is causing the problem.  Both payments remained unconfirmed for almost 3 days and Blockchain cancelled them.  The monies were returned but within minutes there was an automatic resend of both transactions (which I didn't want).  Now the same is happening again....no propagation and no confirmations.  I am concerned that after another 3 days Blockchain will cancel the transactions again, and another automatic resend will happen and i'll be stuck in an endless loop.  I know the sender and I don't need the received payment.  And I would just MAKE a payment.  Please help, I don't know what to do.
Many thanks
Lok   

[--Encrypted--]

stick to one thread, please. if your tx gets dropped again it'll be returned to the sender for good. that is unless the sender is continuously rebroadcasting it. this happens automatically with core so if the sender is using core ask him to delete the unconfirmed tx.

[cr1776]

What software are you using?  Are you using blockchain.info to do the sends or just using them (assuming that is what you meant by blockchain) to check the status?
 

Hi, any help will be greatly appreciated.

I RECEIVED a payment.  When it was still an unconfirmed transaction I use part of it, to MAKE a payment.  I think it is this connection that is causing the problem.  Both payments remained unconfirmed for almost 3 days and Blockchain cancelled them.  The monies were returned but within minutes there was an automatic resend of both transactions (which I didn't want).  Now the same is happening again....no propagation and no confirmations.  I am concerned that after another 3 days Blockchain will cancel the transactions again, and another automatic resend will happen and i'll be stuck in an endless loop.  I know the sender and I don't need the received payment.  And I would just MAKE a payment.  Please help, I don't know what to do.
Many thanks
Lok   

[lokster72]

Thanks for you response.   Yes using blockchain.info for sends.  I really want to stop a rebroadcast when the transactions are rejected, so a re-attempt isn't make for the 3rd time

What software are you using?  Are you using blockchain.info to do the sends or just using them (assuming that is what you meant by blockchain) to check the status?
 

Hi, any help will be greatly appreciated.

I RECEIVED a payment.  When it was still an unconfirmed transaction I use part of it, to MAKE a payment.  I think it is this connection that is causing the problem.  Both payments remained unconfirmed for almost 3 days and Blockchain cancelled them.  The monies were returned but within minutes there was an automatic resend of both transactions (which I didn't want).  Now the same is happening again....no propagation and no confirmations.  I am concerned that after another 3 days Blockchain will cancel the transactions again, and another automatic resend will happen and i'll be stuck in an endless loop.  I know the sender and I don't need the received payment.  And I would just MAKE a payment.  Please help, I don't know what to do.
Many thanks
Lok   

[lokster72]

Many thanks for your response.  The sender of the 1st transaction and myself for the 2nd transaction both use blockchain.info   I’m assuming that we must use core as the when the transactions failed the 1st time they were both resent within a matter of minutes.  How I do check we are using core, and if we are, how do I stop a re-broadcast?    One thing that might be relevant - Earlier today just before the transactions were rejected I was asking for help on the forum and others said they were re-broadcasting.  Could this be the reason why a re-attempt was made?  Thanks for your help

stick to one thread, please. if your tx gets dropped again it'll be returned to the sender for good. that is unless the sender is continuously rebroadcasting it. this happens automatically with core so if the sender is using core ask him to delete the unconfirmed tx.