Alright... Here's what I changed:
OWNER_NPUB - This should obviously be changed to the npub you will be using Haven with.
RELAY_URL - This should be the domain where the relay will be accessible.
Leave the rest of the settings in this top section of the .env as they are unless you have a specific reason to change them and pop down to the Private Relay Settings.
PRIVATE_RELAY_NAME - You can name it whatever you like, but probably don't want to leave it as "utxo's private relay." Each of the other sections allow you to change their name, too.
PRIVATE_RELAY_NPUB - This should be the npub you plan to use the relay with. The private relay will only accept notes authored by that npub. Same applies for all the other sections below that allow you to set the relay npub.
PRIVATE_RELAY_DESCRIPTION - You can leave this as is or change it as you see fit. It just gives those who check the relay description document an idea of what the relay is for.
PRIVATE_RELAY_ICON - Slap in a URL for an icon for your relay. Think of it like your relay's profile picture. Keep it small. You can even have a separate icon for each of Haven's relays, if you want.
I haven't changed anything in the Private Relay Rate Limiters section.
Your "Chat" relay is used for receiving DMs. Apart from the fields similar to the Private relay setup, you may want to adjust the WoT depth, how often the WoT is refreshed, or the minimum number of followers. These settings dictate who can post messages to your DM inbox, so you don't get a bunch of spam DMs. But, if you want to see DMs from people outside of your WoT, you may want to make these less strict by reducing the CHAT_RELAY_MINIMUM_FOLLOWERS to 0, but know that you will start getting spam DMs, too.
Make similar updates as you did in the Private Relay section to the Outbox and Inbox sections, too.
Your Import Settings may also need to have the date updated, depending on when you joined Nostr. Haven will import your notes from other relays from that date to present, based on the relays you instruct it to pull from in the relays_import.json document.
Finally, you may need to add some values in the AWS Backup Settings, if you are having Haven backed up to AWS.
The next document you will want to make sure has all the relays listed that you want to pull from is the relays_import.json. Make sure it is pulling from any and all relays you can remember writing to in the past. It's already including relay.nostr.band, which is an aggregator, so it should be able to find most of your notes, regardless.
And to round it all out, you'll want to edit the relays_blastr.json to include any relays you want your public notes mirrored to. This will only be notes that you are writing to your Haven outbox relay. The default relays are pretty decent, but you may want to make some adjustments. Note, you should not choose any relays that require AUTH for write access, as Haven will be unable to sign their AUTH requests.
Maybe utxo the webmaster 🧑💻 (npub1utx…50e8) and/or Anthony Accioly (npub1a6w…0tyc) can review the above to ensure I haven't given any bad advice. 😂
Dikaios1517
npub1ku…v3lhe
2025-06-13 22:45:12
in reply to nevent1q…czuu
Author Public Key
npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhePublished at
2025-06-13 22:45:12Event JSON
{
"id": "a283899d16167d057f42be4f00cec5d36ddf13b8521ee46a2699fda52f5cf5fb",
"pubkey": "b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
"created_at": 1749854712,
"kind": 1,
"tags": [
[
"e",
"644e1e898840ce75a55236b7ec90e43d0331253a476361d7cb85c8b275f10231",
"",
"root",
"f7922a0adb3fa4dda5eecaa62f6f7ee6159f7f55e08036686c68e08382c34788"
],
[
"client",
"asknostr.site"
],
[
"p",
"f7922a0adb3fa4dda5eecaa62f6f7ee6159f7f55e08036686c68e08382c34788"
],
[
"p",
"e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
]
],
"content": "Alright... Here's what I changed:\n\nOWNER_NPUB - This should obviously be changed to the npub you will be using Haven with.\nRELAY_URL - This should be the domain where the relay will be accessible.\n\nLeave the rest of the settings in this top section of the .env as they are unless you have a specific reason to change them and pop down to the Private Relay Settings.\nPRIVATE_RELAY_NAME - You can name it whatever you like, but probably don't want to leave it as \"utxo's private relay.\" Each of the other sections allow you to change their name, too.\nPRIVATE_RELAY_NPUB - This should be the npub you plan to use the relay with. The private relay will only accept notes authored by that npub. Same applies for all the other sections below that allow you to set the relay npub.\nPRIVATE_RELAY_DESCRIPTION - You can leave this as is or change it as you see fit. It just gives those who check the relay description document an idea of what the relay is for.\nPRIVATE_RELAY_ICON - Slap in a URL for an icon for your relay. Think of it like your relay's profile picture. Keep it small. You can even have a separate icon for each of Haven's relays, if you want.\n\nI haven't changed anything in the Private Relay Rate Limiters section.\n\nYour \"Chat\" relay is used for receiving DMs. Apart from the fields similar to the Private relay setup, you may want to adjust the WoT depth, how often the WoT is refreshed, or the minimum number of followers. These settings dictate who can post messages to your DM inbox, so you don't get a bunch of spam DMs. But, if you want to see DMs from people outside of your WoT, you may want to make these less strict by reducing the CHAT_RELAY_MINIMUM_FOLLOWERS to 0, but know that you will start getting spam DMs, too.\n\nMake similar updates as you did in the Private Relay section to the Outbox and Inbox sections, too.\n\nYour Import Settings may also need to have the date updated, depending on when you joined Nostr. Haven will import your notes from other relays from that date to present, based on the relays you instruct it to pull from in the relays_import.json document.\n\nFinally, you may need to add some values in the AWS Backup Settings, if you are having Haven backed up to AWS.\n\nThe next document you will want to make sure has all the relays listed that you want to pull from is the relays_import.json. Make sure it is pulling from any and all relays you can remember writing to in the past. It's already including relay.nostr.band, which is an aggregator, so it should be able to find most of your notes, regardless.\n\nAnd to round it all out, you'll want to edit the relays_blastr.json to include any relays you want your public notes mirrored to. This will only be notes that you are writing to your Haven outbox relay. The default relays are pretty decent, but you may want to make some adjustments. Note, you should not choose any relays that require AUTH for write access, as Haven will be unable to sign their AUTH requests.\n\nMaybe nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 and/or nostr:npub1a6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajq7w0tyc can review the above to ensure I haven't given any bad advice. 😂",
"sig": "bd493a1d0914eca917a77d64f3cb33369b011a07e633200ff9531f03ea3cbd9bbf55d8df28ccbf6df04519f66bff95788d3d3c268173d293f66fc60aaed19a30"
}