Vitor Pamplona
e4937befd6
Zap splits
2023-05-23 13:44:58 -04:00
Alejandro Gomez
0495931355
NIP-23: suggest kind 30024 for drafts
2023-05-23 10:45:00 -03:00
heipacker
1c916953c1
new: add new signer. Android, IOS, Extension
2023-05-20 08:23:52 -03:00
jiftechnify
ccbdfb95c1
allow underscores in an emoji shortcode
2023-05-17 12:38:16 -03:00
Asai Toshiya
835ec26141
Add emoji tag to list
2023-05-17 12:37:23 -03:00
jimbojw
d9caf9d7b4
fix: Updating links in NIP-15 to point to intended other NIPs.
2023-05-15 16:01:33 -03:00
Neil
4ea0e8e9f2
Add new signing extension to NIP-07
2023-05-15 15:43:09 -03:00
Jon Staab
1457399664
Merge pull request #484 from alexgleason/emojis
...
NIP-30: Custom Emoji
2023-05-15 09:23:39 -07:00
Jon Staab
00491aa9fa
Merge pull request #529 from jiftechnify/fix-57-wording
...
Minor Fixes of NIP-57
2023-05-14 06:03:32 -07:00
jiftechnify
89e3c01b14
fix description of nostr query param
2023-05-14 13:16:10 +09:00
jiftechnify
9076b8486d
fix inconsistent quoting of zap request / receipt
2023-05-14 12:04:47 +09:00
jiftechnify
64ac0710de
zap note -> zap receipt
2023-05-14 11:55:07 +09:00
earonesty
2619482200
More explicit
2023-05-13 13:30:42 -03:00
earonesty
4cbb672d1c
Fix docs from kind0 to kind33
...
https://github.com/nostr-protocol/nips/issues/376
2023-05-13 13:30:42 -03:00
Jon Staab
2c1ed74c49
Merge pull request #155 from VictorieeMan/patch-1
...
NIP-05: Fixed some typos
2023-05-12 05:11:00 -07:00
Jon Staab
e5302f84c7
Merge branch 'master' into patch-1
2023-05-12 05:10:45 -07:00
William Casarin
4208652dc7
nip47: add lud16 parameter to connection string
...
This adds an optional but recommended lud16 parameter to nostr wallet
connection strings. This enables seamless onboarding of new users,
allowing clients to automatically configure the receive address for
zaps.
2023-05-10 12:16:37 -03:00
Robert C. Martin
60aa6ae168
A few changes to some nips. ( #510 )
2023-05-09 12:17:15 -03:00
Asai Toshiya
d70aa87f07
Restore some lost changes
...
c7711aa3cec80d
2023-05-09 12:15:33 -03:00
fiatjaf
89a7aa0ea0
nip01: remove misleading markdown example.
2023-05-08 11:05:58 -03:00
Josua Schmid
ee018ef8a4
Rephrase Markdown special rule
2023-05-08 11:04:34 -03:00
Kieran
de1aec64d2
change references title
2023-05-08 12:25:51 +01:00
Kieran
f75d91551c
typo
2023-05-08 12:25:51 +01:00
Kieran
30620c8e54
Update readme
2023-05-08 12:25:49 +01:00
Kieran
2d31ddd38a
add note about payload hash
2023-05-08 12:22:53 +01:00
Kieran
29f26e72b5
NIP-98
2023-05-08 12:22:53 +01:00
ekzyis
1678c53dcd
Update old link to fiatjaf/nostr
2023-05-06 19:07:07 -03:00
Jon Staab
d5484a33bc
Clarify how NIP 45 works with multiple COUNT filters. ( #504 )
2023-05-06 15:35:21 -03:00
fiatjaf
b8aec7dad5
nip-31: dealing with custom unknown events.
2023-05-05 09:18:02 -03:00
fiatjaf
bc9d469c20
add nip-47 to index.
2023-05-05 08:50:50 -03:00
fiatjaf_
544095d23f
Merge pull request #406 from nostr-protocol/47-wallet-connect
2023-05-02 17:00:22 -03:00
Robert C. Martin
d7c189d70b
NIP11 example using curl. ( #490 )
2023-05-02 11:41:59 -03:00
mplorentz
7f75d0db33
Change NIP-21 URL->URI
...
I think the `nostr:...` scheme is not actually a Uniform Resource Locator, because it doesn't tell you where the data is located. For instance if I see the string `nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9` I understand that this identifies a Nostr keypair but I don't know where to find data for that keypair. The scheme does fall under the definition of a Uniform Resource Identifier, or maybe even the stricter class Uniform Resource Name. But nobody talks about URNs, so maybe best to just use the less-specific term "URI" here.
2023-05-01 15:16:30 -03:00
Alex Gleason
e91ce3409e
NIP-30: Custom Emoji
2023-04-29 13:16:58 -05:00
Jonathan Staab
346036208c
Add dim tag to NIP 94
2023-04-28 13:05:35 -03:00
Semisol
5a8c463641
NIP-47: Add error for payment failed
2023-04-27 17:24:20 +03:00
kiwiidb
de095e4758
NIP-47: Implement feedback
...
Co-authored-by: Semisol <hi@semisol.dev>
2023-04-27 17:21:15 +03:00
Asai Toshiya
badabd513e
Reword description of kind 1063
2023-04-25 10:07:24 -03:00
fiatjaf_
8168f546c3
Merge pull request #473 from arkin0x/patch-1
2023-04-24 17:02:11 -03:00
arkin0x
61475db6f4
forgot to update the initial nonce in the explanation
2023-04-24 14:43:15 -05:00
arkin0x
6fb9e54f7b
example was incorrect
...
the example event id had 21 leading zeroes, not 20
I provided new C code that has been tested to work (I couldn't get the original example code to work) and I provided some JavaScript code to test event ids as well.
I did not re-compute the event id for the example event; I simply changed the nonce to be 21. Since it is an example, it may not matter that the event id is not correct.
2023-04-24 14:34:02 -05:00
fiatjaf
5d0cbcbebf
reword NIP-94 to remove confusion.
2023-04-24 14:57:37 -03:00
Vivek Ganesan
bf8f8e2708
blurhash explanation
2023-04-24 08:27:57 -03:00
michaelhall923
c5f43a8f90
Update 01.md
...
Info on "e" and "p" tags is kind of hard to find so I added a link to it in the place that I intuitively looked for it.
2023-04-21 10:17:36 -03:00
jiftechnify
4b9847802a
fix: re-add NIP-15 to the list
2023-04-21 07:48:34 -03:00
Asai Toshiya
92536d8b56
Add NIP-94 and kind 1063 to README.md
2023-04-20 13:29:19 -03:00
frbittencourt
34af61df41
nip update to reach consensus with other nips
2023-04-20 08:06:14 -03:00
frbittencourt
bfd2a0fc38
fixed text description
2023-04-20 08:06:14 -03:00
Fernando Bittencourt
f766a850cd
Apply suggestions from code review
...
add sugestion of arthurfranca and nryo-o
Co-authored-by: arthurfranca <arthur.a.franca@gmail.com>
Co-authored-by: Ryo_o <127748188+nryo-o@users.noreply.github.com>
2023-04-20 08:06:14 -03:00
frbittencourt
bd32adfc2a
change to regular event
2023-04-20 08:06:14 -03:00
