Nostr notes by Cypher Guide (Digital Nomad)

CypherGuide is a no-KYC, Nostr + Lightning lodging protocol. ...

2026-10-17T09:26:04Z

CypherGuide is a no-KYC, Nostr + Lightning lodging protocol. It's experimental and we have no live hosts yet.
We're looking for a small number of hosts (homestays, rooms, retreats) to try it end to end: sign a listing, receive a test booking, tell us what breaks. Early hosts get a lower suggested protocol contribution (1%) and, more importantly, direct input into the design.
You'd be a pilot, not a customer. Real money is optional while we test. Reply here if you're interested, and please don't send keys or sensitive details in public.
#nostr #bitcoin #homestay #cypherguide

Update on the WoT agent RFC (RFC-0017) Thanks to everyone who ...

2026-10-17T08:44:28Z

Update on the WoT agent RFC (RFC-0017)
Thanks to everyone who picked apart the draft last week. Two points changed the RFC:
• Two co-signing keys controlled by one person can fake stays. We now require down-weighting of closed groups, a reputation cap for them, and a simulation test of the attack.
• Real communities form dense clusters too, so a second test measures false positives on benign clusters. No fixed "X%" cutoff: continuous weighting calibrated by simulation.
Also added: NIP-90 room requests should be encrypted to a designated agent by default, since they reveal travel intent.
Still true: agents never hold or move sats, and they are labeled as AI. https://github.com/greenweaveglobal/cypherguide/blob/main/RFC/0017-stay-assistant-agents.en.md
#nostr #nip90 #webOfTrust #cypherguide

How should a P2P, no-custody lodging protocol earn money? We ...

2026-10-17T06:58:19Z

How should a P2P, no-custody lodging protocol earn money?
We looked at this honestly. In our flow a modified client can simply skip the fee invoice, and the host still gets paid. So a "mandatory protocol fee" isn't enforceable at the protocol level.
Our direction (RFC-0020, Draft):
• Phase 1: an optional, transparent protocol contribution. Suggested 2%, 1% for early hosts, one tap to set it to 0.
• Phase 2: charge for services that can actually be gated (real arbitration, Proof-of-Stay attestation, discovery) once they exist.
We rejected a verified-fee-by-server model: it brings back a central chokepoint.
Honest expectation: contributions will cover infrastructure, not salaries.
Critique welcome: https://github.com/greenweaveglobal/cypherguide/blob/main/RFC/0020-protocol-fee-enforcement.en.md
#nostr #bitcoin #lightning #opensource #cypherguide

Small things that now work in CypherGuide: • Vietnamese and ...

2026-10-17T00:51:51Z

Small things that now work in CypherGuide:
• Vietnamese and English UI with no mixed-language leftovers (a CI check now blocks hard-coded strings)
• Image upload via NIP-96 servers with NIP-98 auth, with automatic fallback
• Rate-limited docs assistant that answers from local RFCs even without an LLM key
• Our own relay: wss://relay.cypherguide.org
Not done yet: first real hosts, relay-distributed listings, real arbitrators. Source: https://github.com/greenweaveglobal/cypherguide
#nostr #opensource #cypherguide

Good question, and to be clear: the RFC doesn't set an 80% ...

2026-10-10T08:41:42Z

In reply to nevent1q…k6s4
_________________________

Good question, and to be clear: the RFC doesn't set an 80% cutoff. That number isn't in the draft. It says "mostly" on purpose and lists the exact method and cap as an open question (#8), because we have no empirical failure data to justify a number. The plan is to avoid a hard cutoff: weight edges continuously and calibrate by simulation against two cases, a closed fake cluster (attack) and dense benign clusters like meetups or DAOs. The failure we most want to measure is false positives on real communities. If you know of data or papers on WoT attacks, pointers welcome.

Thanks, this is exactly the weak spot. Two signatures only prove ...

2026-10-10T04:06:50Z

In reply to nevent1q…vl27
_________________________

Thanks, this is exactly the weak spot. Two signatures only prove two keys agree, not that two independent people met. We're adding a collusion-resistance requirement to RFC-0017's WoT module: down-weight closed groups of npubs that mostly co-sign each other, cap the reputation a closed group can create on its own, and make your regression test (how much can a fake guest/host pair manufacture before it needs outside trust?) a release condition. Credited in the Discussion section.

Agreed, the AI label is the one line that can't be ...

2026-10-10T04:06:29Z

In reply to nevent1q…a3nd
_________________________

Agreed, the AI label is the one line that can't be negotiable. Kept as is.

Good point on signed, timestamped inputs so a host can later ...

2026-10-10T04:05:31Z

In reply to nevent1q…w59d
_________________________

Good point on signed, timestamped inputs so a host can later prove what the agent saw at booking time. We're adding it as an optional audit feature, with the constraint that inputs contain npub relationships, so they're shared only with the parties involved, not published. We're not integrating any third-party service in this RFC.

CypherGuide is exploring AI agents on Nostr to help guests and ...

2026-10-09T10:21:46Z

CypherGuide is exploring AI agents on Nostr to help guests and hosts, without any agent ever holding or moving sats.
Phase 1 proposes three narrow jobs:
🤖 Stay Q&A: answers from public docs and listing info. Never handles door codes or Wi-Fi passwords.
🕸️ Deterministic Web-of-Trust score: plain code, no LLM. Anyone can rerun it and see why a score is what it is. A hint only, never an automatic block.
🔎 Room suggestions via NIP-90: the agent suggests listings. Guest and host close the deal themselves.
Hard limits:
• Its own npub, never the project's official key
• Separate VPS from the relay
• Tool allowlist: no shell, no code edits, no transfers
• All Nostr content treated as untrusted input
• Clearly labeled as an AI, no fake reviews or zaps
• Posts and proactive messages approved by a human
Deliberately left out for now: hold-invoice deposits, AI arbitration, auto-pricing, and fees routed through an agent wallet. Money decisions stay with humans and the protocol.
It's a draft and we want it picked apart:
→ Which NIP-90 kind should room-search requests use?
→ How would you game a public WoT score?
→ What should an agent never be allowed to do?
Read it: https://github.com/greenweaveglobal/cypherguide/blob/main/RFC/0017-stay-assistant-agents.en.md
#nostr #bitcoin #lightning #nip90 #cypherpunk #opensource #cypherguide

📜 RFC-0017 (Draft): AI agents for P2P stays, with no custody ...

2026-10-02T09:45:27Z

📜 RFC-0017 (Draft): AI agents for P2P stays, with no custody
CypherGuide is exploring AI agents on Nostr to help guests and hosts, without any agent ever holding or moving sats.
Phase 1 proposes three narrow jobs:
🤖 Stay Q&A: answers from public docs and listing info. Never handles door codes or Wi-Fi passwords.
🕸️ Deterministic Web-of-Trust score: plain code, no LLM. Anyone can rerun it and see why a score is what it is. A hint only, never an automatic block.
🔎 Room suggestions via NIP-90: the agent suggests listings. Guest and host close the deal themselves.
Hard limits:
• Its own npub, never the project's official key
• Separate VPS from the relay
• Tool allowlist: no shell, no code edits, no transfers
• All Nostr content treated as untrusted input
• Clearly labeled as an AI, no fake reviews or zaps
• Posts and proactive messages approved by a human
Deliberately left out for now: hold-invoice deposits, AI arbitration, auto-pricing, and fees routed through an agent wallet. Money decisions stay with humans and the protocol.
It's a draft and we want it picked apart:
→ Which NIP-90 kind should room-search requests use?
→ How would you game a public WoT score?
→ What should an agent never be allowed to do?
Read it: https://github.com/greenweaveglobal/cypherguide/blob/main/RFC/0017-stay-assistant-agents-phase1.en.md
#nostr #bitcoin #lightning #nip90 #cypherpunk #opensource #cypherguide