The Ethereum community has elected to do a hard fork in order to resolve the DAO exploit. The MainNet block on which the hard fork will occur is set at 1920000, which should be reached on July 20 or 21 depending on your time zone.In an email statement to clients last week about the hard fork we said:

ETH deposits and withdrawals will be disabled approximately 1 hour before the hard fork activates. Trading will continue as normal during the fork. All ETH on Kraken after the fork will be tokens of the winning chain (i.e. the chain with the most work on it). ETH deposits and withdrawals will be enabled again once the winning chain has become clearly evident.

Some interpreted this statement to mean that we would not grant access to balances on the non-dominant chain under any circumstance but this was never our intention. The statement was written from the standpoint of a “winner take all” scenario where the non-dominant chain dies out fairly quickly. Since the outcome of the fork may be more complicated than this, we want to make a number clarifications here and assure everyone that we are making preparations to be ready for any outcome of the fork and will act accordingly.How long will it take? Although the process may go smoothly and quickly, we want everyone to understand that we will be very cautious about waiting for a clearly dominant chain (with the most work on it) to emerge before enabling ETH and DAO funding again. We think this is unlikely, but depending on how things go, we may have to wait several days or more to be safe. You should not send any Ethereum or DAO deposits to Kraken until we have enable deposits. You can follow us on twitter (https://twitter.com/krakenfx) or our status page (https://status.kraken.com/) to learn when funding is enabled again. Are my funds safe with Kraken? Yes. We are taking steps to ensure that Kraken balances on both chains are secure against any replay attack. You can read more about the replay attack here:

https://www.reddit.com/r/ethereum/comments/4t2jfq/security_the_oldtonewchain_replay_attack_and_the/

Our own Kraken developer Timon Rapp has written a technical guide for exchanges and expert users on dealing with the replay attack:

https://medium.com/@timonrapp/how-to-deal-with-the-ethereum-replay-attack-3fd44074a6d8#.biqtsvw49

There are other ways to protect against the attack, but this guide has been at least partially endorsed by Ethereum co-creator Vitalik Buterin.What about my private wallets? Please be very cautious with your private Ethereum wallets and do not send any transactions during the fork to Kraken or anywhere else. Even after the fork you should be careful and understand the danger of the replay attack. If you only care about your funds on the dominant chain, then you do not need to worry about the replay attack. But if you care about funds on both chains then you will need to take precautions against the replay attack. Unfortunately, aside from the highly technical guide linked above there isn’t a comprehensive guide for more ordinary users on how to protect yourself. But here is one place with some tips and discussion that is aimed at a somewhat less technical level:

https://www.reddit.com/r/ethereum/comments/4t9mzg/quick_hf_safety_tips_for_users/

Hopefully a better guide to navigating the fork with your private wallet will be available soon on https://blog.ethereum.org/ or elsewhere. Will Kraken offer markets for the non-dominant chain? While we haven’t ruled this possibility out, we do not at the present time intend to offer trading markets for the non-dominant chain. In our view it could possibly take several weeks or more before it would even be safe to do this. What about margin positions? We highly recommend that margin positions be closed before the hard fork starts since the fork may bring a lot of unpredictable volatility or other unusual market behavior and make margin trading much riskier than normal. Depending on how the fork resolves, in order to manage the overall exchange risk, we may need at some point to do at least a partial forced closure of margin positions. This means that margin traders may possibly experience at least a partial forced closure of their positions. We will make every effort to minimize the impact and only close positions to the degree that seems necessary, but we cannot guarantee that our decision will be ideal for everyone. Margin traders who are uncomfortable with this possibility should close their positions prior to the start of the fork.What about The DAO? Caution should be exercised for all Ethereum blockchain operations during the fork, including DAO and any other Ethereum based tokens. DAO funding on Kraken will be offline during the fork and you should not send DAO transfers to Kraken or anywhere else during the fork. DAO transfers are also vulnerable to the replay attack discussed above, so you should be cautious about sending DAO transfers even after the fork