TL;DR
The establishment of a multi-country treasury aims to achieve the goal of making LXDAO more transparent and automated, improve the operational efficiency and flexibility of LXDAO, optimize the fund unlocking process, make the fund flow clearer, prepare for a new distribution mechanism, and reduce the risk of fund loss.
The ownership of the multi-country treasury belongs to LXDAO, including the working group treasury and the project group treasury. All income needs to be distributed after entering the treasury. In addition, it details the fund distribution process, the composition of multiple signatures for sub-treasuries, and the kanban content and related processes after the creation of multiple treasuries, including the process of treasury creation, replacement of multiple signatories, and destruction of the treasury. It also proposes a phased implementation plan.
1. Background of Multi-Treasuries
The future of LXDAO envisions a sufficiently decentralized organization with numerous independently operating projects and groups. As the organization grows, relying solely on the main treasury for all processes will reduce overall operational efficiency and flexibility. With a multi-treasury structure, many processes can be optimized:
- Funding Unlocking Process: Each project and group will have a fixed budget, providing a clearer plan for fund utilization. Milestones can be used to establish a funding unlocking cadence unique to each project, eliminating the need to adhere strictly to the main treasury’s schedule.
- Resource Pre-Allocation: Projects and working groups can lock resources in advance, preventing them from being taken by other projects or overused by the project itself.
- Clearer Funding Flows: LXDAO’s internal funding flows will become more transparent, allowing for a clear understanding of where money comes from and where it goes.
- Preparation for New Allocation Mechanisms: The current allocation process involves registration, manpower statistics, and then distribution, which is inefficient and prone to errors. Future iterations will automatically calculate allocation quotas based on records and execute them after voting.
- Reducing Funding Risks: It reduces the risk of funds being attacked in a single treasury (risk in Scenario 1: the risk of LXDAO’s multi-signers being compromised).
The diagram of the multi-treasury structure is as follows:
2. Explanation of Multi-Treasuries
The ownership and control of all multi-treasuries should belong to LXDAO.
- Working Group Treasury: The ownership and funds of the working group’s treasury belong to LXDAO.
- Project Group Treasury: The ownership and funds of the project group’s treasury also belong to LXDAO. All revenue must enter the treasury (this needs to be stated in the project proposal), and all funds should be distributed after entering the treasury (also needs to be specified in the overall proposal). For collaborative projects, funds must first be deposited into the LXDAO project treasury.
In the current self-treasury system, only the distribution of U will be involved. For LXP, registration is still required, followed by unified distribution.
2.1 Fund Distribution Process
Milestone Funding Unlocking (Tally) → Confirmation & Voting by Multi-Signers of the Treasury → fs Record (Optional) → Fund Distribution → Dashboard Disclosure
2.2 Composition of Multi-Signers for Sub-Treasuries
- Working Groups (excluding Forge Group): Fixed members of the Forge team and the leader of the working group.
- Forge Group: Leaders of each working group (including the leader of the Forge group).
- Projects: Initially composed of fixed members of Forge and PMs, with subsequent adjustments based on proposals.
3. Multi-Treasury Processes
After the creation of multi-treasuries, a dashboard needs to be constructed for each treasury. The dashboard should include the following information:
- Addresses, asset information, and multi-signer details of the main treasury and project treasuries, ensuring complete transparency and traceability.
- Income information of treasuries.
- Expenditure information of treasuries.
- History of multi-signer replacements.
Multi-treasuries primarily involve three processes:
- Treasury Creation Process: Initiated after a proposal is approved.
- Multi-Signer Replacement Process: Conducted when there are changes in project PMs or Forge team members, or during seasonal transitions.
- Project Treasury Destruction Process: When a project terminates, all funds in the sub-treasury must be transferred back to the main treasury, and the project treasury is archived. For working group sub-treasuries, remaining funds are transferred back to the main treasury at the end of the season, with the sub-treasury retained.
Any changes to treasuries must be announced in the community forum. The details of the three processes are as follows:
Project Treasury Creation Process
- Project/Workgroup proposal approved (or existing project)
- Project PM/Workgroup Leader creates a safe treasury
- Fixed members of the Forge team are added as multi-signature members (final multi-signature members will be the PM and the Forge team)
- The multi-signature team of the Forge group consists of leaders from various workgroups (including the Forge group leader)
- Add the treasury to the dashboard and automatically update the data
- Publish treasury information on the community forum
Treasury Multi-signature Replacement Process
- Replacement of project PM or Forge team members
- Update the multi-signature
- The treasury dashboard automatically retrieves and updates the data
- Publish treasury information on the community forum
Treasury Destruction Process
- Project termination
- Transfer all remaining funds back to the lxdao main treasury
- The treasury dashboard automatically retrieves and updates the data
- Publish treasury information on the community forum
Staged Implementation
- Experimental phase: Forge and governance teams create sub-treasuries and use Fairsharing for salary payments
- Phase 1: Each workgroup and project creates a sub-treasury and uses Fairsharing for salary payments
- Phase 2: Complete the treasury dashboard, automate data retrieval and updates, and update everyone’s Profile
- Phase 3: Enable the Tally on-chain governance framework
TL;DR
设立多国库旨在实现 LXDAO 更透明、更自动化的目标，提升 LXDAO 的运行效率和灵活度，并优化资金解锁流程，使资金流转更清晰，为新的分配机制做准备，同时也降低资金损失的风险。
多国库的归属权属于LXDAO，包括工作组国库和项目组国库，所有收入需进入国库后再分发。另外详细说明了资金发放流程、子国库多签组成以及多国库创建后的看板内容和相关流程，包括国库创建、多签人更换和国库销毁流程，并提出了分阶段实施计划。
1. 多国库设立背景
LXDAO 的未来是一个足够去中心化的组织，会有很多独立运行的项目和小组，随着组织不断变大，如果全部流程都依赖主国库，那么就会降低整体的运行效率和灵活度。在多国库的结构下，很多流程可以被优化：
- 资金解锁流程：每个项目和小组有自己固定的预算，对资金的使用规划会更加清晰，可以利用 milestone 来让项目有自己的资金解锁节奏，而不用完全按照主国库的节奏
- 提前锁定资源：项目和工作组可以提前锁定资源，避免被其他项目占用或者项目本身超用
- 资金流转更清晰：LXDAO 内部资金的流转会更加清晰，清晰地知道钱从哪里来，到哪里去
- 为新的分配机制做准备：当前的分配流程是先登记，人力统计，然后再发放，效率低，而且容易出错，后续将会基于记录自动统计分配额度，然后投票后执行
- 降低资金风险：降低资金在单一国库中被攻击的风险（方案 1 的风险：LXDAO 多签人被攻破的风险）
多国库示意图如下：
2. 多国库说明
多国库的归属权应该都是属于 LXDAO，应当被 LXDAO 控制。
- 工作组国库：工作组的国库的归属权和资金都属于 LXDAO
- 项目组国库：项目组的国库归属权和资金都属于 LXDAO，所有的收入都需要进入国库（这点在项目立项的提案中需要说明），所有的资金收入应该进入国库之后再分发（也需要在提案总说明），如果是合作类型的项目，每次需要将资金先打入到 LXDAO 项目国库。
在当前的自国库中，只会涉及 U 的发放，对于 LXP 还是需要登记，然后统一发放。
2.1 资金发放流程
Milestone 资金解锁 （Tally）→ 国库多签人确认&投票 → fs 记录（可选）→ 资金发放 → dashboard 公示
2.2 子国库多签组成
- 工作组（forge 组除外）：forge 小组固定成员和工作组组长
- Forge 组：各个工作组组长（包括 forge 组组长）
- 项目：前期由 Forge 固定成员和 PM 组成，后续根据提案再调整
3. 多国库流程
多国库创建之后，需要为多国库构建看板，国库看板需要包含的信息：
- 主国库和项目国库的地址、资产信息、多签人信息，完全公开透明、可追溯
- 国库的收入信息
- 国库的支出信息
- 多签人更换历史
多国库主要包括三个流程：
- 国库创建流程：提案通过之后进行
- 多签人更换流程：在项目 PM或者 Forge 小组成员变更、Season 更替时，需要对多签人进行更换
- 项目国库销毁流程：在项目终止时需要将子国库资金全部转回到主国库，并将项目国库归档，对于工作组子国库，在 season 结束之后，需要将剩余资金转回主国库，子国库保留。
在每次国库产生变更时，都需要在社区论坛中公示。三个流程细节如下：
项目国库创建流程
- 项目/工作组提案通过（或者存量项目）
- 项目 PM/工作组 Leader 创建 safe 国库
- 添加 Forge 小组固定成员为多签人（最终多签人为 PM 和 Forge 小组）
- Forge 小组的多签由各个工作组（包括 Forge 小组）的 Leader 组成
- 添加国库到看板，并自动更新数据
- 社区论坛公示国库信息
国库多签人更换流程
- 项目 PM 或者 Forge 小组成员有更换
- 更新多签
- 国库看板自动拉取数据更新
- 社区论坛公示国库信息
国库销毁流程
- 项目终止
- 将剩余资金全部转回到 lxdao 主国库
- 国库看板自动拉取数据更新
- 社区论坛公示国库信息
分阶段实施
- 实验阶段：Forge 和治理小组创建子国库，使用 Fairsharing 发工资
- 第一阶段：各个工作组和项目创建子国库，使用 Fairsharing 发工资
- 第二阶段：完成国库看板，自动化拉取和更新数据，并更新每个人的 Profile
- 第三阶段：启用 Tally 链上治理框架