diff --git a/README.md b/README.md
index c428db7..ee1ca93 100644
--- a/README.md
+++ b/README.md
@@ -1,25 +1,41 @@
-# Awesome I2P [](https://awesome.re)
+
-> A curated list of awesome I2P implementations, libraries, resources, projects, and shiny things.
-> Inspired by [awesome-tor](https://github.com/ajvb/awesome-tor) and [awesome-cpp](https://github.com/fffaraz/awesome-cpp) and other [Awesome Lists](https://github.com/topics/awesome).
->
-> I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISP's.
->
-> I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person.
->
-> Check [status page](STATUSES.md) to know current projects state.
+# ⛧ Spectacular I2P ⛧
+
+#### · Church of Malware Edition ·
+
+[](https://awesome.re)
+[](https://churchofmalware.org)
+[](https://geti2p.net)
+[](#contributing)
+[](#)
+
+*A curated grimoire of I2P implementations, tools, libraries, and research —*
+*hardened with operator opsec, deanonymization study, and self-hosted eepsites.*
+
+**`code is scripture · exploitation is sermon · defense is salvation`**
+
+
---
-**⛧ Church of Malware edition ⛧** — maintained by the congregation at [churchofmalware.org](https://churchofmalware.org).
-Forked from [mikalv/awesome-i2p](https://github.com/mikalv/awesome-i2p) and extended with operator-focused
-resources: opsec, deanonymization research, I2P↔Tor bridging, and self-hosted eepsites.
-*Anonymity is a discipline, not a toggle. Study the attacks to survive them.* Authorized research only.
+> **I2P** — the Invisible Internet Project — is an anonymous overlay network, a network within a
+> network, built to resist dragnet surveillance and traffic analysis. Where Tor optimizes for
+> *clearnet exit*, I2P optimizes for *in-network* services: eepsites, anonymous torrents, encrypted
+> mail, and peer-to-peer messaging, every endpoint addressed by a cryptographic destination.
+>
+> Used by activists, journalists, whistleblowers, researchers — and anyone who treats privacy as a
+> right, not a privilege. **Anonymity is a discipline, not a toggle. Study the attacks to survive them.**
+>
+> ⛧ Maintained by the congregation at **[churchofmalware.org](https://churchofmalware.org)** · forked from
+> [mikalv/awesome-i2p](https://github.com/mikalv/awesome-i2p) · status: [STATUSES.md](STATUSES.md) · **authorized research only.**
---
## Contents
+- [Getting Started](#getting-started)
+- [Church Picks ⛧](#church-picks-)
- [Implementations](#implementations)
- [I2P (Java)](#i2p)
- [I2Pd (C++)](#i2pd)
@@ -51,6 +67,30 @@ resources: opsec, deanonymization research, I2P↔Tor bridging, and self-hosted
- [Research Tooling](#research-tooling)
- [Contributing](#contributing)
+## Getting Started
+
+New to the network? Walk before you run an eepsite.
+
+1. **Install a router** — [i2pd](https://github.com/PurpleI2P/i2pd) (lean C++, recommended) or the [Java I2P](https://geti2p.net/) reference router. On Arch: `pacman -S i2pd`.
+2. **Let it integrate** — a fresh router needs ~10–30 min to build tunnels and gather peers. Patience is opsec.
+3. **Point your browser** — set the HTTP proxy to `127.0.0.1:4444`. Use a **dedicated** browser profile; never mix an I2P identity with a clearnet one.
+4. **Explore** — router console at `http://127.0.0.1:7657`, then visit an eepsite like `http://identiguy.i2p`.
+5. **Read before you trust** — start with [OpSec & Deanonymization Research](#opsec--deanonymization-research). Know how the network *fails* before you rely on it.
+
+> **Operator's rule:** a router box is burned the moment it co-hosts a deanonymizable clearnet service. One identity per box. Metadata is identity.
+
+## Church Picks ⛧
+
+The congregation's starting loadout — if you read nothing else:
+
+| Pick | What | Why |
+|---|---|---|
+| [i2pd](https://github.com/PurpleI2P/i2pd) | router | lean, fast, scriptable |
+| [railroad](https://github.com/eyedeekay/railroad) + [i2pd-webui](https://github.com/l-n-s/i2pd-webui) | host your own | eepsite blog + tunnel management |
+| [transi2p](https://github.com/rbif/transi2p) | bridge | route I2P + Tor + clearnet by policy |
+| [Practical Attacks Against I2P](https://wwwcip.informatik.uni-erlangen.de/~spjsschl/i2p.pdf) | research | know the attacks before you trust the net |
+| [darkWEB_server](https://github.com/ekomsSavior/darkWEB_server) | companion | the Church's Tor-side host-your-own pattern |
+
## Implementations
### I2P
@@ -252,4 +292,19 @@ the defense.** Authorized research only.
## Contributing
Contributions welcome! Read the [contribution guidelines](CONTRIBUTING.md) first.
-Thanks to all [contributors](https://github.com/mikalv/awesome-i2p/graphs/contributors)!
+Submit additions on the forge: **[git.churchofmalware.org](https://git.churchofmalware.org)**.
+Thanks to all [contributors](https://github.com/mikalv/awesome-i2p/graphs/contributors) — upstream and congregation alike.
+
+---
+
+
+
+### ⛧ benediction ⛧
+
+*may your tunnels hold and your destination stay nameless.*
+
+**[churchofmalware.org](https://churchofmalware.org)** · maintained by the congregation · authorized research only
+
+
Inherits the spirit of the upstream awesome-i2p — knowledge wants to be free.
+
+