Or did you take the receiving wallet (B) private key and created a code that once the timelock was broadcast it automatically swept the BTC being received from Wallet B from Wallet A? The BTC would have to be in wallet B already otherwise a transaction could not be created with an empty address
The idea was to be able to do this:
I wouldn't mind creating a cronjob that tries to broadcast a bunch of transactions every minute. Once it's accepted by the network, bitcoind (which I have running anyway) will broadcast it.
So, in yogg's time locked case: You already have a time locked transaction, which can't be broadcasted yet. You use this transaction to create a child transaction that sends the funds to your own wallet (this transaction also can't be broadcasted yet).
Then, by trying to broadcast those transactions every minute, both will get broadcasted the moment it's possible and your funds are swept as fast as possible.
And none of this is useful in cases where the scammer kept the private key which can bypass the time lock.If you still have a future time lock pending, let's try this for real
LOyce...thanks for the reply...that is interesting so from what I understand is this...
By using a child transaction you are increasing the fees to have it confirmed faster.?..but it still will end up going to the same private key of when it was forged in the original timelock transaction....correct? Just faster as far as confirmations go.
But I have been able to rebroadcast bitcoin without any confirmations when sending from wallet to wallet.
But bottom line is, if a person just has a raw hex transaction....and no wallet A or Wallet B, then there is no way in hell that that can be altered.
Still its good to know you were able to do it if I understood correctly
P.S. is it also called a child pays for parent?