Social media or monetizing otherwise free user-generated content isn’t the use case that will encourage #nostr adoption. It’s a start, but certainly not the end game. Nostr events have no value of themselves. Once someone figures out how to use nostr to underlay a completely novel use case, then things will take off. I have a hunch, it will be based on what is specified in NIP-01 along with a few conventions, no more.
This is cool - I can now directly send funds between different instances of a #nostr #safebox. If I know the npub of the receiving safebox, I can just do the command:
$> safebox send 21 @npub1l3e…e9w5c
The receiving safebox does a check
$> safebox check ecash
And voila, the funds (21 sats) appear in the receiving safebox.
I am currently using NIP-04, but switching to NIP-17 as I now have an implementation working for #safebox (It was a late night last night)
I will also be doing some further abstraction so that the user need only care about sending and receiving funds, they won't have to care if it's lightning, ecash, or zaps. I am also thinking about adding in a currency rate option, so a user can specify that they want to send a fund equivalent for a local unit of account (USD, CAD, EUR, etc.). Easy to do as I already support that in my lightning payment service; I can just bring the code over to the wallet.
I am also thinking about adding in a key signing capability. Right now the device stores the nsec, but I'd like the option to push that out to a hardware signing device. I am hoping to just plug in something that someone else has developed, but that is still a while away.
I'll be taking a close look at the badge NIPs, because it should be pretty each to add a badge issuance/verification capability. Every wallet should be able to do this - not just special issuer/verifiers as the current commericalized models imply.
More to come!
#nost r #safebox
All I really care about is signed events that I can parse and verify with a npub. Plus a few conventions around kinds. If signed events can be serialized for more efficient transmission, great, but that’s icing on the cake.
It’s actually amazing what I am accomplishing with ecash on nostr (or luggage on wheels)
Don’t let anyone tell you anything differently but “Mandatory Backdoor” and “Own Goal” are one and the same.
Just returned from a ramen restaurant where the walls were adorned with framed pictures of AI-generated cats drinking beer and eating ramen.
So glad that AI-generated art has finally found its true home.
Ecash on nostr is like having wheels on your luggage.
“We’ve leased our central nervous systems to various corporations.”
Marshall McLuhan, 1964
GM 
Agree. Let nostr be nostr. For me it's about data that I want to trust and store on my own sovereign terms. It's just a subset of my personal data: payment data, proof data and other things I need to function digitally if I get rug-pulled by various providers. It's like a digital go-bag
Nice blog. You’re right, the system is broken and the ones who want to ‘fix it’ just want to take away freedoms that are not in their favour.
Not sure how to fix it, but I know it’s partly about keeping the power balance tilted in favour of the individual, especially for all of those digital services.
Thanks!
Thx. Still pretty raw. I try to compile the binaries ASAP. You can find the link at: https://github.com/trbouma/safebox
I’m excited to be going to labitconf.com in Buenos Aires to talk about Nostr and the importance of social media being build on a permissionless open protocol. There’s going to be a Nostr day after as a side event to help people exposed to Nostr to dive deeper.
This is connected to bringing the NostrBooth to three November conferences in Latin America. The project, organized by nostr:npub1hz5alqscpp8yjrvgsdp2n4ygkl8slvstrgvmjca7e45w6644ew7sewtysa, is being crowdfunded by the community and we need your help to make it happen.
I’d be keen to replicate the #nostrbooth for some local events.
Good progress with #nostr #safebox this weekend. I got the sending part of NIP-17 dms working; you can dm any npub or NIP-05.
The command line looks like this:
$> safebox dm trbouma@openbalance.app "hello from a safebox"
Next part is converting all of my ecash dms to NIP-17 (currently using NIP-04). That'll take a few days.
I also implemented an interesting feature which enables me to share a private record from a wallet. If I do the commend to create a private record:
$> safebox put private_record "This is content for a private record"
I can retrieve it by:
$> safebox get private record
Retrieving private_record "This is content for a private record"
I can also share the contents via a dm to a npub or nip05 address
$> safebox share private_record trbouma@openbalance.app
Not exactly sure what the use case will be, but I think it's pretty cool that you can share private details to someone you trust, in case of an emergency. The big use case I see, is storing and sharing medical information - I am exploring this possibility.
Anyway, I am having great fun building what I believe is a true sovereign wallet that can integrate payments, proofs, and private information - all under your sovereign control!
Snapped another nice pic just before the Endtimes arrive. 
Chromium has a multi-billion dollar company as an enterprise user. Most #nostr users are still in their underwear and fljp-flops.
The supposed seat of digital power used to be being part of a browser root store program.
Now it's about gaining access to the secure element in the mobile OS.
Let's upend that by only requiring a self-generated nsec that you alone decide whether it should power or not.
Fruit flies > AI
“Fortunately for the worriers, AI today is incredibly inefficient. It requires power inputs which would service a small city and such vast quantities of data to train itself that the entire internet is not enough. By contrast, flies, which are powered by rotting fruit, can do things no AI can yet manage. If their ability to navigate and avoid objects could be replicated, for example, then designing self-driving vehicles would be a doddle.” -Economist
Tonight’s dinner: beef ribs, mac’n’cheese, corn and salad. 
It’s the big red lever on the door. Let me know how it goes.
ICYMI
?cid=6c09b952xph1sec2vs66k3n4gju3kgy4ruokpxa6xfnh6nr6&ep=v1_internal_gif_by_id&rid=giphy.gif&ct=g
After a few weeks of hard work, i am really pleased how things for #nostr #safebox are shaping up. I've managed to hide a lot of the complexity of nostr, lightning and cashu behind some some simple subcommands for safebox. For example - the different ways to pay:
1. issue - to issue a cashu token to the command line
2. accept - accept a token
3. receive - accept a token and settle amount to home mint
4. deposit - deposit funds via a lightning invoice (plus text QR code!)
5. withdraw - withdraw funds via a lightning invoce
6. pay - pay to a lightning address
7. zap - zap to a nostr event; zap split if zap splits are present
8. send - send an amount as a cashu token to an npub or nip05 address
All this looks easy, but there was (and still) a lot a engineering in the background to make this all work. I've read and re-read many of the NIPS to make sure I am implementing properly.
I am also adding a bunch of other stuff - for example storing and retrieving private records. I see this turning into a full blown wallet and am looking store important things that you want to control and not lose like personal medical records.
In the end, THIS IS ALL TOTALLY EXPERIMENTAL, but I am progressing way beyond what I had originally envisioned and a completely new model for wallets that are independent of devices, apps, and platforms ('Here's looking at you, Google/Apple/Samsung/EU!').
And it all started with payments that now just work thanks to nostr, cashu, lightning and bitcoin (well, there is still more testing and debugging to do, but the main mechanisms work)
Anyway, just wanted to share my progress.
Cheers.
I had this hunch. I attended a web3 event last night. Total cringe. Explains my headache this morning. nostr:note1jgs4rs8krftdmae9t8zntnhvppyrf7na5tceg5kqvmlef9c9lvysj3pdx6
A patchwork of subnets with unified namespaces for events and actors. #nostr does this elegantly with event ids, npubs and relays.
