Hey Lightning Wallets, you have done an amazing job integrating zaps!! 👏 Wonderful job!

What about stepping up your nostr integration?

What about allowing the user to opt-in to this integration defining his npub?

With that npub the wallet could get from nostr relays information about the user's sent and received zaps, and fetching info of the sender or receiver.

That information could be used to enrich the corresponding Lightning transactions history with the name and pfp of the sender/receiver.

What do you think?

Does it make sense?

cc: #[0] , Alby, #[1] , Stacker News , #[2] , #[3] , #[4] , #[5] , Strike(army), #[6] , etc.

Reply to this note

Please Login to reply.

Discussion

Adding cc. #[9] from Zebedee.

Agree.

Looking forward to using my npub in Lightning Wallets:

#[2]

What about getting the zaps information from the nostr events to enrich the transactions history screen?

(Sender/receicer's name & pfp)

#[1]

Lightning Wallets won't be able to read private zaps... until the became nostr clients by themselves!

#[3]

sorry. missed this message. yes, those are great ideas. it also fits very well with what we do in SATurn. are you interested in joining some brainstorming on this?

Could try to see if I can add something useful...

Lightning Wallets integrating nostr profiles enriching their transaction history page:

#[1]

Bueno, espero que los siguientes en transformarse en clientes nostr sean algunas de las existentes Lightning Wallets, que además de publicar los zaps (como ya hacen ahora) sean capaces de recoger info de nostr para enriquecer la lista de transacciones con ella.

Estaría bien poder ver directamente en la lista de transacciones de la wallet a quién enviamos ese zap y de quién recibimos aquel otro, con el nombre y foto de perfil actualizado.

A ver si se animan a implementarlo...

#[1]

It could even improve a bit with the transaction list enriched with the zap information (sender/receiver name and pfp), imo:

😉

#[1]

What about showing zaps info in transactions list?

#[1]