Segwit fixes transaction malleability, which means that a transaction composed entirely of segwit inputs will have only 1 txid. This makes it easier for services to track deposit transactions because then there is no need to actively watch for any malleated transations and track those as well. Those malleated transactions would be considered a double spend and ordinarily rejected.

Segwit also makes sighashing[1] a linear operation instead of quadratic with a new algorithm. This reduces the effect of a large transaction taking a long time to verify. Note that such a large transaction has happened before. A transaction was created a few months ago that was 1 MB in size. It was created by a miner and included in the miner's next block, i.e. not broadcast until confirmed. This transaction took ~30 seconds to confirm, which, in computer time, is an incredibly long time.

Segwit makes hardware wallets to their jobs better. The new segwit sighashing algorithm includes the value of the output being spent from so hardware wallets can easily verify whether the transaction that it is signing is valid. This helps with further verification done by the wallet itself prior to signing the transaction.

For the full list of what segwit does and its benefits, see https://bitcoincore.org/en/2016/01/26/segwit-benefits/

---

[1] Sighashing is the process where all of the transaction details are prepared and then hashed. The hash is then signed and the signature goes into the transaction.

Send them a PM. Click the following links to send a PM to that person: Quickseller and macbook-air

It depends on if you just wait or if you do an RBF transaction (double spend with a higher fee). However, it is actually impossible to know how long that will take to confirm because the state of the network (i.e. the recommended fee) constantly changes.

Use the latest version of Electrum and set the fee settings to use Dynamic Fees so that it always choose the optimal fee.

You paid a fee of ~30 satoshis/byte. According to http://bitcoinfees.21.co/, that should (but not guaranteed to) take up to 43 blocks to confirm. The recommended fee is 80 satoshis/byte.

You can either wait, or attempt a double spend with a higher fee. You can also try contacting the users macbook-air or Quickseller, both are known to be able to help people with these problems.

Not upgrading to a segwit enabled wallet will not affect sending or receiving Bitcoin as you do now. The backwards compatibility of segwit means that you will be able to receive from someone with segwit (albeit after the transaction has confirmed a few times) and send to someone who wants to use segwit.

Hard forks are far from simple. Segwit also solves a lot of problems simultaneously, not just capacity. A "simple" block size increase hard fork ignores a lot of the nuance that comes from making such a change

Segwit does not need a block size increase hard fork.

It's a blockchain.info problem on their end. Blockchain.info has nothing to do with how the Bitcoin network functions, so whatever happens on their site will not affect anything unless you use their web wallet.

If you have Bitcoin in your account, you should be able to send Bitcoin to an address. If your currency is no longer Bitcoin, then you cannot send Bitcoin at all and it will have all been converted to whatever currency you set.

That's not true. You can still deposit Bitcoin if your account already had the Bitcoin currency option set. So long as your account has the Bitcoin currency option set, you can still send and receive Bitcoin.

AFAICT Circle does not give you access to the private keys.

Please do not hijack threads and necro post. Make your own for your own issue. I have split this into its own topic

This should no longer happen with the latest version of Bitcoin Core. What version are you using?

Why? Linux won't help you here.

Just click OK in the prompt that appears. If that does not appear, you probably don't need to reindex. When reindexing does happen, just let it run, there is nothing that you need to do.

DO NOT USE THAT WEBSITE!! IT IS A KNOWN SCAM SITE!! The owner of that website holds onto the private keys and will steal any Bitcoin.

I don't think it matters.

It shouldn't, but you should still attempt to provide the correct IP.

Because....

Just use 0.

You won't get banned on the first time that you try. Just don't send bad messages too many times too quickly and you should be fine.

You should test this against your own local node and you can set it to never ban the node that you are testing.


You should use wireshark to see the messages actually sent by nodes so that you can check your own message and see how the messages are usually done.

Bump.

Bump.

I don't know why it is not getting any connections. You can try connecting to my node. You can try connecting to my node. In that debug window, go to the Console tab and in the box at the bottom, type
then hit enter. If it works, you should see that you now have one connection.

Bitcoin Core is not developed by goatpig. It is an important part of Armory as a dependency, but Bitcoin Core having problems has nothing to do with Armory.

Your problem looks like it is currently with Bitcoin Core. Usually you need to reindex when it says "no source block available" and you still have connections. Go to the folder where Bitcoin Core is installed. Hold shift, right click, then choose the option to "Open a command window here". Type
This will start Bitcoin Core's reindexing. It will look as if it is redownloading the blockchain, but it actually is not. You will see the green progress bar at the bottom, let it reindex and sync. You have to leave Bitcoin Core open until the green progress bar disappears. Once it is, try starting Armory again.

Bitcoin Core has changed since 0.9.x. Just follow the instructions here: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md to build Bitcoin Core for ubuntu.

It looks like Bitcoin Core is not fully synced. You have no connections and the Armory logs seem to indicate that you may have a corrupted block. Can you please give me the debug.log file from Bitcoin Core? Go to Help > Debug Window and there is a button that says "Open" which will open the debug.log file.

Yes.

Try starting everything manually. Start Bitcoin Core, then start ArmoryDB, then start ArmoryQt.

Make sure that you don't have anything using port 9001.

These aren't errors at all. A few miners are still mining blocks signalling the BIP 109 which uses a different version number. Bitcoin Core will detect that the version number is not one that is recognized and print this message to the debug log.

Completely unrelated to the above message.

Not weird at all. Miners constantly mine blocks with few transactions. They are free to choose whatever transactions that they want to include, whether that is 5 (plus one for coinbase) or 2000+.

Uncheck that box. Stop Armory. Close the command prompt with ArmoryDB.

Start Bitcoin Core. Let it run until it is fully synced. Once it is keep it running and repeat the steps I gave for running the ArmoryDB command in a command prompt. Then start Armory while both ArmoryDB and Bitcoin core are still running.

Hit enter. There should be some output on the console. Leave it open and wait for a message about "enable zero-conf tracking". Then start Armory normally while the console is still open.