I set the fees to 30 sat/b, and now it changed At the same time, it shows that transaction 1 and 2 are invalidated
The transaction made with fee rate of 30 sat/vbyte will be likely confirmed in the next block. (A new block is mined every 10 minutes on average) Transactions 1 and 2 no longer exist.
|
|
|
So right now, I will need to get transaction 3 confirmed first,
If you are in hurry, bump the fee of transaction 2. If you are not in hurry, just wait. As calculated, the total virtual size of your transactions is 427 vbyte. Given that for a fast confirmation, transaction fee of around 14 sat/vbyte is required, you need to pay 5978 satoshi in total. You have paid 3024 satoshi for transactions 1 and 3 and need to pay 2954 satoshi for transaction 2. If you are in hurry, bump the fee rate of transaction 2 to 21 sat/vbyte. You can pay a bit more (around 25 sat/vbyte) to make sure your transaction will be confirmed soon. The fee rate required for a fast confirmation changes over time. I'm now trying to increase the fees for transaction 3. The current fee for transaction 3 is 7 sat/b, but even I put in 27 sat/b, it still says:
With doing so, you invalidate transactions 1 and 2. If you want all three transactions to included in the blockchain and you are in hurry, bump the fee of transaction 2. Note that in my previous post, I had assumed that the order is transaction 1 ---> transaction 2 ---> transaction 3 and that was why I said you should bump fee of transaction 3. Since the order is transaction 3 ---> transaction 1 ---> transaction 2, you should bump fee of transaction 2. Again, no need to do anything, if you are not in hurry.
|
|
|
I made transaction 3 first, then 1 and 2 (not remember the order between 1 and 2)
As mentioned by ranochigo, you have made the transaction 1 before transaction 2. If you want these transaction to be confirmed fast, you should bump the fee of transaction 2 Note that with bumping the fee of transaction 3, you invalidate transactions 1 and 2 and with bumping the fee of transaction 1, you invalidate transaction 2.
|
|
|
The first 2 transactions are marked as 'Unconfirmed Parent' and the third transaction is marked as 'Unconfirmed'. What's the difference, do they link with each other ?
When electrum says that a transaction has unconfirmed parent, it means that the fund which is being tried to send in that transaction has been received in a transaction which is still unconfirmed. Assume that you have sent bitcoin from address A to address B and then the same coin from address B to address C. As long as the transaction made from address A to address B is unconfirmed, the transaction made from address B to address C can't be confirmed. The two transactions that have been marked as "unconfirmed parent" can't be confirmed before confirmation of their parent. Can you share your transactions IDs? With sharing your transactions, you may hurt your privacy. But it won't have anything with your security.
|
|
|
I haven't understood what you said 'Note that increasing the fee for your first transaction invalidates the later (child) transactions'
Assume that you have sent bitcoin from address A to address B and then sent the same coin from address B to address C. If you bump the fee of the transaction made from address A to address B, the transaction made from address B to address C becomes invalid. -----------
The total virtual size of your transactions is 427 vbyte and the total fee paid for three transactions is 3953 satoshi. This means that the effective fee rate is around 9 sat/vbyte. Your transactions are now around 45 vMB from the the tip and you shouldn't expect them to be confirmed soon. If you are in hurry, bump the fee of transaction 3. Currently, for a fast confirmation, the fee of around 20 sat/vbyte is required. Given the total size of your transactions are 427 vbytes, you should pay 8540 satoshi in total. You have paid 2945 satoshi for the first two transactions and you need to pay 5595 satoshi for the third transaction. So, you need to bump its fee to 38 sat/vbtye. Again, if you are not in hurry, just wait. Edit: I assumed that transaction 3 is spending the fund received in transaction 2 and transaction 2 is spending the fund received in transaction 1.
|
|
|
If you have chosen the first option and still can't recover your wallet on an app that supports bip39, then make sure you selected the right addresses format (p2wpkh or p2wpkh-p2sh) because green wallet will create two accounts for these two formats (segwit and legacy).
This is probably the problem. Wasabi wallet only generates native segwit addresses. If OP has created a wallet with different address format in green wallet, it can't be recovered in Wasabi. Another question: what happens if i want to recover a wasabi wallet with passphrase in another wallet? do they all have the password/passphrase available??
You can use electrum. It allows you to import a BIP39 seed phrase with a passphrase.
|
|
|
If so, is it normal that my transaction is unconfirmed (it was 1 hour and 40 minutes ago) and do I just have to wait ?
Yes. Miners prioritize transactions based on the fee paid for them. At 10 sat/byte: yes. Someone made a lot of transactions at slightly higher fee than yours. OP has paid 14 sat/vbyte for the transaction in question. It's now about 4.5 vMB from the tip and it shouldn't take a long time to be confirmed.
|
|
|
I don't really understand why would it be some change returning? That's how bitcoin transactions work. Every time you receive a transaction, you receive a UTXO. Let's say you have received two transactions. In each of them you received 0.5 BTC. Now you have two UTXOs and you want to spend 0.75 BTC. As you UTXOs must be spent completely, you have to use both UTXOs. So you make a transaction with two inputs and two outputs. One of receiving addresses is owned by the recipient and the other on is your own address which receives the remaining balance of UTXOs. Do you know how I can do to complete or cancel this transaction ?
The network is so congested now. If you are not in hurry, just wait. Your transaction will be confirmed. If you are in hurry, you can bump the fee.
|
|
|
Cant I just make a wallet. Create an address and then let it be well known that this is where you send bitcoin to pay me ?
You can. Am I supposed to create a new address for every new person who wants to pay me ?
You don't have to create a new address. You can give the same address to everyone you want. If I want to buy coins on an exchange to top up my wallet am I supposed to create a new address for receiving and then go through the drama of white listing that address every single time ?
No. You can use the same address numerous times. Using a new address is optional and you don't have to that. Note that with using a same address multiple times, you may hurt your privacy. The person who knows your address can track your previous transactions and know your bitcoin balance. Using a change address is also for your privacy. In the case your sending address is used as your change address, everyone can know that which of the outputs is owned by the recipient and which one is your own address. Anyways, if you want the remaining amount of your coins is sent back to the sending address, go to "Settings" and then to "Wallet" tab. Check "Enable coin control features". Check "Custom change address" when making a transaction and enter the address you are sending bitcoin from.
|
|
|
If someone has really sent you bitcoin, the transaction is final and there is no need to pay any transaction fee. So, he/she hasn't sent you any bitcoin. Also, a normal bitcoin transaction doesn't need that high transaction fee.
Can you be more specific please? I guess someone is trying to scam you. Anyone asking you to send bitcoin to receive more is a scammer.
|
|
|
I have put my private key on the dialog box for "Import private ket" but it's impossible to push on the "Next" button.
In your previous post, you said that you made a transaction to an exchange and now you say you can't import your private key into electrum. Am I missing something here?
|
|
|
I guess it's because I haven't put enough but someone can explain what I have to do here ?
If you are not in hurry, just wait. There is no need to waste more money on transaction fee. If you are in hurry, right click on your transaction and select "Increase fee". Currently, you need to pay around 15 sat/vbyte if you want your transaction to be confirmed in the next block. (A new block is mined every 10 minutes on average.) Note that the fee rate required for a fast confirmation depends on network state and changes over time.
|
|
|
Also would it be possible then to import the Seed in lets say trust wallet and start generating new addresses there and then be able to restore those addresses AND the vanity adress later with the seed?
No. If you enter that mnemonic into a wallet, you can't get your vanity address. It will generate completely different addresses. Of course, it's possible to derive your private key from that mnemonic. But there is no wallet doing that. Note that you can't derive your seed phrase from your private keys at all. Anyways, Below is how pooya87 converted the WIF private key to a mnemonic. WIF private key: L3YPzKfwpVYQr4B9DxbUxhFAncxveBnUoJJ2rSyq5KujaHdgUMXy
First we convert the WIF private key to a hex string using Base58Check encoding. 80bca326ea69831c76b9ac4828b30cfdd7955a0a775cf017bf3106afb73afeb811011838d07c
Now we remove the 80 from the beginning and the suffix "01" and the checksum from the end. The checksum is the last 4 bytes (the last 8 characters in the hexadecimal format) Note that there is no suffix to be removed if you started with an uncompressed private key (a private key starting with 5). bca326ea69831c76b9ac4828b30cfdd7955a0a775cf017bf3106afb73afeb811
Now we have a number in hexadecimal format. The 256 bit number in binary format: 101111001010001100100110111010100110100110000011000111000111011010111001101011000100 10000010100010110011000011001111110111010111100101010101101000001010011101110101110011110 00000010111101111110011000100000110101011111011011100111010111111101011100000010001 We should extend the 256 bit number with 8 more bits which is called checksum. To calculate the checksum, we hash our number (as a hex input) using SHA256 function and then convert the result to a binary number. The first 8 bits is our checksum. Checksum: 01101011 With adding these 8 bits to our 256 bit number, we have a 264 bit number which is shown below. 101111001010001100100110111010100110100110000011000111000111011010111001101011000100 10000010100010110011000011001111110111010111100101010101101000001010011101110101110011110 0000001011110111111001100010000011010101111101101110011101011111110101110000001000101101011 For converting this number to a mnemonic, we use BIP39 wordlist. Each of 11 bits gives us a word. The first 11 bits: 10111100101 ----------->1509 ---------> Word number 1510 in the list ---------> royal The second 11 bits: 00011001001 ---------> 201 ---------> Word number 202 in the list ----------> bomb ........ ........ ........ The last 11 bits: 00101101011 ---------> 363 ---------> Word number 364 in the list ----------> coin Again, there is no wallet deriving your vanity address from your mnemonic if it has been generated using this method and you need technical knowledge for generating your address using that mnemonic. Avoid this method, if you don't know what you are doing.
|
|
|
Around this time yesterday, even the Free BTC transaction accelerator wasn't helping. They had 98 slots left for the hour, but whenever I would try to push the transaction for OP. A notification would pop up saying that the fee rate in the transaction was way too low.
ViaBTC doesn't accelerate transactions paying fee of less than 10 sat/byte freely and that's why you couldn't submit that transaction. To accelerate such transactions, you have to use their paid service.
|
|
|
That it is not true, since you can have a seed phrase in a secure steel backup and want to use that for your vanity adress too.
I think you didn't get pooya87. He didn't say you can't have a seed phrase on a steel sheet or keeping a private key is easier than keeping a seed phrase. It's surely possible to have a vanity address generated from a seed phrase. pooya87 was referring to complexity of deriving a vanity address from a seed phrase. If you want to have a vanity address generated from a private key, you generate a private key and then derive the public key and the address. You repeat the process until you generate the address you are looking for. For generating a vanity address derived from a seed phrase, you add extra steps. You should generate a seed phrase and then derive the seed, the extended private key, the private keys, public keys and addresses.
|
|
|
I don't understand why you want to reduce it and you're dividing f*(SA+SB) - SA*fA by the length of the new transaction.
Note that f B is the fee rate you should use for the new transaction. It's not the absolute fee. The fee required to be paid for the new transaction is f*(S A+S B) - S A*f A. In your new transaction, you should set the the fee rate to (f*(S A+S B) - S A*f A) / S B, so the absolute fee paid for it is f*(S A+S B) - S A*f A. Let's say the fee required to be paid for the new transaction is 1000 satoshi and its size is 200 vbyte. I should set the fee rate to 1000/200 = 5 sat/vbyte.
|
|
|
I don't know if it is due to this but your transactions got confirmed finally. Congratulations and for next time better use the default fee.
The transaction was confirmed normally and without help of CPFP. The output of the transaction in question was spent in another transaction with transaction fee of only 1.127 sat/vbyte which is even lower than the transaction fee of the first transaction.
|
|
|
The two new transactions have been made with lower fees. The first transaction had been made with the fee rate of 2.7 sat/vbyte. You made the new transactions with the fee rate of 1.13 sat/byte. Anyways, even if you had made the two new transactions with 1 BTC/vbyte, it wouldn't help your receiving transaction to be confirmed. You made the two new transactions from the receiving address of the unconfirmed transaction, but you spent different UTXOs. For implementing CPFP, you must spend the UTXO received in the unconfirmed transaction. The other mistake you did is that you spent significant number of other UTXOs is the same transaction. With doing so, you increase the transaction size and make the CPFP more expensive.
|
|
|
If I sign a transaction with Electrum and send the raw text to someone, can he decode it to find my private key?
No. Your raw transaction doesn't include your private key. Instead, it includes a digital signature which can be used only for that transaction and becomes invalid if transaction data is changed. By the way, why doesn't your friend let you broadcast the transaction yourself?
|
|
|
I knew the basics, and at a first look it does look correct.
I knew you know that. I made that post for OP or anyone else who want to do such a calculation. Still, I am not convinced that everybody knows where to look for those "numbers" (and I'm not talking about you or me).
You are right. For a newbie, it may be difficult to know what are fee rate and transaction size.
What site is this?
The screesnshot posted by Peanutswar has been taken from mempool.space. It's a block explorer and can be used for tracking transactions. You didn't tell us whether you have control over any of receiving addresses or not. If so, as suggested by NeuroticFish, you can use CPFP method.
|
|
|
|