# RSKIP-291: Network Upgrade Hop (Initial Proposal) **URL:** \ **Category:** RSKIP\ **Created:** [December 14, 2021, 1:36pm UTC](https://research.rsk.dev/t/rskip-291-network-upgrade-hop-initial-proposal/257 "2021-12-14T13:36:29Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![adrian.eidelman](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@adrian.eidelman](https://research.rsk.dev/u/adrian.eidelman)\ **Post date:** [December 14, 2021, 1:36pm UTC](https://research.rsk.dev/t/rskip-291-network-upgrade-hop-initial-proposal/257/1 "2021-12-14T13:36:29Z")
Hello RSK community! I’ve just created an initial meta RSKIP for the next RSK network upgrade called Hop ([RSKIPs/RSKIP291.md at master · rsksmart/RSKIPs · GitHub](https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP291.md)). I’m proposing 2 RSKIPs to be part of Hop, which are RSKIP-264 and RSKIP-271: - RSKIP-264: [Simplified Emergency Time-locks Refresh](https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP264.md) - List item RSKIP-271: [Bridge peg-out Batching](https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP271.md) As discussed in previous RSK Community Calls, we’d like Hop to be limited in scope so it can be activated during Q1 2022 (dates to be defined) to quickly address the concerns raised by the community about the [Time-locked Emergency Multisignature](https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP201.md) introduced in RSK Iris hard fork. This is an initial proposal, discussion is now open for anyone to comment or propose other improvements. ---
**Author:** ![cypher](https://yyz2.discourse-cdn.com/flex036/user_avatar/research.rsk.dev/cypher/32/90_2.png) [@cypher](https://research.rsk.dev/u/cypher)\ **Post date:** [December 16, 2021, 6:36am UTC](https://research.rsk.dev/t/rskip-291-network-upgrade-hop-initial-proposal/257/2 "2021-12-16T06:36:21Z")
Great. I came here, to comment about this: “[BIP 0067: Fix a broken link by katesalazar · Pull Request #1202 · bitcoin/bips · GitHub](https://github.com/bitcoin/bips/pull/1202/commits/26a7824e6b744cd7137b818341d299df999ea26a)” A bip for a link? really? it seems that the main need as of now is about strenghtening nameserving and routing the way we already know. My 2 cents: Workarround the transition to decentralized NS, not using the old NICs, we can always encapsulate within. Something like [socket.io](http://socket.io) within tcp/IP. ? NICs are the current intermediaries to be addressed. ---
**Author:** ![bguiz](https://avatars.discourse-cdn.com/v4/letter/b/fbc32d/32.png) [@bguiz](https://research.rsk.dev/u/bguiz)\ **Post date:** [December 23, 2021, 3:31am UTC](https://research.rsk.dev/t/rskip-291-network-upgrade-hop-initial-proposal/257/3 "2021-12-23T03:31:01Z")
@cypher I’m not sure how your post relates to HOP or even RSKJ/ RSKIPs in general. That being said, if you are looking for DNS-like technology that is RSK-native, you might want to check out [RIF Name Service](https://developers.rsk.co/rif/rns/). ---
**Author:** ![adrian.eidelman](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@adrian.eidelman](https://research.rsk.dev/u/adrian.eidelman)\ **Post date:** [June 22, 2022, 10:28pm UTC](https://research.rsk.dev/t/rskip-291-network-upgrade-hop-initial-proposal/257/4 "2022-06-22T22:28:30Z")
The final scope for RSK Hop is now updated in RSKIP-291 [RSKIPs/RSKIP291.md at master · rsksmart/RSKIPs · GitHub](https://github.com/rsksmart/RSKIPs/blob/master/IPs/RSKIP291.md). All RSKIPs will be explained in RSK Community Call on June 23rd. ---
**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:** [June 22, 2022, 11:48pm UTC](https://research.rsk.dev/t/rskip-291-network-upgrade-hop-initial-proposal/257/5 "2022-06-22T23:48:27Z")
This link will take anyone to the post for this months community call and also the agenda for the call. > [@Community Call June/July 2022](https://research.rsk.dev/t/community-call-june-july-2022/351): > > wave everyone! I trust you have been doing great since [Community Call January/February 2022](https://research.rsk.dev/t/community-call-january-february-2022/258). I am excited to let you know that our next community call is proposed to be held on June 23rd, 2022, and we are already planning the event. We would welcome your input in the lead up to the community call. Action: Please comment below with the RSKIPs that you would like us to prioritize for discussion! Follow up: Based on this discussion, we’ll create an agenda, and then invite all of you to the dis…