armstrys on Nostr: Amazing. People learning quickly the similarities between locked ecash tokens and ...
Amazing. People learning quickly the similarities between locked ecash tokens and nostr events. Both are just crytographically signed chunks of data that can be transmitted or stored anywhere. A token isn’t locked to a given wallet the same way a nostr event isn’t bound to a certain relay/client. The ecash mint just needs to be able to validate the token and spender at the time of spend the same way a nostr client validates an nevent signature and its author. I don’t know how PABLOF7z (npub1l2v…ajft) made this all work, but ecash over nostr was inevitable.
👉 Create a new npub AND DOING NOTHING ELSE, no WoS, no nostr-wallet-connect pairing,... NOTHING
☑️ receive zaps ☑️ send zaps ☑️ and most importantly ACCESS MY WALLET FROM ANY CLIENT ON ANY DEVICE
these zaps are verifiable, way faster -- they are immediate (since the sending of the ecash is the zap, instead of waiting for a LN node to, maybe, publish a zap receipt)
Just like our contact lists follows us around, just like our profile data and our shitposts pops up in any nostr application, now so does our sats.
{
"id":"749fddd52f19ca263f0ac388c3f0d4bc46948bb103c022d0d44aadbcfded4af9",
"pubkey":"c80b5248fbe8f392bc3ba45091fb4e6e2b5872387601bf90f53992366b30d720",
"created_at":1720877812,
"kind":1,
"tags": [
[
"q",
"00899f66d24014876863a328cc46fada54fac570bae70db6da642c6569bf41a8"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content":"Amazing. People learning quickly the similarities between locked ecash tokens and nostr events. Both are just crytographically signed chunks of data that can be transmitted or stored anywhere. A token isn’t locked to a given wallet the same way a nostr event isn’t bound to a certain relay/client. The ecash mint just needs to be able to validate the token and spender at the time of spend the same way a nostr client validates an nevent signature and its author. I don’t know how nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft made this all work, but ecash over nostr was inevitable. \nnostr:note1qzye7ekjgq2gw6rr5v5vc3h6mf2043tshtnsmdk6vskx26dlgx5qskqz34",
"sig":"c0a2b43fabf5a41aa48989a6ba694a47ecd29239ca55f2e1c37798a75ca09fec5d1a36b0535819037bd43bc0328ea8899a9463463a31526a99574bf1a7a6fcda"
}
