|
A CPFP transaction is not a conflict and does not result in any additional transactions being listed in your wallet unless you are the one performing the CPFP. It does not affect you.
The safest thing for you to do would be to wait for one confirmation. After one confirmation, it does not matter whether a transaction was RBF'd or not; the conflicting transaction will be unconfirmed and you aren't counting those.
|
|
|
|
|
One confirmation means that your transaction has been included in a block. All subsequent confirmations happen with more blocks are found on top of the block your transaction was included in. Once you have one confirmation, more confirmations will come as blocks are mined; there is nothing that you need to do.
You only need to pay a transaction fee (or fee for that service) once in order to get the first confirmation.
|
|
|
|
This topic has been moved to Trashcan. Begging |
|
|
|
So, how will it be faster than the chain if the miners would stay in the main channel because the payment they will receive might be lower?
I'm looking forward to the Lightning Network and I don't want to use Bitcoin Cash just for a faster transactions.
THere is no "main channel". Miners are not involved in lightning except for confirming the on-chain opening and closing transactions. The transactions are faster through lightning because they can be done nearly instantaneously (well as fast as you can send data over a wire) with basically guaranteed security. |
|
|
|
|
A transaction is confirmed when it has at least one confirmation. If you don't see it in your wallet or it says "unconfirmed", that means that your wallet is either working improperly or not synced with the blockchain.
|
|
|
|
|
It won't be centralized in the sense of traditional banking centralization. Even if LN is dominated by most people connecting to just a few large hubs, those hubs don't have the level of control that a bank does. You as a user will still be in control of your money, and you can close a payment channel at any time you want. And you don't even have to have a channel with those hubs if you don't want to; LN lets you create payment channels with anyone else.
|
|
|
|
During adoption, there will be a fee in the form of the on chain transaction to stake your coins and open a channel? So basically we are asking the userbase to endure a one time "adoption fee" in the name of lowering overall fees long term. When lightning network is operational, and transactions are largely off chain, then the on chain demand is reduced creating the fee reduction. That seems to be the biggest barrier to adoption, the requirement for "paying a fee to reduce fees".
Not everyone is going to suddenly start using LN at the same time. Some people will suck it up and be the first people to open a channel and pay higher fees. As their transactions move off chain, the fee will decrease, and more people will then join. That will happen so on and so forth; the fee will decrease gradually as more people use LN and more people will begin using LN as it becomes more widely accepted and the barrier to entry (i.e. the funding transaction's transaction fee) decreases. |
|
|
|
XEM is not on the list of coins on that source. When I enter that and the seed all I get is more Bitcoin addresses and private keys. Same goes for anything else I select. It's coin dependent.
It must require some type of input of initial code from whichever coin to give you results back.
It is only the encoding of the private key that is coin dependent. The private key itself is not coin dependent. You can decode the Bitcoin WIF private key into hexadecimal form, drop the extra encoding bytes, and just get the raw private key in hexadecimal. Then encode that with whatever coin encoding you want to use. Sites like bitaddress.org will do all of this decoding for you. |
|
|
|
The problem I see with the "just not use LN" argument, is that once Lightning network is widespread and we have channels all over the world filling flocks with all these microtransactions, the overall on-chain fee will be higher than ever, at some point it will be non-viable for most people to transact on-chain. For people using LN, it wouldn't matter, as their transactions will eventually go into a block mixed with the rest of LN transactions (btw, who sets the fee for an "LN-tx filled block"?) but for people that want to transact on-chain, it will be extremely expensive, unless im missing something here.
PS: Im not saying "make blocks bigger as soon as they get filled" and such nonsense are a solution, im just pointing out at how widespread LN usage could lead to unusable on-chain transactions.
What? No! That is not how LN works. There won't be "filling blocks with all these microtransactions" because the microtransactions are happening off chain. LN moves transactions off chain so there will be more block space for other transactions. Fees should be lower with LN, not higher. |
|
|
|
unfortunately it happened again, this time at 5%
Since this is continually happening, this may be a sign of hardware failure. You should run diagnostics on your RAM and hard drive to make sure that there are no errors. |
|
|
|
|
It depends on the wallet software you are using. Most will have RPC commands so you can interact with them programmatically.
|
|
|
|
thanks
what is the name and location of the created exe file
The files will be src/bitcoind.exe, src/bitcoin-cli.exe, and src/qt/bitcoin-qt.exe (well a few others, but these three are the only ones that people actually care about). |
|
|
|
This is the derivation path on the Trezor - m/44'/43'/0'/0'/0' . I have the seed. Beyond that I'm stumped.
Go to https://iancoleman.io/bip39/. Choose the BIP 32 tab. Enter that derivation path. You will then get the private keys. |
|
|
|
After I run the make on Ubuntu there is not an exe file,under src there is bitcoind bitcoin-cli
But how can I get the wallet with interface and run under Windows ？
Did you follow the documentation exactly (i.e. go into depends and build the dependencies)? Also, if you have built any part of Bitcoin Core before, you will need to use make clean before performing make. |
|
|
|
|
The actual watchlist link will only show threads which have had a new post since the last time you visited the thread. You can see what threads are actually being watched by clicking the "edit watchlist" link.
|
|
|
|
Lets say all the non-mining full nodes reject the block. Why would the miners care? the miners are the one creating the blockchain. You can cry foul all day long but unless you can vote with your hashpower on which chain is correct, you are yelling to the wind.
Miners care because the businesses that accept Bitcoin run full nodes. Businesses will choose to run the nodes that the users are using otherwise they would not have any other customers and would thus be making no money from accepting a different chain. If no one accepts the miner's chain, then they are mining something has no value. Bitcoin is not ruled by miners. |
|
|
|
|
For what? Bitcoin? There is no readme-qt.rst file in the Bitcoin Core source docs.
|
|
|
|
Thanks for that. Is there any way of knowing if people are running modified code?
No. |
|
|
|
|
Show Posts
