# INCIDENT: Peerunity fork

**URL:** <https://discourse.peercoin-library.org/t/incident-peerunity-fork/3875>\
**Category:** General\
**Created:** [April 27, 2016, 4:26am UTC](https://discourse.peercoin-library.org/t/incident-peerunity-fork/3875 "2016-04-27T04:26:11Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Sunny\_King](https://discourse.peercoin-library.org/user_avatar/discourse.peercoin-library.org/sunny_king/32/1937_2.png) [@Sunny\_King](https://discourse.peercoin-library.org/u/Sunny_King)\
**Post date:** [April 27, 2016, 4:26am UTC](https://discourse.peercoin-library.org/t/incident-peerunity-fork/3875/1 "2016-04-27T04:26:11Z")

</div>

Peerunity clients have forked from main peercoin blockchain as of block height 233762 ([https://www.peercointalk.org/index.php?topic=4538.0](https://www.peercointalk.org/index.php?topic=4538.0))

Impact:  
Peerunity v0.2.0

Severity:  
Moderate. Not affecting wallets or main blockchain. Not affecting peercoin v0.5.3. Peerunity users are recommended to temporarily suspend transaction activity until a hot fix release is ready for upgrade.

Resolution:  
Fixed as of peerunity v0.2.1

---

_[View the full topic](https://discourse.peercoin-library.org/t/incident-peerunity-fork/3875)._