#ZapVert is cooking!
Applied knowledge is power!
There is the init with new secret method,
* that could get a param for the budget,
* then the apps could request only for a specific amount of funds.
Not more, not less. Then generated key would be non-useable. This way, the user do not have to keep in mind how much he shall allow for that specific app.
This way, we can generate on the fly throwable keypairs for apps.
Batch invoice authorization
Send a wallet a batch of invoices, and pay them in one click.
It would make a convenient way to make p2p payments to multiple people.
This can be solved at the moment in 2 ways:
1️⃣ Solution: Send a service the total money, and let the service handle the rest
🚫 Problem: It creates unnecessary payments (⚠️ fees!), and adds a middle man, not convenient to self-host.
2️⃣ Solution: Let a service pay all of them through nwc.
🚫 Problem: If you want to be safe, you have to set a budget. It is inconvenient. But it is easily self-hostable without server.
💡This could be solved by extending the nwc spec, so that we can create on the fly authorization strings and prompt the user to accept, that will be only useable for the current purpose, therefore keeps wallet safe, but improves comfortability.
Cc: nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm what do you think?
Batch invoice authorization
Send a wallet a batch of invoices, and pay them in one click.
It would make a convenient way to make p2p payments to multiple people.
This can be solved at the moment in 2 ways:
1️⃣ Solution: Send a service the total money, and let the service handle the rest
🚫 Problem: It creates unnecessary payments (⚠️ fees!), and adds a middle man, not convenient to self-host.
2️⃣ Solution: Let a service pay all of them through nwc.
🚫 Problem: If you want to be safe, you have to set a budget. It is inconvenient. But it is easily self-hostable without server.
💡This could be solved by extending the nwc spec, so that we can create on the fly authorization strings and prompt the user to accept, that will be only useable for the current purpose, therefore keeps wallet safe, but improves comfortability.
Cc: nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
on the second flight I finished writing the implementation (and modifications to NIP-46) to make the following possible:
1. Alice goes to App A (e.g. Coracle) -- she clicks "create account" and gets a NIP-05 "alice@somesite.com". She uses Coracle as she normally would.
2. Alice goes to App B (e.g. Primal) -- she clicks "login" and types in "alice@somesite.com". A popup comes up and asks Alice if she wants to authorize this application to access her account. In an advanced setting She can scope down what the application can do (e.g. only create short notes but don't change the profile data)
At no point is there any mention of nsec, npub, keys, NIP-07, nsecbunker. Nothing. It just works.
cc nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240
I fuckin love this! 💜🔥🦙
nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac the nostr design page you made is awesome! 🔥
Link for others: https://nostrdesign.org/
Unfortunately I am lazy, and want to have a running prototype first for my new nostr project, but if I publish it tomorrow, I will go through that page fully again, and solve the low hanging fruits.
Thanks for the great work! It is and will be tremendous help!
Coming soon to nostr near you!
I am quite excited, if it works out, I can leverage it with my next nostr projects.
Soon some of you will see it already in action.
I fuckin love nostr, I fully agree with you nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft ! When you can build tools, and then you can leverage in your new tools your old tools, it is freaking amazing! 🔥
I will wrap it up for today, and deploy it tomorrow. Then a little AI hackathon continues tomorrow.
Have an amazing rest of the day! And don't forget to say nice words and appreciate your loved ones! 💜🦙
🧐 Life hack: 🧐
Create a marketing tool, and promote your tool with your own tool. 😂
#zapvertising
At least it is #zapclusive
NDK 👀
✅️ Brainstorming for hackathon
✅️ Lunch cooked for a few days
✅️ Coffee ☕️
✅️ Idea for today to develop
🔄 Let's get hacking 👨💻
Pay attention to conflict of interest.
It might highlight the real reason for the things that are happening.
I would assume the same. Also big exchanges have big liquidity, p2p markets do not have that big liquidity.
Therefore the only way to substantially increase liquidity is to buy on exchanges and sell on p2p market. What do I miss?
Thanks! This part is clear.
I am rather curious, that the btc sold on p2p market was bought previously on an exchange so that it can be sold p2p. Or how frequent is it for btc sellers on p2p platforms to use exchanges to buy btc to sell on p2p platforms.
Good morning! ☕️🦙 Have a great day nostr:npub1w4j2y74wx24sckf7ymgnf3r4gp0yqd8huw8kzfyt2lj8lhmh7ujs75j067 !
Would you use a card company that gives you one-use credit cards for a specific amount paid by sats?
Benefits:
🟢 Pay via credit card with your sats
🟢 Preserving privacy when using credit card payment
🟢 No real credit card or account needed
How company makes money?
🟢 You pay x% above market prices
🟢 They make money from the conversion
#asknostr #bitcoin #lightning