Support MoaV¶
MoaV is free software built for people who can't rely on the internet being open. There are four ways to help, and the first one is worth more than the rest.
Run a server¶
This is the highest-leverage thing you can do. Every MoaV server is capacity that didn't exist before — for your family, your colleagues, or people you'll never meet. The project doesn't run infrastructure on anyone's behalf; the network is the people running servers.
A $5/month VPS or a Raspberry Pi in a spare room is enough. Quick Start takes about ten minutes.
If you already run one, the most useful next step is giving bundles to people who need them — see sharing safely first, because how you distribute matters as much as that you do.
Donate bandwidth instead of users¶
You can help even without users of your own, by relaying traffic for existing circumvention networks. Both are opt-in, capped, and run alongside everything else:
- Psiphon Conduit — your spare bandwidth carries Psiphon traffic for people in censored regions.
- Tor Snowflake — your server becomes a Snowflake proxy, helping people reach Tor.
You can also donate configs to MahsaNet, which distributes them to users in Iran who have no server of their own. That turns spare capacity on your server into access for someone who can't set one up.
Contribute code¶
Bugs, protocols, docs, packaging — all of it. Development & Testing covers running from source, how CI and the end-to-end suite work, and the one rule that shapes the project: every bug fixed ships a regression test in the same PR.
Bug reports count. A reproducible report with moav doctor output is often more work than the fix, and it's the thing that turns "it's broken for me" into something that stays fixed for everyone.
Never paste bundles,
.envcontents or share links into an issue — they contain live keys.
Translate¶
Documentation only in English is a real barrier for exactly the people MoaV exists for. A Persian setup guide is worth more than another protocol.
The single highest-value target is the user bundle guide — the README.html template that ships inside every bundle. It is the one document a person reads while trying to get online, often on a phone, often in a hurry. It already ships English and Farsi; every additional language there reaches people who never touch this site.
After that, in order:
- The bundle guide template (
scripts/lib/bundle-readme.sh/ its template in the MoaV repo) - The project READMEs — MoaV and moav-client. MoaV already has
README-fa.mdas the pattern to follow. - The docs pages read under pressure: Quick Start, Setup, DNS Configuration, Client Apps, Troubleshooting, OPSEC
Deep developer docs can stay English.
Partial translations are welcome — a translated Quick Start on its own is useful. Two things we ask:
- Human-reviewed only. A machine-translated DNS or OPSEC instruction that's subtly wrong is worse than an English one that's right. Unreviewed drafts get marked as drafts.
- English stays the source of truth, so a translated page can be checked against it when things change.
The scaffolding is ready — start here
Translating the Docs is the full walkthrough: which page to pick, where the file goes, what must stay untranslated, and how to preview your work before opening a pull request.
Farsi and Russian are open now. Copy one English page into docs/fa/ or docs/ru/, translate it, and open a PR — untranslated pages fall back to English, so a single page is a complete contribution. For another language, open an issue and we'll add it.
Donate money¶
Funds go to infrastructure the project actually needs — test servers for the end-to-end suite, domains, and build capacity. Not salaries.
Cards, PayPal, recurring
| Platform | Link |
|---|---|
| GitHub Sponsors | github.com/sponsors/shayanb |
| Buy Me a Coffee | buymeacoffee.com/pangana |
Crypto — click an address to copy it
Bitcoin (BTC)
Ethereum (ETH) — works on all EVM chains at this same address: Ethereum mainnet and every L2 (Arbitrum, Optimism, Base, Polygon, Gnosis, zkSync, and so on), plus any ERC-20 token such as USDC, USDT or DAI.
Monero (XMR)
Zcash (ZEC)
u1pclheucppc87qlffh9m8wjfw87w2nka40w9nxjuqnyppj0kx9xp7z9rg6wx556662y5f8dtfyeynmm2lnz5aqvaqzmnpajlq0mnmkntdqzqqegk8lwv09cnudf3ttzm3878p3030j3lwupj257rmmv9p3ea32hgwsuf3jdh8ycv7q587
Lightning
lno1zrxq8pjw7qjlm68mtp7e3yvxee4y5xrgjhhyf2fxhlphpckrvevh50u0q0zdgjjahpdv7tnd9vstumyrw43snsmfmlzv0pgkqrjkgy48tsne6qsr0k64d8rz4k394pmre2rgnmstdxqsfj0w4dsmq2ec73ssek5wzqtqqv7argu9ptk09h9vfvvvham5xnwe306zjw6lptxx0d2yfk5rlvznjwefmsrmmpu8qnkqmghe0v96c8qy3m3nqgm977ay8f5p6k2d2ll2j3knnc8c4s6haufe203jx4ufy8z25tsscqqseg8jzh2qykejnc9sp2v4qm3z2q
Lightning Address
Tron — accepts TRX and TRC-20 tokens (USDT, USDC). Tron has its own address format, so this one is not interchangeable with the EVM address above.
Verify the address
Addresses are long and easy to spoof. Take them from this page or the repository over HTTPS, and check the first and last characters after pasting. We will never DM you an address.
The addresses above are generated at build time from .github/FUNDING.yml in the MoaV repository, which is the single source of truth — so what you see here is whatever that file says, and it cannot drift from the repo.
Just here to use it?¶
That's fine — that's the point. If you want to help without running anything, the most useful things are: tell someone who needs it, report what breaks, and don't share bundles in public channels where they'll be collected and blocked.