From 89fb82455eb3429e042f48217f5c410a173e1138 Mon Sep 17 00:00:00 2001
From: ionextdebug <146920353+ionextdebug@users.noreply.github.com>
Date: Sun, 7 Jan 2024 09:18:53 -0300
Subject: [PATCH] Update 01.md

Add practical tutorial about how to partially implements the NIP-01, important for newcomers software developers.
---
 01.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/01.md b/01.md
index 80ee792..c73d5ea 100644
--- a/01.md
+++ b/01.md
@@ -175,3 +175,8 @@ This NIP defines no rules for how `NOTICE` messages should be sent or treated.
   * `["CLOSED", "sub1", "error: could not connect to the database"]`
   * `["CLOSED", "sub1", "error: shutting down idle subscription"]`
 - The standardized machine-readable prefixes for `OK` and `CLOSED` are: `duplicate`, `pow`, `blocked`, `rate-limited`, `invalid`, and `error` for when none of that fits.
+
+-----
+### HOW TO
+How to partially implement the NIP-01 using general purpose libraries, without NOSTR toolkits or SDKs:
+[How to implement NOSTR Protocol from scratch with Python (NIP-01)](https://fullstackengineer.hashnode.dev/how-to-implement-nostr-protocol-from-scratch-with-python-nip-01)