## Smart Invoice Community call ### 2023-11-16 <!-- Put the link to this slide here so people can follow --> slides: https://hackmd.io/@smartinvoice/Skxjl3aXVa --- ## Agenda - What should these community calls be? - How often should they be? - Updates from teams - Proposals to discuss - Discuss rename/rebrand for protocol - Set funds aside for protocol specific dev --- ## What should this meeting be for? Note: - TE: product-team-driven meetings so the protocol team's efforts are aligned with the product teams' needs. e.g. 60/40 split - plor: at this stage there's also a need to clarify the scope and needs of the protocol itself. Maybe it's less feature dev and more repo maintenance, e.g. - scoot: opportunities to make base layer contracts more flexible so we can use extensions rather than make new escrow types altogether - TE: ^ might not need factory changes rn. now's the time to think of other base changes we might do at this point - specifically the fee implementation --- ## How often? - stick to the fortnightly schedule? monthly? other options? - Note: - 2 weeks (tufnel) - monthly (tufnel, ben, george) - conclusion: monthly for now, async in between of course --- ## Updates #### Smart Invoice #### Smart Grants #### Protocol Maintainers Note: - Smart Invoice - ben: the marketing side has a lot of figuring out and still some friction b/c I don't fully understand what richa needs - Smart Grants - derrek: sprint created landing page, Christina is networking, derrek is developing an MVP front-end - vika: happy to help with UI/UX design/research - plor: we don't want to build something no one wants, so our priority is figuring that out - Protocol - tufnel: todo list just about done, so it'll be open from here - george: we've still gotta make sure subgraph is up to date (thanks scoot). anything else might be v2 --- ## Proposals - $4500 for Smart Grants - ###### https://admin.daohaus.club/#/molochV3/0x64/0xc4c2f72157e502a6980dcdf75744c7a83f6ffcfd/proposal/17 - ###### see proposal for detail. - ###### tl;dr: funds product development as a stopgap while the team seeks more external funding --- ## Rename - plor grabbed salus.eth if people like that concept: Roman goddess of Health, Protection & Well-Being - Magna Carta protocol also suggested --- ## Protocol funds - How do we fund the maintenence of the protocol? (e.g. implementing fees) - What are the needs to wrap up near term? Note: - plor, tufnel agree holding funds in current DAO (i.e. not needing subDAOs) works for now - benedictvs recommends seeking external funding opportunities (e.g. grants for L1 deployments) - diversifying arbitration: benedictvs is a member of Distributed Ledger Technologies, which may have lawyers interested in filling LexDAO's arbitration role --- ## Discussion - v2 protocol mtg w/ scott, tufnel, george to follow - governance: plor desires more clarity on how allocating responsibility for approving modules, deploying, etc. are handled --- ## Thanks!