exportspacensec

[spacesops]

Thinking about the broader spaces protocol operator ecosystem, a future entity that wants to provide a platform to service space owners would want the ability to require that a top-level space it indeed owned by the person claiming to own it.

This can be easily accomplished by providing a simple nostr event and asking the owner to sign it with their key.

space-cli signevent

The signed event could then be returned to the platform operator and verified with.

space-cli verifyevent

While this works in a rudimentary way, if the platform operator and/or the space owner wants to keep the line of communication open for future announcements and/or questions and/or billing/payment issues without actually knowing who each other are, it is cumbersome to continue using the space-cli subcommands.

This new subcommand exportspacensec behaves similar to exportwallet in that it creates a file with the exported content. In this case it is the nostr nsec and hex encoded format of the private key for that derivative path of that space.

This allows for easy Nostr client account setup and allows for monitoring of messages and using direct messages between the space owner and the platform operator.