Skip to content

Bug: Primal Studio profile metadata not properly published across configured relays #13

@tummtukote

Description

@tummtukote

Describe the bug

The Nostr profile of Primal Studio has incomplete metadata distribution across its configured relays, which prevents proper discovery in some clients.

Key issues:

  • relay.nostr.band is inactive.
  • Profile metadata (kind 0) is not available on the listed relays.
  • Relay list (kind 10002) exists only on:
    • wss://premium.primal.net
    • wss://relay.primal.net
  • Contact list (kind 3) exists only on:
    • wss://premium.primal.net

Steps to reproduce

  1. Open the Nostr profile of Primal Studio in a client that relies on relay list discovery.
  2. Observe missing profile metadata, relay discovery, or incomplete history.

Expected behavior

  • Profile metadata (kind 0), relay list (kind 10002), and contact list (kind 3)
  • should be published and replicated across multiple active configured relays.

Environment

  • Observed in Nostria and other clients using standard relay discovery.

Additional context

Incomplete relay distribution makes profile discovery and full history retrieval unreliable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions