> Neighborhoods are leading segments with no specific meaning, whose purpose is to help route to the right area. At this time, there is no official list of neighborhoods, but the following list of examples should illustrate what might constitute a neighborhood:
> `crypto.` for ledgers related to decentralized crypto-currencies such as Bitcoin, Ethereum, or XRP.
> `sepa.` for ledgers in the Single Euro Payments Area.*
> `dev.` for Interledger Protocol development and early adopters
From "ILP Addresses - v2.0.0" [2]:
> Example Global Allocation Scheme Addresses
> `g.acme.bob` - a destination address to the account "bob" held with the connector "acme".
> `g.us-fed.ach.0.acmebank.swx0a0.acmecorp.sales.199.~ipr.cdfa5e16-e759-4ba3-88f6-8b9dc83c1868.2` - destination address for a particular invoice, which can break down as follows:
> - Neighborhoods: us-fed., ach., 0.
> - Account identifiers: acmebank., swx0a0., acmecorp., sales, 199 (An ACME Corp sales account at ACME Bank)
> - Interactions: ~ipr, cdfa5e16-e759-4ba3-88f6-8b9dc83c1868, 2
And from [3] "Payment Pointers and Payment Setup Protocols":
> The following payment pointers resolve to the specified endpoint URLS:
$example.com -> https://example.com/.well-known/pay
$example.com/invoices/12345 -> https://example.com/invoices/12345
$bob.example.com -> https://bob.example.com/.well-known/pay
$example.com/bob -> https://example.com/bob
<meta
name="monetization"
content="$wallet.example.com/alice">
[2] https://github.com/interledger/rfcs/blob/master/0015-ilp-add...
[3] "Payment Pointers and Payment Setup Protocols" https://interledger.org/rfcs/0026-payment-pointers/