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
https://geyser.fund/project/nostrsafebox/
Tim Bouma
npub1q6…nx7d5
2024-10-07 20:05:34
Author Public Key
npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5Published at
2024-10-07 20:05:34Event JSON
{
"id": "a8b3e47a1c07a31921b71bd7fc1747b6ddb9b7e9da3d76884602bcb361998ece",
"pubkey": "06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c",
"created_at": 1728331534,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"safebox"
],
[
"t",
"safebox"
],
[
"t",
"nost"
],
[
"t",
"safebox"
]
],
"content": "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:\n\n$\u003e safebox send 21 @npub1l3e…e9w5c\n\nThe receiving safebox does a check\n\n$\u003e safebox check ecash\n\nAnd voila, the funds (21 sats) appear in the receiving safebox.\n\nI 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)\n\nI 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.\n\nI 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.\n\nI'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.\n\nMore to come!\n\n#nost r #safebox \n\nhttps://geyser.fund/project/nostrsafebox/",
"sig": "93aaf3de85a4eeeea61c06eb08c61022abc0b38877d444fd7332067027fc6f60b0ed856337c5b544d7cb4ce5ac5ba8259274161938f847df8a1d075f3bf76875"
}