From 57f4d29b4c37df59a83b9fe745d6f93a82c3e832 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Wed, 24 Jan 2024 04:31:12 -0500
Subject: [PATCH] Update README.md

---
 README.md | 23 ++++++++++++++++++++++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index b16b4b4..869b548 100644
--- a/README.md
+++ b/README.md
@@ -1 +1,22 @@
-# rfc-index
\ No newline at end of file
+# Vac RFC Index
+
+# RFCs
+
+This repository contains specifications for the [Vac](https://vac.dev), [Waku](https://waku.org/), [Nomos](https://nomos.tech/), [Codex](https://codex.storage/), and [Status](https://status.app/) projects.
+The RFCs, ([Request for Comments](https://en.wikipedia.org/wiki/Request_for_Comments)), 
+included in this repository will be managed by Vac after the specifcations have reached a rough consensus within the working groups.
+
+Vac is an R&D org creating modular p2p protocols for private, secure, and censorship-resistant communication.
+A detailed, albeit slightly outdated (2019), explanation of Vac and its design goals can be found [here](https://vac.dev/vac-overview).
+
+Vac, while having a core team of maintainers and contributors, is an open and permission-less organization.
+
+**See [rfc.vac.dev](https://rfc.vac.dev) for an easy to browse index of all RFCs.**
+
+## Contributing
+
+Please see [1/COSS](https://rfc.vac.dev/spec/1/) for general guidelines and spec lifecycle.
+
+Feel free to join the [Vac discord](https://discord.gg/Vy54fEWuqC). There's a channel specifically for RFC discussions.
+
+Here's the project board used by core contributors and maintainers: [Projects](https://github.com/orgs/vacp2p/projects/5)