Yesterday was demo day in #sec03 and I demoed a new relay I created called MIMO. The ...

Why Nostr? What is Njump?

npub1gz…ea5ds

2024-10-26 16:39:28

Yesterday was demo day in #sec03 and I demoed a new relay I created called MIMO. The primary goal is to add a remote signing functionality to a personal relay, allowing you to set a root key in the relay that will be used to sign incoming events from subkeys or hosted keys (I'm still deciding on the final terminology, as 'subkeys' is a simpler concept but not entirely accurate, while 'hosted keys' is more accurate but slightly less intuitive). These subkeys/hosted keys can be created and managed in the relay dashboard, which uses NIP98 to protect the HTTP endpoints. When you create a new subkey, the relay will automatically sync the kind 0, 3, and 10002 events from the root key, simplifying the user experience and making the subkeys ready to use immediately. The process is straightforward: create a new subkey, import it into your preferred client or signer, and you're ready to go. You can then use the created subkey to publish content in the client of your choice, without requiring the client to be compatible with any new features. When you write a note signed with the created subkey, it will be resigned and broadcasted with the root key.
One of the key benefits of this relay is that you can create any number of subkeys, enabling use cases such as subkey-per-device. Additionally, subkeys have scoped permissions to publish, allowing you to define the specific kinds of events that a subkey can publish. Another feature of the relay is that it also function as a Web of Trust (WoT) relay, computing your WoT to allow your network to publish in the relay. In this case, events are stored as-is, without being resigned with the root key, whereas events from subkeys are resigned. The relay also actively stores the kinds 0, 3, and 10002 of your WoT, similar to the use case of purplepag.es relay. This enables correct delivery of notes to the inbox of the user you are chatting with.

!! Note that the implementation is still incomplete, and there is ongoing work to make this a more useful and secure tool.

quoting
nevent1q…neje
What do these two notes have in common?... They were signed with my keys, but they were not published by me 👀
nevent1q…ktk4

nevent1q…grnv

Author Public Key

npub1gzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gs3ea5ds

Show more details

Published at

2024-10-26 16:39:28

Kind type

1 Short Text Note

Event JSON

{ "id": "7e97ee0254ffc54f7febfce75a186f35f0230edbbd9923b7dd6eff274e76c724", "pubkey": "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451", "created_at": 1729960768, "kind": 1, "tags": [ [ "t", "sec03" ], [ "e", "079e0832a061887a16dd662d75a4dde8c5ec3f5cc32144c1cc61a83f4bb3f2ac", "wss://relay.nostr.band/", "mention" ], [ "p", "40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451", "wss://nostrelites.org/", "mention" ], [ "client", "noStrudel", "31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546" ] ], "content": "Yesterday was demo day in #sec03 and I demoed a new relay I created called MIMO. The primary goal is to add a remote signing functionality to a personal relay, allowing you to set a root key in the relay that will be used to sign incoming events from subkeys or hosted keys (I'm still deciding on the final terminology, as 'subkeys' is a simpler concept but not entirely accurate, while 'hosted keys' is more accurate but slightly less intuitive). These subkeys/hosted keys can be created and managed in the relay dashboard, which uses NIP98 to protect the HTTP endpoints. When you create a new subkey, the relay will automatically sync the kind 0, 3, and 10002 events from the root key, simplifying the user experience and making the subkeys ready to use immediately. The process is straightforward: create a new subkey, import it into your preferred client or signer, and you're ready to go. You can then use the created subkey to publish content in the client of your choice, without requiring the client to be compatible with any new features. When you write a note signed with the created subkey, it will be resigned and broadcasted with the root key.\nOne of the key benefits of this relay is that you can create any number of subkeys, enabling use cases such as subkey-per-device. Additionally, subkeys have scoped permissions to publish, allowing you to define the specific kinds of events that a subkey can publish. Another feature of the relay is that it also function as a Web of Trust (WoT) relay, computing your WoT to allow your network to publish in the relay. In this case, events are stored as-is, without being resigned with the root key, whereas events from subkeys are resigned. The relay also actively stores the kinds 0, 3, and 10002 of your WoT, similar to the use case of purplepag.es relay. This enables correct delivery of notes to the inbox of the user you are chatting with.\n\n!! Note that the implementation is still incomplete, and there is ongoing work to make this a more useful and secure tool.\n\nnostr:nevent1qvzqqqqqqypzqs9eep0ll6hurjkl3sc2fewgses07mjfwxsdcu3at2m8fd0xrdz3qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qyt8wumn8ghj7mn0wd68yetvd96x2uewdaexwtcqyqreuzpj5pscs7skm4nz6adymh5vtmpltnpjz3xpe3s6s06tk0e2c0nneje", "sig": "ad81c63433537c6369c240c244e6b3248bed3a31fa9a36fbdf72dad0aa39cfab3a6cca82b2ebd95466d4ff3ec2e633601f3b8353d821ea3c18d6a32f4cf4b1b5" }