# N-1 to N Solution: Staging Version

**URL:** <https://forum.thegraph.com/t/n-1-to-n-solution-staging-version/3735>\
**Category:** Protocol Functionality\
**Tags:** indexer, curator\
**Created:** [November 19, 2022, 1:08am UTC](https://forum.thegraph.com/t/n-1-to-n-solution-staging-version/3735 "2022-11-19T01:08:56Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ari](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/ari/32/2747_2.png) [@ari](https://forum.thegraph.com/u/ari)\
**Post date:** [November 24, 2022, 7:21pm UTC](https://forum.thegraph.com/t/n-1-to-n-solution-staging-version/3735/10 "2022-11-24T19:21:13Z")

</div>

Exactly, because a subgraph developer communicating the intent to upgrade does not encode economic penalties in your proposal, I think GraphCast could be a good channel to broadcast this information and propagate across the network. It is still early days of GraphCast but by monitoring that channel different actors could react faster to changing conditions in the network.

More detail about GraphCast: [GRC-001: Graphcast - a Gossip Network for Indexers](https://forum.thegraph.com/t/grc-001-graphcast-a-gossip-network-for-indexers/3544)

---

_[View the full topic](https://forum.thegraph.com/t/n-1-to-n-solution-staging-version/3735)._