Add Mina Signer developer documentation

[MartinMinkov]

Question for the reviewer:

Mina Signer has multiple responsibilities in the Mina ecosystem. It can generate keypairs and sign payments/delegations for Mina. It can additionally sign payments created by o1js, such as zkApp transactions, field payloads and nullifiers.

• Should one document contain all information related to Mina Signer?
• If so, which section should this information live in? It has info useful for zkApps and node operators
• If not, is having two separate pages for the same concept a worthwhile trade-off? Will maintenance be easier if we just had one page?

Resources Mina Signer is in the o1js repo https://github.com/o1-labs/o1js/blob/main/src/mina-signer/README.md

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 13, 2023 9:20pm

[MartinMinkov]

@barriebyron Could you give this a first-pass review, please? Also, wdyt about the question posed in the description?

[barriebyron]

@garwalsh can you familiarize yourself with the Mina Signer, and let's talk? Who is the target reader of this doc? What content does the zkApp dev and Node Operator need? who can advise on this content

@nicc and I talked, and we thought a first draft could place the content in the zkApps section with a link from the existing topic at https://docs.minaprotocol.com/node-operators/mina-signer