Thanks for help. I tried that, exactly as you wrote and how it's in https://www.bitcoinarmory.com/troubleshooting/ Command-Line Options, but error and log is the same. I tried both C: and F: and created folders myself. Will try tomorrow, maybe I did sth wrong... If you copy and pasted directly from the examples on that site, then it is wrong. There's something wrong with the quotation marks that are used there. Type it out manually, don't copy and paste. Also, bitcoinarmory.com is not our website. The website is https://btcarmory.com/ |
|
|
|
Please post the transaction id of the transaction. The issue is likely due to a low transaction fee or spending from other unconfirmed inputs. Given that you are using blockchain.info's crap software, both possibilities are extremely likely to have happened. Please read https://bitcointalk.org/index.php?topic=1914800.0 |
|
|
|
|
Bitcoin Core's databases (LevelDB) doesn't work with network shares. You won't be able to have the datadir on a NAS.
|
|
|
|
Im using blockchain.info  Please read https://bitcointalk.org/index.php?topic=1914800.0Unfortunately there is not much that you can do except ask miners for help and wait. Do u reckon it will be confirmed in next 24 hours?  Probably not, but predicting when a transaction will confirm is incredibly hard. Unfortunately for you, the majority of transactions are in the 120 sat/byte range (because a lot of people use blockchain.info's shit software) and they can't all be confirmed at the same time. |
|
|
|
Please post the transaction id of your transaction. The absolute value of the fee is completely meaningless as miners do not use that to determine which transactions to accept. Also, read https://bitcointalk.org/index.php?topic=1914800.0. Since you are using blockchain.info's wallet, there is not much that can be done. |
|
|
|
There is also some additional overhead for transaction version and data lengths. In fact, the public key is also "overhead", because it can be derived from digest, signature and hash160. Having the public key saves on computation time since it is hashed and compared first before doing the more expensive signature validation operations. Otherwise attackers could just put invalid signatures which first have to go through expensive signature operations to get the public key, and then compare the public key last. That could potentially be a DoS attack vector. |
|
|
|
i used blockchain wallet,
There's your first problem. Read https://bitcointalk.org/index.php?topic=1914800.0Unfortunately, because you use blockchain.info's wallet, there is not much you can do except for asking a miner for help and waiting. i already doubled the fee it recomended sending
It is still not enough. Blockchain.info's fee estimation is horrible so what it recommends is definitely not enough. |
|
|
|
|
In the transactions list, right click the transaction and choose "Copy Raw Transaction". Then paste what was copied into a post here. That is the raw hex of the transaction itself and posting it will allow people here to rebroadcast the transaction for you so that the network actually sees it. The problem is likely due to poor propagation of the transaction as I am unable to find it both on block explorers and on my own node.
|
|
|
|
|
Please post the transaction id of the transaction.
|
|
|
|
If the first transaction was sent with RBF enabled, then you can replace it with a higher fee transaction. So, what should i change/set in a tx for it to be marked as RBF enabled? There is surprisingly little i can google about this. You cannot change it after the fact. Since the transaction has already been broadcast, you cannot change it to be RBF enabled. That can only be done when creating the transaction, before it is signed and broadcast. Your transaction is not RBF enabled. |
|
|
|
|
I have never heard of a fw2 file extension. All the major wallets that I know of use .dat, .wallet., or .key as their wallet file file extensions.
|
|
|
|
Your transaction fee rate is not high at all. You are paying a fee rates of 109 sat/byte, 120 sat/byte, and 132 sat/byte, which are much lower than the current recommended fee rate of 270 sat/byte according to https://bitcoinfees.21.co/. Your third tx depends on the second, so it cannot confirm until the second does. The second depends on the first, so that cannot confirm until the first does. Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about your transactions. |
|
|
|
4. Is there an issue for using the same wallet address for many transactions? Talking about being investigated or followed by a governmental agency? How traceable a transaction is? How vulnerable is it?
Yes. Using the same address will result in less privacy and potentially less security. People who send you money will know how much money you actually have. People can then also see who you are paying and how much you are paying them. It is highly recommended that you do not use the same address but instead generate a new address for each payment you want to receive. |
|
|
|
achow101, DannyHamilton: Thank you for your responses guys, I already see that blockchain is a big mistake and I will switch to your reccomended wallets, but you also need to understand that there are lots of people like me who see their website and their claims that they are the biggest and best wallet in the world and also lots of other websites write about them positively. And if you need to do just 1-2 transactions per month, then its obvious choice for a lots of people.
Can you tell me, what can I do with the actual status of my transaction. I really need to make it completed, I dont know how exactly it works but I can pay someone some extra fee to PayPal for example to complete it. Sorry really dont know, how it goes here.
Thank you very much
All you can do is ask miners for help and wait. Read https://bitcointalk.org/index.php?topic=1914800.0 |
|
|
|
Blockchain.info's web wallet is considered a poorly written wallet and is seemingly incapable of sending proper transactions with correct transaction fees and confirmed inputs. If you are using blockchain.info's web wallet and your transaction is stuck, it is almost definitely because the transaction fee is too low (at 120 sat/byte which seems to be blockchain.info's default fee rate even though it is much too low) or because you are spending from other unconfirmed transactions. If you are using blockchain.info's web wallet, unfortunately you won't be able to attempt RBF or CPFP transactions as blockchain.info does not provide the advanced functionality to make those transactions. All you can do is ask miners for help and wait. For asking miners for help: Ask a miner for helpSome mining pools and miners offer services to allow you to prioritize your transaction in their mempool so that it is chosen sooner for inclusion in a block. You can contact the users Quickseller and macbook-air. These two users have access to F2Pool's transaction selector and they can help you with confirming your stuck transaction. You can also try using https://www.viabtc.com/tools/txaccelerator/ to "accelerate" your transaction. Note that ViaBTC does have a limit the accelerator to 100 transactions every hour and requires that it pays a minimum fee rate of 10 satoshis/byte, so their accelerator may not necessarily work. To avoid this problem in the future, stop using blockchain.info. Instead switch to any wallet listed on Bitcoin.org and has one of the following texts regarding how the wallet handles transaction fees: Full control over fees Dynamic fee with override Dynamic fee suggestions Any wallet which has one of these texts for in their descriptions (with the color and bolding) will support dynamic fees and allow you to make transactions with proper fee rates. |
|
|
|
|
Show Posts
