Nostr Web Client

Yep, equivalent. The simplest form of an Attestation is v simple too. All other events in the NIP are optional, as are most of the tags in the base kind.

Would be cool to have you using it also! You would simply use your verification event (30301) as the Subject Event.

btc_remnant 5mo ago 💬 2

Hey Nathan,

Is this NIP more or less stable now? Should we expect to have changes to it yet?

Reply to this note

Please Login to reply.

Discussion

btc_remnant 5mo ago 💬 1

Another question. In the event 31871, what's the "d" tag for?

Nathan Day 5mo ago 💬 1

Needs to be addressable and replaceable to support revocations.

I did have revocations as a separate event to begin with, but was steered this way to keep it simpler and have a single event representing the current state.

btc_remnant 5mo ago

Ah! Of course! What was I thinking? Thanks!

Nathan Day 5mo ago 💬 3

Pretty stable I think, especially the basics. Tweaks expected as clients implement and we learn what we got wrong.

btc_remnant 5mo ago

It would be something like this:

Nathan Day 5mo ago 💬 2

Nice.

Zapstore 5mo ago

Love seeing this!

nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qqsvfa085adgecmg84ffelcxx6zrn3ffu5jrc6cjtwng0zge3ptv43c5xzlap was great listening to you on PCR.

Eager to implement on Zapstore

btc_remnant 4mo ago

Hey Nathan!

Do we have an "oficial" nip for this Attestations spec?

Nathan Day 4mo ago

Not in the merged sense.

Community NIPs are the repo now.

Maybe it gets merged one day, but I think the protocol can be more emergent now.