[Design]: Withdrawal Flow Clarity LLD

[AshtonStephens]

Design - Withdrawal Flow Clarity LLD

Ownership breakdown: #47

• Primary: Hank (@hstove)
• Secondary: Jesus (@setzeus)
• reviewer: Joey (@xoloki)

This ticket tracks creating the low level design document for the withdrawal flow clarity. For a low level design to be "complete" it must have the approval of the majority of the sBTC team and meet the criteria of the checklist below.

The withdrawal contract LLD is included in the Clarity LLD Google doc.

Acceptance Criteria Checklist

• There's a written low level design doc with the following
  • Clear descriptions of all component interactions including serialization format
  • Diagram/s on how the component will work
  • Clear descriptions of the programming languages and infrastructure that will be used
  • Justifications for the design decisions
  • A rough task breakdown of the component's implementation plan referencing inter-dependencies
  • A general list of the of tests required for the component
• Low level design has been reviewed and approved with the secondary.
• Low level design has been reviewed and approved with the team.
• The task breakdown is refined with GitHub issues for each task

[hstove]

I should have commented this previously, but the withdrawal contract definitions are included in the Clarity LLD doc:

https://docs.google.com/document/d/1Bwi1jM_7p9OqNGT41eWCuoKnfoOrNHycqxby3XSonCA/edit#heading=h.z1svj1g6pe7v