Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use OWNER_PUBKEY to build the WoT network #53

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dtonon
Copy link

@dtonon dtonon commented Sep 19, 2024

Currently RELAY_PUBKEY is used to build the WoT network, but this is misleading, in fact in the example .env it is stated "not your npub!", but it actually contains the owner (UTXO) pubkey.
Since RELAY_PUBKEY is used for NIP-11 info, make sense to add a OWNER_PUBKEY env and use it to build the WoT network.

The alternative would be to ask the user to follow himself with the relay account, and add a one level to the following discovering; too complex.

@barrydeen
Copy link
Contributor

I agree that the name is better, but I think most people won't be creating a pubkey for their relays. but now so many people are running it this way it will break their relays if they update :\

@barrydeen
Copy link
Contributor

I think what i'll do is merge this in for v0.2.0 so relay operators know to at least expect some breaking changes

@dtonon
Copy link
Author

dtonon commented Sep 19, 2024

Yes, it is an hassle, but better now than later.
If OWNER_PUBKEY is missing the app crashes explaining the matter.
The next major version seems a good moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants