The absolute value of the transaction fee is completely meaningless. What matters is the fee rate in sat/byte. The fee rate paid by your transactions is extremely low due to the large size of your transactions. You are only paying 3 sat/byte for the first transaction, and 7 sat/byte on the second. The current recommended transaction fee is 390 sat/byte according to https://bitcoinfees.21.co/. Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about the transactions. |
|
|
|
What are benefits of setting prune to be anything greater than 550, such as 551, 2000, 3000?
You will be storing more of the blockchain and thus be less likely to be affected by very large blockchain reorgs. I'm planning to run Bitcoin Core 0.14.1 on two machines: one that is online and another that is offline (hence offline wallet). I'll have to update the blockchain once in a while on my online machine. The offline machine will be the same physical machine except booted from a Ubuntu USB stick. To run Bitcoin Core on the offline machine, I was thinking of running Bitcoin Core from the same USB stick. Is this do-able?
On the rare occasion that I use my offline machine, I was thinking that I would copy the block folder from the online machine onto a second USB stick, go offline, boot up Ubuntu from the first USB stick, copy the block folder from the second USB stick to the first USB stick. This way, when I launch Bitcoin Core from the first USB stick, it would be synced and therefore I will be able to send out bitcoins.
Does this sound do-able?
Yes. |
|
|
|
|
Please post the transaction id and the wallet that you used to send/receive the transaction.
|
|
|
|
|
bitcoin and altcoins are incompatible. You cannot sync an altcoin with bitcoin and vice versa unless the altcoin specifically implements some functionality in order to do so.
|
|
|
|
|
Is the wallet encrypted? If it is, are you using the walletpassphrase command first to decrypt it?
Also, sendfrom is deprecated. You should use sendtoaddress instead.
|
|
|
|
Does it make sense to attempt a build on my Macbook?
If so, which git branch should I use?
Use the testing branch. Building on macs right now may not work though, but you can try. |
|
|
|
1.Is there a third party service which allows you to rebroadcast transaction with higher fees with just the raw unsigned transaction ? Or is it impossible ?
Generally you need to use a different broadcasting software which either ignores the rules and broadcasts double spends. If the transaction does not show on a block explorer, you should be able to use that block explorer's broadcast api in order to send your transaction. 2.If I approach a miner personally,can he accept my transaction in the chain of blocks ?
Yes. Talk to Quickseller or macbook-air. They have access to f2pool's backend so they can include transactions for you. |
|
|
|
Your parameters are in the wrong order. The command format is sendtoaddress "address" amount ( "comment" "comment_to" subtractfeefromamount )
|
|
|
|
|
It has been confirmed now.
|
|
|
|
|
Bitcoin transactions cannot be canceled. If the fee is too low, you can attempt to make a conflicting transaction which is more likely to be confirmed, but there is no guarantee that the conflicting transaction will be the one that confirms. When you make your transaction, you can have it signal RBF which makes it easier to replace with a higher fee conflicting transaction.
|
|
|
|
Apparently transaction fees basically doubled in the past day or so, so the 220 sat/byte fee rate on your transaction is too low. According to https://bitcoinfees.21.co/, the current recommended fee rate is 450 sat/byte, which is way higher than I have ever seen. |
|
|
|
|
blockchain.info's fee estimation is garbage. Their wallet is also known to have many problems. I highly recommend that you don't use blockchain.info for your wallet.
|
|
|
|
I know about that. I mean I want to have another public key for my private key in the imported address.
You can't have multiple public keys for one private key. There is only one public key for a private key, and one address for a public key. |
|
|
|
Does it mean that that DB in v > 0.93.3 is much smaller in size? 0.93.3 runs very smoothly for me but its DB is very huge/
Yes. The DB has been significantly reduced in size. On my computer, it is ~1 GB. |
|
|
|
why 0.96.0.1-testing but not just 0.96? I do not like the word testing.
0.96 has some weirdness that has been fixed for 0.96.1 but 0.96.1 is still in the testing phase. And one more Q. Is it mandatory for me to migrate or I can continue to enjoy bitcoin with 0.93.3 ?
You can still use Bitcoin with 0.93.3. However you will be missing all of the improvements to the database, performance, coin selection, fee control, etc. that have been made since. |
|
|
|
hi,
I am still using 0.93.3 version for both online and offline wallets of Armory in conjuction with bitcoin core 0.11.2 and would appreciate any recomendations for smooth migration from 0.93.3 to 0.96 on Win 10 machine
On you online machine, upgrade to Bitcoin Core 0.14.1 and Armory 0.96.0.1-testing. To install, just download and run the installers, you don't need to do anything else. Once both are installed, go to the Armory datadir and delete the folder named databases. Your offline machine does not need to be upgraded as long as you only use the p2pkh address type. |
|
|
|
The transaction hash is 5f9b8a515eb7d9ee81831d7718cb039b656dee4b053200c8ff80d69e6fe8a2da - and if I look it up in the block chain its transaction fee is 50.389 Sat/B Shouldn't that be normal?
That fee is quite low. Are you using the "fee rate from node" option or just the "fee/byte" option when you make a transaction? |
|
|
|
What kind of debug were you referring to? From the debug.log file?
Yes, the debug.log file. It might have some info in there about why this happened. It also might not. |
|
|
|
|
It should give you a new address every time. However, IIRC, there's sometimes it won't if the keypool has not been refilled recently. For the keypool to not be refilled recently, you would have had to have requested the number of addresses in your keypool since the last time your wallet was unlocked.
Could you post the debug.log?
|
|
|
|
i've got windows 10 64 bit and i figured i would run a fullnode too, just because.
The program has already crashed twice, with nothing remotely resembling a human friendly error message, like, what it was it could not read (or where). it just crashes with various very generic messages. This is the only program that crashes regularily on my pc and i have no idea why, because the error messages are too generic like "cannot read database" hey! how about also writing on what drive, and in what dir, and what went wrong..
i don't feel like i would dare to trust this software with my bitcoins when it can't even bootstrap itself from the net, when it doesn't even seem to know itself why it crashes.
First of all, don't hijack someone else's threads with your own issues. Secondly, all of the important error information ends up in the debug.log file found in the Bitcoin Core datadir, not in the error dialogs. If it is crashing regularly, you may have a hardware failure somewhere as Bitcoin Core is known to be very hardware intensive. However the software itself can't tell you that, it just knows that it tried to read from the database and got back garbage that it wasn't expecting. And it does know why it crashes, it couldn't read the database. Why that happened, it does not and cannot know. |
|
|
|
|
Show Posts
