nostr:nprofile1qqsdmup6e2z6mcpeue6z6kl08he49hcen5xnrc3tnpvw0mdgtjemh0spr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qy28wumn8ghj7un9d3shjtnwdaehgu3wvfnszyrhwden5te0dehhxarj9ekxzmnymrwrzm, this reminds me of your idea with the proofs that are locked to a recipient with an expiry so that they can be recovered if un-used. What would it take to make a minimal demo of this?
Login to reply
Replies (1)
I'd like to avoid a scenario where the mint is required to create a large number (millions?) of small (millisat) tokens or proofs
That's why I'm curious to learn about other approaches, which will likely need to be a bit more complex, to make this work with just a small number of proofs
I think we need the ability for the device to say something like "the router can have the tokens worth 32 sat, 8 sat, 1 sat, and 32 millisat", but where the router can delay the redemption until the device disconnects a few minutes/hours later
And we might need some sort of revocation login, where the device can "unlock" a different - likely overlapping - set of proofs while the router revokes its right to the first set