SEC-04: Building it right... Mar 03 - Apr 11 2025

nostr:note1tzafqmqevv23mkj3fmgme8hywkzkzppanggsjg0u09z2ulxukz9qeyq9ar

sorted by created_at in this case is very misleading because it's the date of the last follow but we cannot know for sure who that follow was without a more complete history of that specific list, so unless your key is the last in the tags array (supposing it was appended) the created_at date is kind of meaningless, i.e if someone follows you since a year ago but just updated it's follow list to include someone else now, it would show up as the most recent follow list that you're in, but not the last one to add you..

relay hints go on `e` or `a` tags after the id, and as per the screenshot, they're not even beeing used here.

I'm seeing a bunch of notes with what looks to be a full nip-65 relay list appended to the tags of regular kind-1 notes.

is this a bug or a feature?

examples:

nostr:note1wv7s0r6tq2jgecfsqwx2zksmvpzkmp7hwn0gsgwf2u5yh0snsj8q2f34py

nostr:note14ecul75erfma6u32x6q8gmfpfwdyk4fahpw8y2nn4lgsnc4l9zys6lq3kq

nostr:note158pm5l74akhgekzzrw0hstkljumrgcppw7n2fay7ppz5r68vyk3qfhzmle

just realizing that I don't think I can do p2pk on cashu without having direct access to the private key, so this means I can't do it with nip7 extension alone. or am I missing something?

found it in the integration tests:

https://github.com/cashubtc/cashu-ts/blob/main/test/integration.test.ts#L221

anyone familiar with cashu-ts and how it handles P2PK? can't really find info on the subject.. nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226

the heavy lifting is done by cashu-ts: https://github.com/cashubtc/cashu-ts/ if you're doing web then you'll probably want to look there.

my code is at https://github.com/eskema/alphaama/blob/0c9e930ba2872e89e8cd6fc57937e7200cc92a29/w/w.js but it's still in a rough state... it's wip that will change for sure in the coming days.

the nip is pretty straithforward: https://github.com/nostr-protocol/nips/blob/master/60.md

just pushed an update to the repo and https://wip.alphaama.com to reflect my local copy but this is still very much work in progress and the workflow isn't polished nor documented and might still change 😅, waiting to have nip-61 working to make "final" adjustments to the whole thing..

my nip-60 integration in alphaama is coming along nicely. I can already create and import wallets, mint and melt proofs. still work in progress but I'm amazed all of this is already possible with no friction at all. now going to work on adding P2PK with nip-61, if anyone wants to send some nutzap my way for science it would be helpful for testing. happy new year 🤘

what does very important note mean? who decides why it is important? why do we need to rely on relays to enforce this thing?

because we're still at the point where the browser is the everything app that works seamlessly across systems and users already understand how it functions and how websites generally work inside of it, supposedly on a layer with restricted access to the whole device. Apps require more trust or heavy usage for a user to warrant installing and giving additional exposure to the wider OS (at least I perceive it this way). At the same time, coding for the browser is basically unrestricted of gatekeepers and compilers and specific hardware, device shape or even coding skills to have something up and running everywhere.

tldr: less friction

lol

<3

I do

yes

it's been months... nostr:note15v8k63vy8vn4nsveg20xuapqrzydq4vvdn92yv5f499xf944jn9q2dghgw

do it

you can do that with alphaama