POC UI

[HabacucMX]

This is the tentative structure for the Dapp and the required UI instances to interact with the multisig and the microDAO contracts:

1. Home / Dashboard
   a. DAO ens
   b. Micro DAO Age (from creation on contract or until dissolution)
   c. MicroDAO attestations (diary, proposals, events) count
   d. Incubation progress
2. CreateDAO
   a. Step 1 Add microDAO owners and consensus threshold.
   b. Step 2 Add funds mainnet and deploy MicroDAO multisig on Superchain networks, extra for other chains. (we should define an estimate to cover the multisig deployment, the ENS process and the automatized attestations).
   c. Step 3 Choose and buy the ENS name for the microDAO (fees calculation and set as primary name occurs on backend).
   d. Step 4 MicroDAO created (Attest onchain and display attestations URLs for microDAO members).
3. Create MicroDAO events
   a. MicroDAO diary (recurrent operation events). [non critical]
   b. MicroDAO proposal (Admin and Executive decisions with consensus required). [Creation non critical, Approval critical]
   c. MicroDAO public event (Zenbit Badges Flow but permissionless for microDAO members). [Critical]
4. MicroDAO funds
   a. Send funds (single or multi address).
   b. Savings and credit (yield from lending, savings as collateral for borrowing).
   c. (Tentative) Flows with Superfluid and recurrent txs.
5. MicroDAO Settings
   a. Add or remove owners
   b. MicroDAO token (Stakeholders share assignment, deployment, token rewards for staking.
   c. Dissolve MicroDAO (Automatize after 1 year of inactivity?)

[HabacucMX]

1. Home Screen mockup

Default Home

Connected Home

[HabacucMX]

2. Create DAO Process

Initial screen

Step 1: Define MicroDAO name, address and members

Step 1b: Add microDAO safe on other networks

Step 2: Deploy multisafe (safe creator pays)

Step 3: Complete name setting

Step 3a: Wait for microDAO consensus

Step 3b: MicroDAO created

Step 4: Attest DAO members

(WIP)