# RSKIP-358: Network Upgrade (patch): Hop 4.0.1

**URL:** <https://research.rsk.dev/t/rskip-358-network-upgrade-patch-hop-4-0-1/385>\
**Category:** RSKIP\
**Created:** [October 28, 2022, 4:43pm UTC](https://research.rsk.dev/t/rskip-358-network-upgrade-patch-hop-4-0-1/385 "2022-10-28T16:43:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gino.osahon](https://yyz2.discourse-cdn.com/flex036/user_avatar/research.rsk.dev/gino.osahon/32/139_2.png) [@gino.osahon](https://research.rsk.dev/u/gino.osahon)\
**Post date:** [October 28, 2022, 4:43pm UTC](https://research.rsk.dev/t/rskip-358-network-upgrade-patch-hop-4-0-1/385/1 "2022-10-28T16:43:45Z")

</div>

Hello Community,

Adrian Eidelman has created a draft RSKIP 358 titled “Network Upgrade (patch): Hop 4.0.1”.

The purpose of this network upgrade is to fix the network issue that produced the peg-out service outage as described in the below incident report.

> **[Incident report: RSK peg-out service outage | RSK - Smart Contract Platform...](https://blog.rsk.co/noticia/incident-report-rsk-peg-out-service-outage/)**
>
> Keywords

For details about RSKIP 358, see the URL below.

> <https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP358.md>

We would really welcome your thoughts and feedback about this RSKIP, discussions are now open for anyone to comment or propose other improvements.