It's not though.

BCH keeps the entire Bitcoin transaction history and simply diverges from the Bitcoin blockchain by introducing blocks with a different ruleset after the 12:20 UTC. This is exactly the definition of a fork. A BCH full node will be able to verify the entire transaction history from Satoshi's Genesis block to the present. The ruleset it will check will change from time to time, including a change after 12:20 UTC on August 1st.

There's nothing preventing a large Bitcoin miner from 51% attacking BCH. It'll cost them a considerable amount of money in lost mining income, so I guess that's what the BCH folks are banking on.

There are 2 issues with this adjustment-algorithm:

First, it only compared the most recent block with the one 6 blocks before that. So if there's no BCC block mined yet, then the difficulty won't be adjusted. This means that if only a small fraction of the miners switch to BCC, then it will take a long time to find this first block (1% of mining power -> 16 hours on average).

Second, this algorithm doesn't adjust the difficulty further down once a rate of 6 blocks in 12 hours has been achieved. Neglecting variance, that means that when the average over the last 6 blocks hits 2 hours per block, the most recent block took about 1 hour. At that point this form of difficulty adjustment stops and the coin will be moving forward at 1 block per hour until the next difficulty adjustment, which will be somewhere between 1 and 2 months later.

This first issue is only relevant if mining support is very small, but the second issue is relevant in almost every realistic scenario. The chance is extremely high that under these adjustment rules, BCC blocks will be moving very slowly for a considerable amount of times. This will disincentivize miners and users from supporting the chain and it may ultimately doom it.

No, the Python errors shown are from the client-side. Kraken typically returns a JSON with the appropriate error message if something goes wrong.

@OP: It seems that something in the response message doesn't parse correctly in the JSON decoder. So take a look at the raw response message, not the Python error message, (or post it here) to see what's going on.

Would there at least be an option to implement some temporary stopgap measures until the new engine is ready? For example a minimum order size to cut down on the total number of orders the engine has to handle.

Any news on when the new trading engine is coming online? Because the current one simply won't do anymore. It often takes several minutes to execute a market order, even when there's not much going on. For active trading, Kraken has become unusable in its current state.

USDT is a crypto-token issued by a company that advertises with a 1:1 peg to the Dollar, but has no means to make good on this (they lack usable banking partners just like Bitfinex) and they explicitly reject any guarantees in their terms of service.

USDT is reasonably stable around $1, so it can be used as a temporary way to get out of crypto or to transfer funds between exchanges, but don't rely on it keeping its value.

It appears that the spikes aren't triggering stop losses (which is good, because it would be crazy otherwise, now the situation is rather limited except for messed up charts). So any stop loss you place should only be triggered by actual price-movements.

I reported this particular issue more than 3 years ago: https://bitcointalk.org/index.php?topic=290799.msg4376913#msg4376913

There have been other reports as well, scattered throughout the thread, so it may have been known for even longer. It used to happen quite rarely, once every few weeks or even less frequently. I suppose that the uptick in these incidents is due to the increased volume. But the issue itself is far from new.

edit: Reading further, it seems that Serpens66 spotted it a month before me as well. Also, you reported in Jan 2014 that you would be looking into it

Which day it should be is obvious, the 3rd of january, the anniversary of the Genesis block and the de-facto birth of the blockchain.

No. Legitimate nodes will never accept a block that is considered invalid, regardless of how many nodes are broadcasting it. In your example, the attacking nodes would form a separate fork and the legit nodes would just carry on with the original blockchain.

How about they completely eliminate maternity tourism by abolishing the ridiculous jus soli policy. Grant citizenship at birth only if at least one of the parents is a citizen, like most countries do.

Delays are irrelevant. You keep fiat on the exchange with the lower price and coins in the higher exchange. When the price difference is sufficient, you perform the buy and sell trades at the same time. Afterwards you deposit and withdraw where needed to settle the balances. If you're waiting for coins to transfer before making the second leg of an arbitrage trade, then you're doing it wrong.

Anyway, if the price on btc-e is consistently lower, then apparently depositing fiat is slow, unreliable or expensive.

No.

HTML is a language for website structure and layout, it doesn't provide features for interactivity. For that, you need to use a scripting language such as JavaScript (client side) or PHP (server side).

The problem is mentioned right there in the screenshot: Your funds are still pending confirmation. You've probably received the 2.5 BTC very recently on this account and the transaction hasn't been confirmed yet.

If the sender included the proper transaction fee, it should be done within an hour. If no fee was included, it might take up to one or two days.

Il y a un forum Francais sur Bitcointalk: https://bitcointalk.org/index.php?board=13.0

Some exchanges have order-types that allow you to do that. Kraken, for example, has a "Stop" order that does exactly what you want. There might be other exchanges with the same features, but since I don't know any, I'll let someone else name them

They're hard to separate though. Securing the blockchain (mining) isn't free and miners have to be rewarded for their efforts in some way. The most obvious way to do so is to issue tokens to the miners that can be transacted through this blockchain. Without a reward for mining, the security of the system is at risk.

Except that it isn't, because Coinbase is far from trustless and can run with the money / get hacked just like Gox / BTER.

Bitcoin.org has an overview of various clients: https://bitcoin.org/en/choose-your-wallet (select Linux as your OS).

So you had $40K in your account and you didn't even set up 2FA?

Without 2FA there are so many ways an attacker can obtain your password.