[Delete the gray parts when done.]
Objective: While technical accuracy is crucial, the presentation of information is equally important as it directly affects how well our partners understand our goals. Therefore, we need to focus not only on technical details but also on communicating our ideas effectively.
The document will follow a clear structure. We'll begin with the Background and General sections, that provides a high-level overview of the current situation and the project. This section aims to give readers a comprehensive understanding of the system as a whole before delving into specific details.
Once readers have grasped the big picture, we'll move to the In-Depth section. Here, we'll examine each component of the system in greater detail, breaking down their individual functions and requirements.
When you look at the structure of the template, we start at a higher level and gradually move to a lower level, adding more details at each stage. This approach ensures that readers first understand the overall context before exploring the technical specifics of each component.
https://github.com/ethereum/L2-interop/blob/main/specs/addresses/technical-specification-solidity-library-for-interoperable-addresses.md
https://defi-wonderland.notion.site/extensible-minting-tech-design
[Information about how the current system works now. Include what the system does, relevant links and the participants.]
[General description of how the new system will work with our changes and what we want to accomplish. This should be a high level overview of the entire project**.** Include diagrams that follow a high level overview of the project.]
[A list summarizing the high-level functionality and constrains of the system.]
[This is the place to go deep and explain in technical detail each of the parts/actors/actions of the project previously described in the General section. Include flow diagrams that explain interactions.]
[Detailed changes to the current smart contracts and new contracts to be added, including functions, variables, events, and interactions.]
[UI/UX specifications. The purpose of the UI, mockups, designs, components, user stories should all go here.]