Replying to Avatar JeffG

GM Nostr! šŸŒž

šŸŽ Announcing Keycast šŸ”‘

A remote signing platform for teams.

https://share.cleanshot.com/y4XbqKpT

Remote signing (NIP-46) has always had a lot of promise. Apps like Amber, nsec.app, and others have made it possible to manage your nostr keys in a way that is safer than browser extensions or pasting your nsec around the internet.

BUT, none of them catered to teams. Groups like nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l and nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk and many many companies out there are just sharing the main account nsec between different people and using it in different apps. A recipe for disaster.

Keycast aims to finally fix this. It allows you to:

- Manage teams of nostr users

- Manage multiple keys that you want to give others access to

- Create authorizations for those keys that grant specific permissions that can be changed, revoked, etc.

- Create your own custom permissions

- Run the signing infrastructure without any extra work

And do it all in a self-sovereign way. Keycast is meant to be run on your server, by you. I think it's tremendously important that this sort of tool doesn't exist as a hosted service (which would basically be a huge key honeypot over time).

The app is both a management web app AND a backend process that manages sub-processes that listen for remote signing requests, check permissions, and sign events.

There is a basic docker setup to start, but my goal is to have this easily deployable to StartOS, Umbrel, Podman, and others.

Code here: https://github.com/erskingardner/keycast

I tried to run it, but got some weird problems on the compilation side or something, I'm not sure. The UI loaded, but the logs showed some errors and then I couldn't create a team.

Also this was after a message was printed kindly asking me to rename "cargo.toml" to "Cargo.toml".

Reply to this note

Please Login to reply.

Discussion

Hmm. Middle of family stuff now but let me have a look a bit later. I might have just borked something while trying to get the docker stuff going last night.

I suspect nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc is working on a windows machine. since thats the only OS I know of that does not have case sensitive file names šŸ˜€

Also I cloned the repo and the files where missing the new line at the end of the files

Nope. New Mac. I’m weirded out by that file name too.

Very odd. File explorer and terminal were showing the uppercase spelling but my guess is that I had it wrong early, changed it, and for some reason git was still tracking it in the old case without changing it... šŸ¤·ā€ā™‚ļø

I'll push a fix (for a few things I found since announcing šŸ¤¦ā€ā™‚ļø) sometime soon.

For now, it's Christmas time. šŸŽ