[Feature] Create microDAO

[HabacucMX]

This feature enables the creation of a minimum viable DAO by integrating:

1. Multichain Multisig (same address on multiple chain)
2. ENS name linked to the Multichain Multisig
3. EAS to create

• Badges for microDAOs achievements
• Record microDAO proposals
• Table events
• Register recurring microDAO activities

4. ERC20 to tokenize the microDAO and distribute ownership to stakeholders

We should consider 3 contracts, a microDAOfactory, microDAOmanager and a microDAObadges

microDAOfactory must:

1. Allow any address to initiate the creation of a microDAO.
2. Gather the required inputs to deploy a multichain multisig (member addresses, required signers for consensus threshold).
3. Gather the input to complete the ENS domain purchase and configuration, setting it as the primary name for the microDAO’s multisig address.
4. Enable the required structures for deploying an ERC20 to tokenize the microDAO and distribute it to stakeholders. This is not executed during the microDAO creation. It becomes available once members earn the required badges via the DAObadges contract.
5. Set up EAS attestations schemas for the listed interactions.
6. Include future feature extensions.

microDAOmanager must:

1. Enable microDAO members to execute basic multisig transactions, such as sending funds to a one or multiple addresses, creating microDAO proposals, logging attestable events or registering recurrent microDAO activities.
2. Manage ENS features and updates
3. Trigger and gather the required inputs to deploy the ERC20 contract to tokenize the DAO (stakeholders addresses, shares, lock times, etc.)
4. Enable microDAO members to support advanced multisig transactions, such as lending and borrowing on DeFi protocols, interacting with other DeFi protocols or onchain dApps through wallet connect
5. Add or remove microDAO members and update the consensus threshold

microDAObadges must:

1. Grant badges for achievements

• First achievement: creating a microDAO. It must grant a badge linked to an EAS schema for all DAOmembers, it should grant the attestation automatically to any new microDAO member
• Second achievement: publishing a Mirror article. It must grant a badge linked to an EAS schema to all DAO members after submission and verification of the article url.

Allow the addition of new achievements and the modification of badge requirements.

[HabacucMX]

Tentative flowchart

flowchart TD
 subgraph subGraph0["Gnosis Safe"]
        SAFEFAC["Gnosis Safe Proxy Factory"]
        SAFEMASTER["Safe Master Copy"]
  end
 subgraph ENS["ENS"]
        ENSREGISTRAR["ENS Registrar"]
        ENSREG["ENS Registry"]
        RESOLVER["Resolver"]
  end
 subgraph MicroDAO["MicroDAO"]
        FACTORY["MicroDAOFactory"]
        MANAGER["MicroDAOManager"]
        BADGES["MicroDAOBadges"]
        SAFEPROXY["Gnosis Safe (Multisig)"]
  end
 subgraph EAS["EAS"]
        SCHEMA_CREATE["Schema: CreateDAO Badge"]
        SCHEMA_MIRROR["Schema: Mirror Article Badge"]
        SCHEMA_PROPOSAL["Schema: Proposal"]
        SCHEMA_EVENT["Schema: Event"]
        SCHEMA_RECUR["Schema: Recurring Activity"]
  end
    FACTORY -- createProxy --> SAFEFAC
    SAFEFAC -- deploys proxy --> SAFEPROXY
    FACTORY -- register ENS name --> ENSREGISTRAR
    FACTORY -- setSubnodeRecord --> ENSREG
    FACTORY -- setAddr --> RESOLVER
    FACTORY -- deploys Manager --> MANAGER
    FACTORY -- grantBadgeOnCreate --> BADGES
    MANAGER -- execTransaction --> SAFEPROXY
    SAFEPROXY -- calls Resolver --> RESOLVER
    SAFEPROXY -- calls Registry --> ENSREG
    MANAGER -- attest Proposal --> SCHEMA_PROPOSAL
    MANAGER -- attest Event --> SCHEMA_EVENT
    MANAGER -- attest Recurring Activity --> SCHEMA_RECUR
    MANAGER -- trigger Mirror Badge --> BADGES
    BADGES -- attest CreateDAO --> SCHEMA_CREATE
    BADGES -- attest Mirror Article --> SCHEMA_MIRROR

    style SAFEFAC fill:#00C853, stroke:#00C853
    style SAFEMASTER stroke:#00C853
    style ENSREGISTRAR fill:#2962FF, stroke:#2962FF
    style ENSREG fill:#2962FF, stroke:#2962FF
    style RESOLVER fill:#2962FF, stroke:#2962FF
    style FACTORY fill:#FF6D00, stroke:#FF6D00
    style MANAGER fill:#FF6D00, stroke:#FF6D00
    style BADGES fill:#FF6D00, stroke:#FF6D00
    style SAFEPROXY fill:#00C853, stroke:#00C853
    style SCHEMA_CREATE fill:#AA00FF, stroke:#AA00FF
    style SCHEMA_MIRROR fill:#AA00FF, stroke:#AA00FF
    style SCHEMA_PROPOSAL fill:#AA00FF, stroke:#AA00FF
    style SCHEMA_EVENT fill:#AA00FF, stroke:#AA00FF
    style SCHEMA_RECUR fill:#AA00FF, stroke:#AA00FF
    style subGraph0 stroke:#00C853
    style EAS stroke:#AA00FF
    style ENS stroke:#2962FF
    linkStyle 1 stroke:#00C853,fill:none

[HabacucMX]

Tentative sequence

sequenceDiagram
  participant User
  participant Factory as MicroDAOFactory
  participant SafeFac as Gnosis Safe Proxy Factory
  participant SafeProxy as Gnosis Safe (Multisig)
  participant ENSReg as ENS Registrar & Registry
  participant Resolver
  participant Manager as MicroDAOManager
  participant Badges as MicroDAOBadges
  participant EAS as EAS Contract
  participant SchemaCreate as Schema: CreateDAO
  participant SchemaMirror as Schema: Mirror Article
  participant SchemaProposal as Schema: Proposal
  participant SchemaEvent as Schema: Event
  participant SchemaRecurring as Schema: Recurring Activity

  %% MicroDAO creation process
  User ->> Factory: createMicroDAO(members, threshold, ensName)
  Factory ->> SafeFac: createProxy()
  SafeFac -->> Factory: returns SafeProxy
  Factory ->> ENSReg: register ENS name
  Factory ->> Resolver: setAddr(namehash, SafeProxy)
  Factory ->> Manager: deploy MicroDAOManager
  Factory ->> Badges: grantBadgeOnCreate(members)
  Badges ->> SchemaCreate: attest()
  SchemaCreate ->> EAS: store attestation

  %% Member interacts with Manager
  User ->> Manager: execTransaction(...)
  Manager ->> SafeProxy: forward transaction (e.g. fund transfer)
  SafeProxy ->> ENSReg: call ENS Registry
  SafeProxy ->> Resolver: call Resolver

  %% Proposal and activity flow
  User ->> Manager: createProposal(data)
  Manager ->> SchemaProposal: attest()
  SchemaProposal ->> EAS: store attestation

  User ->> Manager: createEvent(data)
  Manager ->> SchemaEvent: attest()
  SchemaEvent ->> EAS: store attestation

  User ->> Manager: registerRecurringActivity(data)
  Manager ->> SchemaRecurring: attest()
  SchemaRecurring ->> EAS: store attestation

  %% Mirror article badge flow
  User ->> Manager: triggerMirrorArticleBadge(url)
  Manager ->> Badges: grantBadgeOnMirrorArticle(members, url)
  Badges ->> SchemaMirror: attest()
  SchemaMirror ->> EAS: store attestation

[shyam-patel-kira]

• create a specific address for attestations for attesting events within the DAO