IETF Logo Mail Archive

[Uri-review] Provisional URI scheme registration request: "nostr"

alex@alexgleason.me Thu, 23 July 2026 15:42 UTC

Return-Path: <alex@alexgleason.me>
X-Original-To: uri-review@mail2.ietf.org
Delivered-To: uri-review@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 80B3011D908D3 for <uri-review@mail2.ietf.org>; Thu, 23 Jul 2026 08:42:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784821337; bh=eB3+/TR9HHCdZNO6HiiAd2F93w7ND4ZHvWsMfCz8E3c=; h=Date:From:To:Cc:Subject; b=XfHpm+9cZObMR4uIxvw6n7PN52Kr5ZuL1PXToPQEFHJZvHLCnSuP24Yxf7vLdMJY0 bKXqenHi6VhQ9k2FZ/UME/ppcFdZtPY47S1TlqXZnfRTywVhgF8FJrSo+P3mcgR0i8 lbtIR+XoiZea1VTkgMcnAq2yFg9tzBZi0RqXOH74=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level:
X-Spam-Status: No, score=-1.306 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=alexgleason.me
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yGCpSkVeXT5 for <uri-review@mail2.ietf.org>; Thu, 23 Jul 2026 08:42:16 -0700 (PDT)
Received: from box.alexgleason.me (unknown [138.197.233.88]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CC24111D908CD for <uri-review@ietf.org>; Thu, 23 Jul 2026 08:42:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alexgleason.me; s=mail; t=1784821328; bh=eB3+/TR9HHCdZNO6HiiAd2F93w7ND4ZHvWsMfCz8E3c=; h=Date:From:To:Cc:Subject:From; b=eukRXXTpDy9rUcr9j6UcmjzQSw5nrBEVP9+rUDD0MW6eFOONZR9HBr0eHHUcoZHAU foJ+I8DGRTWR9FOYVL/jTdFxTmhevbh73m1Hw0ezt+Eke2zfgYGsiRwjJzMzWa5jpv z9zyKwppP0OXXhF//rKoEJJ9k8BIOUvYYqex8Liwqn2IcnPAUoBgMszDiTKEnFsa4u u81bXKUP+sY8CAe9DL/t0lbqiDTzOSmkMhakIl4ZrasFscnl1hPpNYpnAHIBaVyNb4 95yN5hWFnSzdJZUwHvyqdCC0RBdpLJnl/FJMVpwvBWWnLlkpVuR0wTWeWM7A+gUIf9 z62pv8h+W5dkA==
Received: from authenticated-user (box.alexgleason.me [138.197.233.88]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by box.alexgleason.me (Postfix) with ESMTPSA id C9B673F086; Thu, 23 Jul 2026 15:42:08 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 23 Jul 2026 15:42:08 +0000
From: alex@alexgleason.me
To: iana@iana.org
Message-ID: <a6f233fa20651a0e7f883b159cd7d9a2@alexgleason.me>
X-Sender: alex@alexgleason.me
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
X-MailFrom: alex@alexgleason.me
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-uri-review.ietf.org-0
Message-ID-Hash: GA4LC2LRNHUVCSUSBESRI76PUNZZPS4Y
X-Message-ID-Hash: GA4LC2LRNHUVCSUSBESRI76PUNZZPS4Y
X-Mailman-Approved-At: Thu, 23 Jul 2026 10:28:59 -0700
CC: uri-review@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Uri-review] Provisional URI scheme registration request: "nostr"
List-Id: Proposed URI Schemes <uri-review.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/xiV_Kk249K48w-D5WuzGEzCXhdo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Owner: <mailto:uri-review-owner@ietf.org>
List-Post: <mailto:uri-review@ietf.org>
List-Subscribe: <mailto:uri-review-join@ietf.org>
List-Unsubscribe: <mailto:uri-review-leave@ietf.org>

Hi,

I'd like to request provisional registration of the 'nostr' URI scheme,
per RFC 7595. Template below.

Scheme name: nostr

Status: Provisional

Applications/protocols that use this scheme name: This scheme name is
used by Nostr [1], an open protocol for decentralized social networking
based on cryptographic keypairs and relays, to reference public keys,
events and profiles for linking and sharing between applications. The
scheme is specified in NIP-21 [2], with the identifier formats specified
in NIP-19 [3].

Contact: Alex Gleason (alex@alexgleason.me)

Change controller: Alex Gleason (alex@alexgleason.me)

References:
    [1] https://github.com/nostr-protocol/nostr
    [2] https://github.com/nostr-protocol/nips/blob/master/21.md
    [3] https://github.com/nostr-protocol/nips/blob/master/19.md

Examples:
    nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9
    nostr:note1fntxtkcy9pjwucqwa9mddn7v03wwwsu9j330jj350nvhpky2tuaspk6nqc
    
nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpp4mhxue69uhhytnc9e3k7mgpz4mhxue69uhkg6nzv9ejuumpv34kytnrdaksjlyr9p
    
nostr:nevent1qqstna2yrezu5wghjvswqqculvvwxsrcvu7uc0f78gan4xqhvz49d9spr3mhxue69uhkummnw3ez6un9d3shjtn4de6x2argwghx6egpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5nxnepm

Thanks,
Alex Gleason

v2.46.0 | Report a Bug | By Email | System Status