$ git log --author=xmrhost
[$ ] Contributions — the verifiable track record
// NAME
contributions — upstream open-source contributions, CVE records authored, security advisories, conference talks, and papers from the xmrhost.io editorial team. The verifiable track record behind the pseudonymous bylines.
// WHY THIS PAGE
Pseudonymous publication only carries authority when the pseudonym has a verifiable record. A handle that posts opinions with no traceable contribution to the technical fields it claims expertise in is indistinguishable from a marketing voice. This page is the brand's commitment to building that record openly, entry by entry, and to staying honest about the gap between the brand's age and its track record.
// STATUS
$ echo "the page is honestly empty"
The brand launched in 2026; the contribution record is being built in the open from zero. Rather than fabricate entries to fill the page (an integrity violation the brand explicitly rejects), this page sits empty until the first genuine contribution lands. Expected first entries include:
- Tor / OSS contributions — relay-operator documentation fixes, tor.conf clarifications.
- Monero ecosystem — Feather wallet documentation, BTCPay / OxaPay integration notes.
- Linux hardening — KSPP guidance, auditd ruleset contributions.
- Threat-model writeups — material that ends up on /threat-models often originates as a separate community publication first.
- Conference appearances — FOSDEM (privacy devroom), Pass The Salt, 36C3, Tor Meetings. Submissions go out in the months following launch.
// the operator's editorial commitment is to ship at least 1 verifiable upstream contribution per quarter starting from launch. The first verified entry will replace this empty-state.
// PLANNED — NOT YET SHIPPED
$ cat /etc/xmrhost/contributions/planned
Editorial commitment, NOT credit. The targets below are the upstream patches, documentation contributions, and conference submissions the editors are working on for the next two quarters. Listed openly so the brand can be held to its commitment. When a target ships, it moves to the "Verified contributions" section above with the upstream link filled in. A target that doesn't ship by its declared quarter is honestly surfaced as "deferred" in the next page revision rather than silently removed.
| // target | // kind | // by | // upstream | // quarter |
|---|---|---|---|---|
| Tor: relay-operator FAQ — document the obfs4-bridge bandwidth-sharing pattern | OSS pull requests / patches | 0xLambda | gitlab.torproject.org/tpo/web/community | 2026-Q3 |
| i2pd: add a configuration-recipe page for floodfill operators behind NAT | Upstream documentation contributions | 0xLambda | github.com/PurpleI2P/i2pd-docs | 2026-Q3 |
| lokinet: clarify staked-service-node uptime-vs-stake recovery in the operator docs | OSS pull requests / patches | 0xLambda | github.com/oxen-io/lokinet/docs | 2026-Q4 |
| Feather wallet: subaddress workflow doc for merchant-side recurring payments | Upstream documentation contributions | Vex | github.com/feather-wallet/feather-docs | 2026-Q3 |
| Pass The Salt 2027 — threat models for self-hosted privacy infrastructure | Conference talks | Vex | passthesalt.ubicast.tv | 2027-Q3 |
// these are not yet contributed. Don't cite them. Don't link them as if they were shipped. Wait for them to land in the verified section above (with the upstream URL filled in) before treating them as authority signals.
// VERIFICATION
$ man 7 verify
Every entry on this page links to the upstream record (GitHub PR, GitLab MR, CVE detail page, conference video, arXiv preprint). The reader is invited to dereference the link and verify the contribution exists, was accepted by the upstream maintainer, and was authored by the pseudonym the entry credits. Entries without verifiable upstream records do not appear on this page.
If you encounter an entry that does not verify, mail /contact (topic=other) with the date + title. Verification failures get a retraction notice in the next quarterly update.
// SEE ALSO
$ ls /usr/share/doc/xmrhost/about
- /about — brand identity + operating practice.
- /about/team — editor masthead with Schema.org Person records.
- /notes — long-form editorial.