Static Public Key Across Zites

Is your feature request related to a problem? Please describe.
What is the purpose of making a user's public key UNIQUE on every zite, but the auth_address (aka Bitcoin address) the SAME on every zite?

Describe the solution you'd like
A STATIC public key (across all zites) that is derived from the user's master key, same as their auth_address (aka Bitcoin address).

Describe alternatives you've considered

1. Could utilize the deprecated auth_key. (btw, why was this deprecated?)
2. Create a NEW plugin to derive a STATIC public key from the master key.

Additional context

So Why Is This A Problem?

Dynamic zites work very well today, by allowing users to write data to their own folder/namespace within the zite's sqlite data storage.

But what if you're NOT using Zeronet's sqlite data storage. It makes using "legacy" client/server features within zites cumbersome; since you have to rely on "legacy" authorization techniques for the user. Rather, a Zeronet-enhanced APP SERVER "should" be able to retrieve a user's public key from a registry (based on their cert id) and then send a challenge that can ONLY be solved by the private key holder. This would be AUTOMATIC, upon arriving at a ANY zite, making user authorization BUILT-IN for ALL developers.

eg. It should appeal to developers wanting to bridge an existing Clearnet application over to Zeronet. In which case, it would be ideal to utilize current backend systems while making the migration to a fully decentralized solution.

Không có tệp, bài kiểm thử hoặc điểm vào nào được nêu tên. Hãy bắt đầu bằng cách theo dõi cách ZeroNet hiện đang xử lý khóa công khai và auth_address, sau đó xem xét auth_key đã không còn được dùng được đề cập trong issue. Kết quả hoàn tất cần bao gồm một phương pháp được xác định để dẫn xuất khóa tĩnh từ khóa chính và làm rõ cách nó hỗ trợ việc ủy quyền giữa các zites.