Well, the address is still funded, but only the one in posession of the private key can move the funds... There is no way of telling wether the owner is just keeping low and wants to sell this BTC later, or maybe he lost the keys, or maybe he's just an honest guy and he's waiting for his clients to contact him... Like i said: many possibility's and no way of knowing the truth.

Here you go: quoted that for you

In that case, you were robbed.
I didn't dig into the thread posted by AdolfinWolf, but after reading the last page, it looks like the owner's identity was known, but he pulled an exit scam? It also looks like he was never suid for what he did???

7.5 BTC is about $100.000 at current preev rate... I'd probably look into verifying the owner's identity and find myself a good lawyer if i were you...

The first two points are the most important... Bitcoin exists as a decentralised payment system without central authority.
If we would "steal" satoshi's coins (or at least, add the value of the unspent outputs we THINK are satoshi's to the block reward), it would be a very bad precedense.
From then on out, your balance would never be safe again... If we, as a community, did this (even once), what would stop us from voiding the unspent outputs belonging to a central bank, or maybe steal the unspent outputs from all addresses we believe are BTC hoarders?

I'm sorry to tell you, bit if BTCquick was an online wallet, and it has dissapeared, the only thing you can try is to find the person responsible for this wallet and hope he kept backups.

blockchain.info is just a private company, they're not a central authority that keeps track of all wallets. If you created an online wallet with a certain, disapeared, company, they cannot help you... The only one that can help you is the one that had access to the private keys from btcquick.

blockchain.info is an independant website... They run a couple of network nodes, but they're not the owner of bitcoin or the blockchain technology.
This transaction is unconfirmed... Which means it only exist in the mempool of part of the network's nodes. For some reason, the nodes of blockchain.info don't have your transaction in their mempool.

You shouldn't worry about this... Either blockchain.info has a bug in it's code, or your transaction didn't propagate completely... It's possible the transaction didn't propagate because it has some problems, but i didn't look into this. On the block explorer you linked to, you can actually see the transaction has a low confidence and low miner preference... So it's probably having a low fee or dust outputs...

Question 1:
This transaction depends on an unconfirmed transaction, it can only be confirmed once the parent is also confirmed.
You can either pay for an acceleration service like viabtc.com, btc.com or f2pool.com, create a CPFP transaction paying the fees for the 3 transaction (the parent transaction, your transaction, and the CPFP transaction), wait it out while rebroadcasting the transaction, or demand that the exchange cleans up their mess.

Question 2:
Can't help you with the amount of information available, can you tell me if you're the sender/receiver and which wallet you used?

Question 3:
This is basically exactly the same problem as question 1, so the advice i gave this poster should also work for you

Question 4:
I saw that you posted right after my public service announcement, so i decided to move my public service announcement one post down and include your question to the final answer round, since the answer might also be interesting for other members

It's basically the other way around: a parent will never get stuck because it's child has a low fee... But if the parent has a low fee, and the child has a much higher fee (in sat/byte), the high-fee child might actually speed up the confirmation for the low-fee parent.
It's quite simple actually, a miner wants to maximise his revenue. He cannot add the high-fee child to his block if the parent is still unconfirmed. If he wants the big fee, he is forced to add both the child and the parent to his block... This is what is commonly known as a CPFP

It doesn't work the other way around: if the parent has a high fee, and the child has a small fee, a miner can just add the parent to his block, and he doesn't have to add the child... This way he maximises his income even more

Public service announcement: This weekend is christmas weekend... I have a week off next week so i won't be hanging around the forum quite as much as i usually do.
Since i'm providing a free selfhelp service in this thread (i'm not getting payed to do this, i have no affiliation with this forum, nor with any service i recommand, exept when i link to my own website), i'd like to have the weekend with my wife and kid, so i'll be locking this thread for NEW questions for at least a week.

If you have RUNNING requests, you can PM me for follow up questions (include the link to the post where you initially asked your question on my thread. PM's not clearly proving they're follow up questions will *probably* get ignored). I do not give any guarantees as to the timing of my replys to any PM's.

If any other longtime member with basic knowledge wants to take over this thread during my absense (well, not really absense, i'll be hanging around, just not as much as i did the last couple of weeks), i can unlock the thread upon their request in PM.

Any posts below this one will get ignored, or deleted... Whichever i fancy!

I just woke up this morning, and saw a lot of unanswered emails, PM's, replies on my blogposts and questions in this thread... I'll try to answer the questions i got in my thread in this post.

I'll be updating this post and adding more and more answers, so please check back untill your question has been answered.

I'd like to note that, since i seem to get a couple hundred help requests each week, i won't be able to spoonfeed any answers... I'll try to give everybody a push in the general direction to help them solve their problems by themselfs.
I no longer have the opportunity to push any transactions to any accelerator, this is something you'll have to do for yourself:

https://pool.viabtc.com/tools/txaccelerator/

Question 1:

It's confirmed... My help is no longer needed

Question 2:

Well, the sender seems to have cheaped out on the fee... Depending on the wallet you used to receive the BTC, you can do a CPFP... Could you tell me the wallet software you used to generate the receiving address?

Question 3:

Since you were using core, i can only assume you created the last couple of tx's while the fee was still in the ~400 sat/byte range, then closed your client? When you re-started your wallet, it didn't immediately knew the "correct" fee, so it used the last-known good fee, which was, at that point, to low...

To solve your problem, there are a couple of options:
1) wait it out and try to double spend the inputs of your stuck transaction... You already figured that out yourself . Since you're using core, you'll need to start up your core wallet. I just found out the wiki has a nice how-to: https://en.bitcoin.it/wiki/Fee_bumping#Bitcoin_Core_GUI (the first 9 steps are necessary for your wallet to stop broadcasting), i'd personally suggest to wait a couple of days after step 9 has been completed, that way your tx will have been pruned from the mempool of most nodes

2) It seems there was a change address.. That fact will allow you to do a CPFP:  you could potentially use the output funding your change address 1JpkfjEz1LsefQWayGHPFGfp1mnV1QjJLv  to create a new transaction with a fee that is high enough to pay the fee for both the stuck transaction (parent) and the CPFP transaction (child)

3) if you're really desperate, as a last resort, you can use the payed accelerator service of viabtc.com or btc.com or f2pool

4) do nothing but keep rebroadcasting the transaction... I really believe (but cannot know 100% sure) that at some point, the fee will once again drop. If you just keep rebroadcasting the transaction (with bitcoin core, just opening your wallet once a day should be sufficient), sooner or later it'll probably end up in a block without any interference

Question 4:

I have a hard time understanding your problem, but rebroadcasting is pretty simple and can even be done using online tools only
1) search your transaction on blockchain.info... Make sure the url is like this: https://blockchain.info/tx/c33be8f735d280826cd13dbdee0e286b6b7268c80998f7835537bf1e9a85ec96 (sample tx from an earlyer question)
2) add ?format=hex at the end of the url (sample: https://blockchain.info/tx/c33be8f735d280826cd13dbdee0e286b6b7268c80998f7835537bf1e9a85ec96?format=hex )
3) copy the raw transaction printed on the screen
4) google for "bitcoin transaction broadcast online", find a couple of nodes that offer a gui for transaction broadcasting. Timelord2067 even created a thread where he collects nodes that allow rebroadcasting transactions: https://bitcointalk.org/index.php?topic=1938621.0
5) just open the web gui's from step 4, paste the raw tx from step 3, submit and you're done


Question 5:

Well, i don't have a lot of knowledge about breadwallet, if you succeed in switching to a wallet i know, like electrum, i can potentially guide you trough the next steps. I don't know if breadwallet uses a seed, if you can export your private keys, or your xprv... I'd personally try to find the answer to this question using google.

As for your second question, there are 3 pools that offer an legit paying txacceleration service (i've never used a payed service myself, but i've read positive things about these pools):
pushtx.btc.com
https://pool.viabtc.com/tools/txaccelerator/
f2pool (you can contact them on bitcointalk by talking to macbook-air, the owner, or quickseller, a member with push privileges)

Question 6:
As a receiver, you're more or less bound to a couple options:
1) waiting it out while regularly rebroadcasting the tx (see question 4 for a howto)
2) creating a CPFP, which is pretty hard to do from an online wallet... I think you can switch from blockchain to electrum somehow. From electrum you can actually do this pretty easily. If you are unhappy with option 1, please try to move to electrum and ask me how to create a cpfp afterwards

Question 7:

Sorry to tell you, but it's basically the same answer as question 6... As a receiver, you can either wait it out while rebroadcasting a transaction, or do a CPFP, which is really hard to do from a web wallet... Is there a possibility to switch your wallet from the web wallet to electrum or core? I have no experience with those web wallets, so i don't know if it's an option

Question 8:

Sure, just for reference, in case anybody wants to try this at home, i'll give the necessary steps:
there is one input with a value of  2.2599 BTC :  "3c43248fb49c6041860610c32be5659039499bf3ccda43a28ccb2d47bf4353d4" vout 0
there are 2 outputs, funding addresses 1Nejxrk4Y9Q2eQ6YTd3hMi46uSnnN4Ghbn  and 3AbZaaKj4ZVomw4YKTTpraqQYbaesByTpJ
since the unspent output used for this tx is funding an address starting with 1, i can defenatly say it's not a segwit wallet without thinking twice
Some commercial interruption: i used my very own tool: https://www.mocacinno.com/page/feeestimate option 2, 1 input, 2 outputs, a "reasonable" fee is: 0.0017 BTC (it's not the best fee, but it should work)

So, we'll fund address 3AbZaaKj4ZVomw4YKTTpraqQYbaesByTpJ with 0.06418718 and we'll take the fee from the funding of address 1Nejxrk4Y9Q2eQ6YTd3hMi46uSnnN4Ghbn, so it should receive 2.2599 - (0.06418718  + 0.0017) = 2.19401282. I'm going to round this down to 2.194

From the command line

the resulting, raw, unsigned transaction is

Since i don't take responsability for any typos, you should run this unsigned tx trough a decoder before even attempting to sign it!
https://blockchain.info/decode-tx

In order to sign it with electrum, you should create an ascii file with a txn extension, and paste the following data into it:

Now, you should be able to go to tools => load transaction => from fille
Sign the transaction
Paste the transaction in a post and let me have a look before we broadcast

If this doesn't work, it might have something to do with the fact that i didn't try this procedure for quite a long time... It's possible you'll have to start up electrum in offline modus, but i can't remember from heart how to do this (info should be available in the electrum documentation, or questions can be asked in the electrum subforum)


Question 9:
Allways nice to see a followup, thanks for sharing

Question 10:

Well, the fee was reasonable, not really perfect i'm afraid... A fee this high gave you a good shot at getting a confirmation within a reasonable timeframe, but defenatly not a 95% chance... Calculating fees is maximising the odds of getting your transaction into the next x blocks... You had decent odds, but they were not optimal.

Question 11:
I can give you a few tips and pointers...
First of all, your transaction added a fee of 15 sat/byte while at this moment, a fee of >1000 sat/byte is optimal if you want a 95% chance of getting your tx in the next 3 blocks... So a transaction with this fee might take multiple months to confirm (if you keep rebroadcasting it).
Your non-technical options are rather limited
1) keep rebroadcasting the transaction (see question 4) and hope it'll *eventually* confirm
2) make sure the transaction is defenatly not rebroadcasted, wait a while, then try to restore your wallet on a different phone from backup and hope your wallet software "forgets" about the transaction. If it doesn't, it probably means that there is a record about this transaction stored in the backup, you can ask if there is a possibility to remove this record in the schildenbach wallet's subforum (i think it still exists).

The technical options could also work, but i don't know if they are possible using a mobile wallet... I think there is an option to export private keys from a schildenback wallet backup and import them into electrum or core... If you don't like the non-technical sollutions, i'd urge you to look into this option, as the technical sollutions actually need to be performed on a wallet i know (unless you find somebody else to help you with more intimate knowledge about the schildenbach wallet).
As a sender AND receiver, you can do the following things:
- double spend the inputs in a new transaction
- create a CPFP

Question 12:

Mycelium messed up, since this fee is defenatly not enough to have a decent chance of getting into any blocks the next couple of days/weeks... It's sufficient to get a confirmation *sometimes* tough, just don't hold your breath for it being any time soon.
Since the receiver is an exchange, the only thing you can do is from the sender point of view:
- there seems to be a change address, so you can attempt a CPFP
- you can double spend the unspent outputs used as an input for your transaction
- the tx isn't opt-in RBF, so you can't do that
- you can keep rebroadcasting the transaction and hope it'll *eventually* confirm
- you can stop rebroadcasting, save the raw tx (see question 4) "just in case", then try to restore your wallet in a couple of days, and hope mycelium will no longer show the stuck transaction and allows you to use the same unspent outputs to create a brand new transaction

In order to do a double spend or a CPFP, i think you'll need a decent desktop wallet... I don't think i can help you create one of these transactions using mycelium. Can you look into moving your wallet from mycelium to electrum or core?

Question 13:
I don't have time to wait for viabtc's tool to allow the next 100 free accelerations. I posted the link at the top of this post.
If you want more advice, please give me the information i need to put you on the right track (read the very first post of this thread)

Question 14:
I don't have time to wait for viabtc's tool to allow the next 100 free accelerations. I posted the link at the top of this post.
If you want more advice, please give me the information i need to put you on the right track (read the very first post of this thread)

Question 15:
I haven't had time to go trough your tutorial (yet), but any help i get is greatly appreciated :-)

Question 16:
If you want my advice, i'll need a little bit more info: like which wallet you used.
If you're willing to pay for an acceleration: the link you posted to viabtc also includes information about their payed acceleration service, btc.com and f2pool.com are also known to accept and execute payed accelerations.

Good luck!

Question 17:
I don't have time to wait for viabtc's tool to allow the next 100 free accelerations. I posted the link at the top of this post.
If you want more advice, please give me the information i need to put you on the right track (read the very first post of this thread)

Question 18:
I'm happy to help you out
There are several roads you can take:
1) wait it out, keep rebroadcasting the transaction by opening your wallet once in a while.. But with a 30 sat/byte fee, it *might* take weeks before the transaction finally confirms (it might even take months... It's all about odds, and right now, the odds of ending up in a block with a 30 sat/byte fee are really low)
2) you were on the right track with abandoning your transaction, you did forget a couple of steps that might explain why it didn't work. I stopped explaining the problem in my own words, since the guys of the wiki did a far better job than i ever could: https://en.bitcoin.it/wiki/Fee_bumping#Bitcoin_Core_GUI . You need the first 9 steps to abandon the tx, but since you were sending to Bitpay, i'd suggest also spending at least one of the unspent outputs again, funding one of your own addresses... That way the "stuck" transaction will no longer be valid
3) a more nuclear option would be to stop your wallet, and restart it with the -zapwallettxes option, this will force a full rescan of all the blocks, and it will only add confirmed transactions to your wallet.
4) since you are the sender, but it looks like a change address was used, you could also attempt a CPFP by spending the unspent output from the stuck transaction that funds your change address in a new transaction whose fee is big enough to cover both the fee of the stuck transaction AND the CPFP transaction. Let me know if you need help

On a sidenote: i would contact bitpay before attempting step 1 or 4, i'd try to find out if they are still honoring the payment first

Question 19:
Hi, could you add the extra info, as stipulated in the very first post of this thread?

Question 20:
There are a couple of problems with this transaction... The wallet used for sending was just a 'normal' (non-segwit) wallet, so (like you assumed correctly), the 400 sat/byte fee wasn't sufficient (it could have been sufficient if you were sending from a segwit wallet tough). But this isn't your main concern.
A 400 sat/byte fee will *eventually* confirm. I can only take a wild guess here, but i don't think it'll take weeks to confirm, as long as you keep rebroadcasting it.
The main problem is that this transaction uses an unspent output from an UNCONFIRMED transaction as it's input. Your transaction cannot confirm before transaction 472bc48974906b8727163c52d401d8a4b3f23c71c73e6ae6db6787108f273e61 confirms. Sadly, this parent transaction has a 24 sat/byte fee, so chances of THIS one confirming are not that good at the moment i'm afraid.
Could you tell me something about this stuck parent transaction, since this is the root problem?

Question 21:

Hi, i can give you a push in the right direction if i get more information about the problem (see the OP)

Question 22:

Hi,

Without a doubt, the stuck parent transaction is the reason the child isn't getting any confirmations.
Since the sweeping transaction still isn't confirmed.. I would personally try to double spend the unspent outputs that were funding your paper wallet in a transaction with a much higher fee... You could potentially fund bittrex'es deposit address directly, that way you only need to pay fees once.
In one of the previous questions, i showed how you can create raw transactions using bitcoin core, i also posted a link to a blogpost on how to create raw transactions using coinb.in

Let me know if you need any assistance!

It has a fee of allmost 400 sat/byte, this isn't technically sufficient, but i'm pretty sure that sooner or later, it'll get confirmed as long as you keep rebroadcasting the transaction from time to time.

If you want to speed things up, i'd like to know if you were the sender or receiver (or both) and which wallet software you used.

yes


there is no maximum... well, theoretically, you could send 1 satoshi and add a fee of the sum of every btc ever payed as a block reward minus 1 satoshi. In reality, that tx probably wouldn't propagate due to the dust outputs, and the fact there is no single entity that controlls all private keys..
Also, *some* wallets *might* have a built-in failsafe

Some illustration:
https://blockchain.info/tx/cc455ae816e6cdafdb58d54e35d4f46d860047458eacf1c7405dc634631c570d
allmost 15 million satoshi/byte... That should shed a different light on the 1000 sat/byte fees we see nowadays

00 sat
OK, this one has a fee of  312 sat/byte. Eventough currently the optimal fee is about 900 sat/byte, this one *should* eventually confirm if you wait long enough and make sure you rebroadcast it regularly.
If you want a quick confirmation there are a couple of options:
1) do a CPFP, the problem is that your wallet used the change that was funding your change address    13bq5aDGxanR7TFSdsKhk12JRg8tj1E6gX to create a new transaction, and than another one... So you'll have to use the unspent output funding your second change address to create a CPFP. I don't really know how to sign transactions in breadwallet, so you'll either have to find out if this is possible, or if the private keys can be exported

2) you can double spend the input of this transaction... But transactions that depend on this one will be cancelled, and the same problem as in the first point arises (you need to sign a raw transaction)

3) you can pay a trusted pool to accelerate your tx

4) you can keep rebroadcasting the tx and wait it out

Depends on how your exchange handles this issue...
This is exactly why i keeped asking you for more information... If you'd have said it was a transaction between two exchanges, i would have immediately told you there were only 3 options:
1) keep rebroadcasting your tx and wait it out
2) pay for an acceleration performed by a decent pool
3) contact the exchange, ask them to clean up their mess


Don't upload your private keys to a web wallet, i'd never suggest such an attrocity 
It *might* be possible to use armory to create a double spend, but to be honest, i haven't used armory in a really long time, so i can't give you any advice in this matter... I think HCP might know a bit more about this wallet than i do, maybe he'll chime in?

I don't bet, i just look at the odds... And right now, the odds of a 134 sat/byte transaction confirming within reasonable time are low if no action is taken... Chances of it being dropped from allmost all mempools are a lot higher than the chance it'll get confirmed before this happens.

I'm not saying it's impossible they will confirm (this should have been pretty clear by the fact that i bolded the text "this fee has a big chance it'll never confirm". I didn't say "there is no chance it'll ever confirm"), nor that i want to bet money on wether or not it'll eventually confirm, the odds are not in the OP's favour. You call this FUD, i call this realism.

If  you want to help the OP, be my guest. I have more than enough requests coming in, and i'm trying to help people for free, so i'm not really in the mood to start bickering over this.

I'm a big fan of people wanting to learn
The "problem" is that it's easyer to create a raw, unsigned transaction if you're running a synced node (like i am doing), electrum is perfect for signing transactions, but not so good at doublespending unspent outputs that have already been spent.

If you want to learn the basics, you can download the sourcecode of coinb.in, i've actually written a small post on my blog on it's basic usage a long time ago: http://www.mocacinno.com/blog/create-sign-broadcast-transactions-using-coinb/
I wouldn't use coinb.in to sign the transaction tough (so you don't need to follow the complete article).

If you succeeded in creating a double spending tx using coinb.in, please post the unsigned transaction in this thread and i'll review it for you and give you some pointers on how to sign it using electrum

no, it'll not be gone... It'll either be rebroadcasted indefenately, it'll be confirmed or after a long time most the network nodes will have removed it from their mempool and they will act like the transaction never happened.

Wether or not it'll be rebroadcasted: no idear, since you didn't give the information i asked for, and the answer to this question depends on this info.

Wether or not your wallet will react like the transaction never happened: no idear, since you didn't give the information i asked for, and the answer to this question depends on this info.

If your transaction doesn't confirm, and it's not rebroadcasted, the nodes will remove the tx from their mempools and according to the network, it'll be like the tx never existed.

Sorry, but the info you posted on my thread just repeated the same info (namely, the two tx id's).

If you want me to try to help you (no guarantees): please read this post, as asked before: https://bitcointalk.org/index.php?topic=1943939.msg19305587#msg19305587 and give sufficient info, as stipulated in this post.
I really don't have time to dig into each individual case and try to deduct information based on blockchain evidence... I know this might look rude, but i'm just a guy dedicating a part of his day to trying to help newcomers for free, but i really lack the time to do all the grunt work in your place.

I already posted a reply to your question in your thread... I get dozens of help requests a day (in this thread, on the forum, over PM, via twitter, via email, on other fora,...) , please don't duplicate requests, it gets very confusing for me this way.

If you want my help, please read my previous post in this thread...

I gave a reply in your thread.


you used a fee of 267 sat/byte, while at this moment the optimal fee for a 95% of getting into the next 3 blocks is 900 sat/byte.
If you want me to give you some advice on how to potentially solve the problem, i need a lot more information, as stipulated in the very first post of this thread


Don't worry your transaction doesn't get rebroadcasted by refreshing that page
As soon as you stop rebroadcasting, the number of nodes having your transaction in their mempool will start to decline. It'll take a long time before ALL nodes dropped your tx, but that shouldn't be a problem.
If you're creating a double spend, i see no harm in starting to broadcast it once or twice a day, starting a couple hours after you stop rebroadcasting

The truth is that it's 100% impossible to tell when (and if) a transaction will (ever) be confirmed.
When talking about confirmation times, you're talking about odds. At the time of writing, when paying a fee of 900 sat/byte the odds of getting into the next 3 blocks are 95%.

You payed a fee of 134 and 135 sat/byte, https://bitcoinfees.earn.com/ teaches us that this fee has a big chance it'll never confirm. Offcourse, if the number of tx's in the mempools would drop, your chances would increase, if there are more tx's broadcasted, your chances get even lower...

In order to give you some advice on how to proceed, i need more info... you posted on my thread here: https://bitcointalk.org/index.php?topic=1943939.120;topicseen , the original post of this thread tells you which info i'd need to help you out.