You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to look at constructing the NIP11 from the config. Right onw it relys on the relay operator to set the NIP11 information manually. This can and will lead to operators not always having an accurate NIP11 document as per other nip requirements. For instance, if a whitelist is enabled, the NIP11 document should not advertise NIP65 compatible per NIP65 Final Considerations #5. NIP11 also has some extra fields that can be defined. These extra fields can be abstracted from the config.yml.
The text was updated successfully, but these errors were encountered:
I need to look at constructing the NIP11 from the config. Right onw it relys on the relay operator to set the NIP11 information manually. This can and will lead to operators not always having an accurate NIP11 document as per other nip requirements. For instance, if a whitelist is enabled, the NIP11 document should not advertise NIP65 compatible per NIP65 Final Considerations #5. NIP11 also has some extra fields that can be defined. These extra fields can be abstracted from the config.yml.
The text was updated successfully, but these errors were encountered: