# The Graph Council - Meeting #13 Notes

**URL:** https://forum.thegraph.com/t/the-graph-council-meeting-13-notes/2533
**Category:** Ecosystem Updates
**Tags:** council
**Created:** [September 9, 2021, 9:22pm UTC](https://forum.thegraph.com/t/the-graph-council-meeting-13-notes/2533 "2021-09-09T21:22:30Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Brandon](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/brandon/32/1265_2.png) [@Brandon](https://forum.thegraph.com/u/Brandon)
#### Post date: [September 29, 2021, 12:18am UTC](https://forum.thegraph.com/t/the-graph-council-meeting-13-notes/2533/4 "2021-09-29T00:18:56Z")

</div>

One option for deeper Radicle adoption in The Graph ecosystem would be to have The Graph Council use [Radicle Orgs](https://radicle.xyz/blog/radicle-orgs.html) for maintaining an on-chain remote of Graph Node.

In the GIP on [Subgraph Feature Versioning](https://forum.thegraph.com/t/a-process-for-specifying-the-subgraph-api-version-and-feature-support-matrix/2004) it is specified that The Graph Council should be responsible for specifying which version of Graph Node represents the canonical subgraph functionality. Using Radicle Orgs could be one way of going about that.

---

_[View the full topic](https://forum.thegraph.com/t/the-graph-council-meeting-13-notes/2533)._