Quote from: NeuroticFish on June 28, 2019, 08:57:30 AM

Quote from: stompix on June 28, 2019, 08:54:22 AM

You just got unlucky!
Really really unlucky!!

Twice unlucky.
The recommended fee has dropped less than 1h ago to 12 satoshi/byte and 1-2 new blocks would have probably gotten his transaction.
Now another wave is on and the recommended fee is 122 sat/byte.

Now I hope you guys jinx it. The new wave of transaction doesn't seem to be coming down or lying low for the next few hours. Mempool seems to be pretty much adding up new transactions faster than miners can clear it. Well at this rate, OP would just want to hope for the best and wish that some miners out there would include his transaction, though I doubt it knowing that his tx is already deep within the mempool already. Just like what stompix said, a CPFP tx would do the trick.

Or try what DannyHamilton stated here (warning: huge block of text):

Quote from: DannyHamilton on May 24, 2017, 03:05:53 AM

Quote from: letitbegood on May 23, 2017, 11:11:01 PM

I've been trying to use the accelerator but am continually getting the message "Submissions are beyond limit. Please try later."

The accelerator only allows 100 free accelerations per hour. They reset at the beginning of the hour. This means you need to attempt your acceleration withing the first minute or so of the hour. After that 100 other people will have already used up the 100 slots.

In case your clock isn't set identically to theirs, I'd suggest trying at about 2 minutes before the beginning of the hour, and then re-trying every 15 seconds or so until a few minutes after the beginning of the hour. You should succeed during one of those attempts.

Quote from: letitbegood on May 23, 2017, 10:38:50 PM

since this transaction was a BTC purchase through the Glidera exchange, does anyone know what would happen if the transaction does not get confirmed and gets kicked back out?

Transactions never get "kicked back out". Some nodes, miners, and mining pools may choose to forget the transaction after a while if it hasn't confirmed yet, but if you store the raw transaction somewhere you can always re-broadcast it yourself to remind them until it finally confirms. If you don't do that, then you'll have to contact Glidera to find out what they do about unconfirmed transactions. Perhaps they'll re-broadcast. Perhaps they'll send a new transaction. Perhaps they'll steal your money and tell you "tough luck". I can't predict what someone else will do.

Quote from: letitbegood on May 23, 2017, 08:24:24 PM

1. With CPFP, do I need to spend ALL of the unconfirmed funds, or just make sure that SOME of the uncomforted funds are being used?

You just need to use the unconfirmed transaction output as an input to the fee paying transaction. How much of that input you send elsewhere and how much you just send to a different address in your same wallet is entirely up to you.

Quote from: letitbegood on May 23, 2017, 08:24:24 PM

2. I understand that I need to make sure a high enough fee is being paid to cover both transactions, but do I also factor in the .0003164 BTC on the unconfirmed transaction as part of the total amount when considering how much more to send ? In other words, if I wanted to make sure the fee on each transaction was .0004164 BTC, would I send 2x this amount, or would I send .0004164 BTC for the child transaction plus an additional 0.0001 BTC for the parent transaction (since .0003164 is already included in the original transaction)?

Generally miners that implement CPFP properly would add up the total bytes from both transactions and the total fees from both transactions. Then they'd calculate the fees paid per byte and compare to the fees per byte of all the other transactions (both other CPFP and other non-CPFP). The transaction (or set of transactions) that get the miner the highest profit (most fees per byte) would then get confirmed.

If you decide later that you need to re-broadcast the transaction, here is the raw transaction:

Code:

0100000001dc2736bf4834fec9d7f5fc8930f34402a264f0a2f73e67c49a4099d75f16db6b010000006b483045022100b55d29a8e5e514a3636bfd072a986fde1014a45ad3e99164bdde363190d853fd0220576dfdf5d49efdc8cc30e72a2a8abe1a7498b648ac455d8605acc23cbcb22ed10121025834c58e5c1aae14e66a669e4b342a1e498258d0a6a5013f86c6535f2ac2e42affffffff0248e4d200000000001976a914cf41ac8d5d0cd15470cb64aa426bad1436bb2f2388acf0d2fe01000000001976a9148968a3751be6bf8446cbf93623a00968b21e187d88ac00000000

https://blockchain.info/rawtx/8f46d46df82a4200e86e485653d725eab567043bbb008688aff964ab26db6197?format=hex