-
DAO Configuration. User goes through DAO configuration steps, specifying each founder and associated voting power, governance modules and other parameters. (see here for example)
-
BBLLC Configuration. If the user elects to instantiate the DAO as a BBLLC, formation documents are auto-generated based on:
a. The specified DAO configuration
b. Additional legal fields such as any initial members' legal names and mailing addresses
-
Entity Deployment and Formation.
a. The DAO's code is deployed to Ethereum
b. The BBLLC's Operating Agreement is cryptographically signed by the initial Members, hashed and recorded on Ethereum
c. The BBLLC's Articles of Organization are filed with the Secretary of State
d. All the above actions and associated fees are bundled into a single atomic transaction (including the state filing fee and payment to a local registered agent)
Different scenarios where legal or accounting actions are linked in with governance flows, such as proposals.
- Accept/reject customer projects
- Accept/reject contractor work orders
- Add/remove members
See templates
Payment documentation for completed work orders
- Issuing tax forms to contractors
- Filing the entity's taxes
- Integrate other entity formations (e.g. Malta Technology Arrangement, Wyoming LLC)