TODOs before Submitting as an EIP

[adrianmcli]

TODOs as of 2023-10-19:

1. Authorship Clarification: Discuss and decide who should be listed as authors based on their contributions.
2. Core Circuits Expansion: Provide more details on the core circuits within the Specification section.
3. Test Cases Addition:
   • Include tests for function inputs, both valid and invalid.
   • Test event emissions for correctness.
   • Test the ZK proof verification functionality.
4. Security Considerations Expansion:
   • Detail potential risks and mitigation strategies concerning ZK proofs implementation.
   • Address security implications of off-chain verification.
   • Discuss error handling and potential exploitation by malicious actors.
   • Address dependency security and potential reentrancy attacks.
5. Placeholder Text Removal: Replace or remove all placeholder text throughout the document.
6. Community Engagement: Engage with the community on the provided discussion link to gather feedback.
7. Final Compliance Review: Conduct a final review to ensure the document complies with EIP-1 guidelines.

Initial Steps (for reference)

According to the official README of the EIPs repo, we need to do the following:

• [x] Discuss the idea on Ethereum Magicians.
• [x] Read over EIP-1 for instructions on creating an EIP.
• [x] Create a draft with the necessary headings.
• [x] Fill out each section.
• [x] Get feedback, and iterate.

Let's also keep this in mind:

It is highly recommended that a single EIP contain a single key proposal or new idea. The more focused the EIP, the more successful it tends to be.

[adrianmcli]

I have created 4 more issues to detail things that need to be complete before we submit the PR for an EIP number:

• 4 Motivation and Rationale needs to be fleshed out

• 10 Solidity Interface for submitProofOfSolvency Function

• 11 Core Circuits and Data Structures

• 12 Security Considerations