Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
6e61c6a5a8 |
@@ -1,5 +1,14 @@
|
||||
---
|
||||
slug: nostr-quantum-preparation
|
||||
title: Nostr Quantum Preparation README.md
|
||||
summary: This project is an interim solution to the problem for those who are concerned about keeping their identities secure through the transition, and also to give developers breathing room.
|
||||
image: https://blossom.laantungir.net/5b96cc0c5ba4a8081e5ee8e5a2e718f28c0cbc77f218c55d956b9be57c120ef1.jpg
|
||||
tags: [nostr, quantum, readme.md]
|
||||
---
|
||||
|
||||
# Nostr Quantum Preparation
|
||||
|
||||
/tmp/sb_test_save.jpg
|
||||
|
||||
## TLDR
|
||||
|
||||
@@ -23,7 +32,7 @@ I have currently used the following post quantum algorithms:
|
||||
|
||||
This app will generate public-private keypairs for each of these, publish on nostr your public key for each, and sign it with your current Nostr identity via your favorite signer (the nsec never leaves the signer).
|
||||
|
||||
You are making a statement to the world: "Here are post quantum pubkeys. If quantum computers hit, you know that the person signing using these can only be me."
|
||||
You are making a statement to the world: "Here are post quantum pubkeys. If quantum computers hit, you know that the person using these can only be me."
|
||||
|
||||
This entire kind 1 event is then hashed and stamped into a block on Bitcoin using OpenTimestamps.
|
||||
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "nostr_quantum_preparation",
|
||||
"version": "0.1.5",
|
||||
"version": "0.1.6",
|
||||
"description": "A migration strategy for bringing post-quantum security to Nostr without breaking the social graph, without requiring consensus on a single post-quantum algorithm, and without forcing existing users to abandon their identities.",
|
||||
"main": "index.js",
|
||||
"scripts": {
|
||||
|
||||
@@ -606,7 +606,9 @@
|
||||
const trustModeNote = selection.canonicalTrustMode === 'pending-only'
|
||||
? ' ⚠ PENDING-ONLY — no Bitcoin attestation has been verified yet; this is not a trust decision.'
|
||||
: (selection.canonicalTrustMode === 'none' ? ' ⚠ no trustable anchor found.' : '');
|
||||
const statusClass = selection.canonicalTrustMode === 'pending-only' ? 'error' : 'success';
|
||||
// F-D4/L-2: a pending-only selection is informational, not an error —
|
||||
// it is not a trust decision, so do not render it in the error (red) style.
|
||||
const statusClass = selection.canonicalTrustMode === 'pending-only' ? 'info' : 'success';
|
||||
setStatus(queryStatus, statusClass, `Selected canonical proof carrier: ${selection.canonical.id.substring(0, 16)}... (${heightNote}). ${confirmedCount} confirmed, ${pendingCount} pending, ${allCandidates.length} total candidate(s).${trustModeNote}`);
|
||||
await verifyEvent(selection.canonical);
|
||||
} else {
|
||||
|
||||
+3
-3
@@ -1,5 +1,5 @@
|
||||
{
|
||||
"VERSION": "v0.1.5",
|
||||
"VERSION_NUMBER": "0.1.5",
|
||||
"BUILD_DATE": "2026-07-29T13:52:32.430Z"
|
||||
"VERSION": "v0.1.6",
|
||||
"VERSION_NUMBER": "0.1.6",
|
||||
"BUILD_DATE": "2026-07-30T10:46:55.076Z"
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user