PROPOSAL TITLE: "Create DAO Sundry Account for Proposals/Contractor Services & SanLeo Dev Contract and Restitution" CREATED DATE: 19/01/2025 AUTHOR(S): @Avereth, @SanLeo, @Fortunate IMPLEMENTERS: Multi-sig committee, @SanLeo DISCUSSION:https://discord.com/channels/835244823857332245/1044341660101910678/1327062566656282665 SUMMARY: This proposal seeks to address the DAO's need for skilled development support within the MultiSig (MS) team by considering hiring a developer(s) for Dev Contract Work (DCW) with a specific SanLeo contract, Other Dev contract terms and Contractor Work (CW) terms for other various services with future approval. This proposal also seeks to create a “Sundry” DAO account for the purpose of future contractor work and proposal use. “sundry.foundersdao.eth”. ABSTRACT: The DAO needs specialized skills for handling complex transactions, which the current MS team lacks. It has been proposed to hire SanLeo for contract development, detailing payment structures, work order processes, and retroactive payment for past contributions. This will enhance our operational capabilities, ensuring we can manage tasks like token airdrops and secure our assets efficiently. There is also scope to hire other contractors for various services once approved. MOTIVATION:The DAO's functionality has been compromised due to a lack of development expertise within the MS team. At no fault of the current team members. Hiring a developer will not only solve immediate issues but also prevent future operational risks. This proposal aims to restore confidence in the DAO's management and safeguard our collective interests. Having a Sundry account for the DAO with pre approved amount of funds and for pre approved use cases, with a shorter voting period increases the DAOs efficiency in certain required situations. CONNECTION TO MISSION: By improving our technical capabilities, we directly support the mission of empowering community-driven investment and transparency. This aligns with our goal of advancing opportunities while maintaining accountability and integrity within the FoundersDAO vision. SPECIFICATION: * Sundry Account: “sundry.foundersdao.eth” The Sundry account will be valued and denominated in USD at the time of establishment and funding. As well as for all future top ups. For the purpose of accountability, bookkeeping and budgeting, the Sundry account and any txns going in / out of it will be valued and denominated in ETH. This makes it an easier process for tracking and budgeting as we are wont be dealing with a fluctuating USD value on a daily basis. This method also has the potential to be automated with software down the track. The sundry account will be broken up into two sections with two different funding amounts and limits as they will have different uses. The total of the Sundry account per annum will be 30k USD in ETH. * A new “sundry.foundersdao.eth” multichain safe for the sundry account will be set up for: ETH, ARBone, ARBnova, Base, and ApeChain. Apechain will require more work to establish for safe vault. SanLeo has estimated 3 hours for this task. * Setup txs to set vault ETH name as sundry.foundersdao.eth. SanLeo has an estimated 1 hour. * Build script to auto generate owner swap transactions into TX JSON files (just like we use) SanLeo has estimated 2-3 hours. * This initial setup costs for our wallets will save the DAO significant time and further dev contractor fees. * SanLeo will set up tx for owner swaps for any safes. SanLeo estimates 10 minutes per vault, the number of chains irrelevant to time. * This swap software will be made open source on a PVFD GitHub account so all our software created for us is available for continual and future use. * Sundry #1 with 10k yearly allocated, Sundry #2 with 20k yearly allocated. Each sundry account has to be approved to be topped up at the end of each 12 month cycle on the date of this proposal being approved. The USD value in ETH is calculated at both time of initial funding and on any future top up date. There is no requirement to rebalance the accounts within a 12 month cycle. Any remaining balance in the Sundry account after a 12 month cycle will be rolled over into the following 12 month cycle. The MS team and Avereth will manage the offchain record keeping of the Sundry account to ensure limits are not breached from either sundry section. This will be done in the FoundersDAO Committees Discord Server in a separate channel record keeping all transactions and amounts for easy calculation. (Txn hash link shared etc). And can be managed in future with software built on a contractor dev once approved. Sundry #1 Will be funded by our “foundersdao.eth” wallet address with $10k USD in ETH initially. Sundry #2 will be funded by our “foundersdao.eth” wallet address with $20k USD in ETH initially. (with future approval, the potential ability to swap out ‘x’ amount of with $gg to promote Reboot and BattlePlan, once $gg claimed up to the $20k USD limit). Bringing our Sundray funding to $30k USD in ETH at time of funding. Use of the DAOs sundry account is limited to certain use cases. Sundry #1 is used by the MS team at their discretion for DWOs. See “Dev Work Orders & Approval” below for details. And is limited to $10k USD in ETH per year. Sundry #2 is used for proposals that might be time sensitive that require funding for either DWO or purchases etc. This will use a 2-Day voting Snapshot period, that will be set up by SanLeo. And is limited to $20k USD in ETH per year. * SanLeo Contractor Terms: SanLeo Contractor Work ETH Payment Address: 0x9dAd6f6ADf207581FEDefF0d03A98D5c244bC8C4 SanLeo will be paid at $120 USD per hour, with hours tracked and documented. The Contracted Developer will track their hours worked and provide documentation for completed work orders. Any work of significance, future value to the DAO and for accountability must be made open source via PVFD GitHub. Any potential developer(s) reserve the right to refuse work orders if they are infeasible, or cannot be committed to at time of enquiry. * Dev Contractors other than SanLeo Terms: Before any other contractor can be hired for a DWO a proposal is to be raised to approve the contractor. The proposal is to include a detailed summary on the contractor. Suggested but not limited to; hourly rate, prior work and years experience, reliability, trustworthiness, skills, any connections with PV or the DAO etc Any work of significance, future value to the DAO and for accountability must be made open source via PVFD GitHub here: https://github.com/founders-dao . The DWO budget limits below can be applied to other dev contractors also. * Dev Work Orders/Proposals & Approval: Three ways a DWO can be raised and approved, 1. MS team requires dev work to carry out a proposal that did not have prior approval to pay for a DWO or has issues with safe vault etc, uses Sundry Section #1 for payments, the $10k USD limit per year. 2. A quick urgent DWO 2-Day Snapshot vote with a basic DWO put forth to the DAO on what's required, why and to include the contractors quote. This uses Sundry Section #2 funding of $20k USD per year. 3. To include a DWO in a main DAO Snapshot 7-day vote proposal (as we currently vote). * 1. MS team can approve up to $10,000/year for work orders with 3/7 members agreement in MS team chat with Sundry Section #1 * 2. Snapshot vote for up to $20,000/year with a 2-day voting period, no quorum req Sundry Section #2. SanLeo will set up the 2-Day Snapshot voting platform to do so. If work has been completed but not approved prior if it's something urgent, the contractor can seek retroactive payment by submitting a SWO for 2-day snapshot voting including other relevant documentation on the work order etc. A SWO is paid out of this sundry account. The risk the contractor is taking is not being paid or approved for this work via the 2-day snapshot process. * Any exceedance in the above budget limits will require a DAO main Snapshot vote. The DAO does not have to use these funds on the sole purpose that they are available every year. * 3. Community members are encouraged to enquire with developers when drafting proposals to verify feasibility, availability of dev, time and cost. A DWO should also be included in any future proposal that will require dev assistance to carry out. A detailed prop should always include the DWO from the potential contracted dev including estimated time to complete and hourly rate. * The hired developer contractor is required to provide regular progress updates to the MS team, with a minimum frequency of once a week, but ideally every few days. If any delays or changes occur that deviate from the original approved Development Work Order (DWO), the contractor must notify the MS team immediately. This includes, but is not limited to, requests for time extensions due to unforeseen circumstances, personal delays, or changes in methodology. The MS team will review and address these issues on a case-by-case basis. If significant changes are proposed that substantially alter the original DWO or outcome, all work must be halted until a new path forward is agreed upon and approved by the DAO. Approval can be obtained through a 2-day Snapshot vote with no quorum requirement, an announced poll in Discord outlining the proposed changes, or cancellation of the job altogether. * A Template for DWOs will be created by the SanLeo to assist DAO with providing the contractor with adequate information and made available to the MS team. * Contractor Work Orders CWO Contractor works orders include any contractor that is not a developer. These contractors could be, but not limited to, Community Manager, Comms, Marketing, Collab Manager, or any other service the DAO has a need for. CWOs can be funded or paid for by Section #2 of the “sundry.foundersdao.eth” account with the same 2-day Snapshot vote approved by the DAO, or via 7-day voting Snapshot and funded by “foundersdao.eth”. A CWO is raised by either a DAO community member or the contractor themselves to seek payment for a service or retroactive payments for services already completed. * DWO + CWO Payment and Approval: Completed DWOs and CWOs must undergo verification by the Multisig Team to confirm hours worked and job completion. Subsequent payment proposals will be submitted by the contractor and require DAO approval through a Snapshot vote, mirroring the initial proposal approval process, 7-day vote or 2-day vote. This approach ensures that payments are authorized and auditable, while also incentivizing contractors to initiate payment proposals in a timely manner and not be an admin burden on the DAO. * Payment Schedule: Monthly payments post-approval of COMPLETED DWOs and CWOs can be carried out by the MS team. The first of every month and payment carried out as soon as reasonably practicable. * Non-Completion of Prior Work and Restitution Payment: SanLeo was paid $10k USD in ETH to build an Alpha discord server. He was paid on a monthly basis as he built it and received all his payments before completing it. He never completed the work due to personal reasons he has discussed within the DAO some details already, and has disclosed what happened to @Avereth. SanLeo has agreed to give $10k USD in ETH back to the DAO. He will have some of the original ETH paid to him leftover, which compensates him for the time he spent building the server. On completion of Restitution Payment the “PVFD Alpha Bot” Server will be deleted. * Retroactive Dev Payment: Proposed to pay $1,800 USD for 15 hours of previously completed work by SanLeo. Swapping over owners for all the DAOs safes including ETH, ARB One, ARB Nova. This required setting up an entirely separate instance of the SAFE multisig website infrastructure in order to sign transactions on Nova, this was important to secure our $gg holdings which are held in our multisig safes. If this proposal is passed and SanLeo is to send the DAO $10k USD in ETH, the $1800 can be deducted from it * Encouragement for DAO members to discuss technical specifics and feasibility with the contractor before submitting any DWO and engage with other community members before submitting a CWO. * Dev Contractor will do their best to explain and teach what they can when completing various DWOs to help educate and upskill the MS team members. BENEFITS: * Enhanced technical capability for complex transactions within the DAO. * Increased security and efficiency in managing assets and executing proposals. * Building a sustainable model for future proposal needs with clear processes. DRAWBACKS: * Financial commitment to external developers, which could strain the DAO's treasury if not managed carefully. * Potential for delays if work orders are not approved swiftly or if there are disagreements on terms. * Dependence on a single contractor might limit flexibility unless other options are kept open. OUTCOMES: * Success will be measured by the timely execution of complex transactions without errors, the security of asset management, and the satisfaction of DAO members with the process clarity and outcomes. * Metrics to track include: * Number of successfully completed work orders. * Time from proposal to execution for critical tasks. * Engagement in development discussions and voting. * Results will be shared via regular updates in the DAO's communication channels, with detailed reports post each significant transaction or development cycle. VOTING CHOICES ON NEXT PAGE: VOTING CHOICES: 1. #1 FOR - APPROVE ALL. Sundry Account, hire SanLeo under the proposed terms, approve all payments, dev work and DWO+CWO contractor terms. 2. #2 FOR - APPROVE SOME. The Sundry Account and Restitution Payment from SanLeo, APPROVE payments and DWO+CWO contractor terms. DENY hiring SanLeo 3. #3 FOR - APPROVE SOME. SanLeo under proposed terms, approve all payments, dev work and DWO contractor terms. DENY Sundry Account. 4. #4 AGAINST - Sit on our Hands and let the funds round trip the next bear market - Do nothing. 5. #5 ABSTAIN - no action