05 — private
Private club
A reserved seat for a closed banking group. The name is unpublished until the club publishes itself.
01 — Identity
What this club is
Not every PATH network is a public club. A banking group can run a directory that never answers a stranger, with members that never appear on this register by name. The protocol still applies: the formats are the same, the discovery document is still required inside the club, and ring 3 still never leaves the operator.
This row is a hole that was declared on purpose. It tells a reader that private clubs are expected, without pretending to list them.
When such a club chooses to be listed, it replaces this reserved seat. Until then there is no site to visit and no member to name.
02 — Datasheet
Declared terms
A network chooses these. The protocol requires that they be public before anyone joins.
- Legal name
- Unpublished
- Slug
- private
- Jurisdiction
- —
- Admitted
- —
- Sonar
- central
- Holder confirmation
- required
- Sonar access
- member_credential
- Hashing
- server_side
- Hash function
- argon2id
- Search log retention
- 30 days
- Rulebook
- Unpublished
- Address profiles
- relationship
03 — Finder
What a member is consenting to
central
The network holds the index and answers. It sees the searches.
server_side
The hash protects the database, not members from the network. Identifiers being searched are visible to the club.
member credential
Directory queries require a member credential. Reciprocity is enforceable.
required
What a destination accepts is answered by the holder. The directory does not speak for its members on capability.
Members
Who sits in the club
Unpublished. A reserved club does not name its members on this register.
- 01PATH-CORE.DiscoveryPATH-CORE
- 02PATH-FINDER.RelationshipPATH-FINDER