Skip to main content

Ritual of Light

Living Governance Document

The DAO Masons rulebook is a living document that may change significantly in response to internal governance.

Do you see a way these docs could improve? Click the Give feedback button at the top of this document or join the DAO Masons Discord to let us know.


Ritual of Light is a proportional compensation system for Projects. It allows the team full visibility into how much work each team member is doing, how long it is taking, and ensures that everyone is paid in proportion to the amount of work they have done.

Current Implementation

Beginning of Project

  • Project Lead creates a Project DAO.
  • Project Lead deploys a Ritual of Light contract and adds it to the Project DAO.
  • Project Lead deploys Project DAO app (example) using the Ritual of Light app template.
  • The default Value Rubric is 1 hour of work = 1 share.
  • The Project Lead may adopt an alternate Value Rubric that awards shares in a different way.
  • Any received funds for the project should be held in escrow with client or held by the Core DAO until the project is complete.

During Project

  • The Project Team meets together at a regular interval as defined in the Recurring Processes section of the Project Proposal (weekly, bi-weekly, etc.).
  • Each Project Team Member makes a claim for the work they have done since the last meeting.
  • Any team member can ask for more information or contest a claim, with Project Lead having final say when there is no consensus.
  • Each Project Team Member adds their claim to the app, and they are rewarded with shares in the Project DAO.
  • The claims are automatically displayed in a timeline feed on the Project DAO's app.

End of Project

  • Clients or DAO Masons have a chance to review the project DAO timeline to ensure that the work was done as promised.
  • If this is an External Project (with a client), and the client is happy with the work, the funds can be pulled from escrow.
  • DAO Masons (or other parent DAO) receives its share of the funds (default 10%).
  • Then the remaining funds are sent to the Project DAO, and each Project Team Member can pull their proportion of the funds.
  • The team simply uses the ragequit function on the project DAO to pull. This will burn the shares they have earned, and they will receive funds in direct proportion to the amount of work they have done.


Working remote feels like working in the dark. After trying this system ourselves, we found that it felt like we were finally working with the lights on. It suddenly became clear how much work we were doing and how much value we were adding. Thus the name, Ritual of Light.

In the dark, we don't get the inspiration boost from seeing others make progress on difficult tasks. We don't have the accountability of having to show up to a physical location and demonstrate that work is being done.

Moreover, in any organization, it's really hard to reward people based on the quantity and quality of the work they've done. In the past, teams have delegated this task to managers and HR departments who assign salary levels based on arbitrary factors like experience, education, and seniority -- when none of this has anything to do with how much work someone is actually doing.

DAOs have a unique opportunity to solve this problem.

The Ritual of Light provides a system where the team is able to decide what is valuable, and then pay those contributors based on the amount of time they have applied to a task, times the value of that task. It's important to understand that 'value' is subjective and should be defined by the organization doing the work.

What Problem are we Solving?


  • Most teams work in the dark, they don't know how much their teammates are contributing, and clients have no real way to track progress on the job they paid for.
  • With remote work, it is difficult to tell who is doing the work and spending how much time on it.
  • While Kanban boards are great for tracking progress on tasks, they don't account well for how long they should take. If someone does assign a time estimate, it is often arbitrary and not based on any real data.
  • Clients often lack awareness of work progress and ongoing project status. Real-time project progress visibility would benefit clients.

Misaligned Incentives

  • Bounty based compensation incentivizes contributors to finish a task as quickly as possible, even if that means they are not doing the best work they can.
  • Value is extremely subjective and can be hard to assign. We need a system where small groups of people can decide what to incentivize.
  • Most importantly, we need a compensation system that is directly proportional to the amount of work done. Project members are incentivized to work more in order to get paid more.

Why is this a good solution?

Ritual of Light is a fully transparent, open system where a small group of contributors are able to decide what is valuable, then pay those contributors based on the amount of work they have done.


  • With every claim a team member makes, we get an update on the progress they are making.
  • We have a 'leaderboard' that shows the amount of work each team member has done, encouraging friendly competition.
  • Clients now have a window into the progress of the project.


  • The only way to earn is to make contributions.
  • If a team member wishes to make a claim, they must first tell the DAO what they've done and for how long. The app and synchronous communication tools like Discord allow the team to use social dynamics to hold each other accountable -- without risking funds.


  • Far faster than proposals and voting, the team can track progress and contributions on the fly.
  • The contract assigns shares optimistically. While this is trustful, it allows the team to greatly minimize governance overhead for trusted actors, while still adding friction to those who try to maliciously game the system.



  • The RoL contract allows contributors to optimistically add their claims to the contract. This means that if a contributor is dishonest, they can add a claim for work they didn't do.
  • This would require the team or a team lead to adjust the claim using a DAO proposal.
  • For this reason, Funds should be escrowed or held by the Core DAO until the project is complete. This ensures that the team is not able to pull funds before the project is complete and the timeline has been audited.

Time-Based Compensation

  • With every time based compensation system, there an incentive to take more time to finish tasks.
  • This is why we have a Value Rubric that allows the team to assign different values to different tasks. Speed of progress could be a metric the team uses to determine the value of a task.
  • The team has an opportunity to review reported work at regular meetings and the Project Lead (or a process defined by the Project Lead) can make adjustments to claimed work.
  • Since funds are drawn from the same pool, there is an incentive to call out bad actors, or to point out inefficient work practices in comparison to other team members.


Automation Phase 1

  • Build a summoner app that makes it easy to get all the project Data and the necessary parameters for the Ritual of Light contract.
  • Record a video of how to add a project DAO to the RoL app template, and how to deploy.

Automation Phase 2

  • Write a factory contract that summons a Project DAO and RoL contract in the same transaction.
  • New factory contract needs to take in a Core DAO field so we can build interfaces that organize projects based on the Core DAO
  • Build an interface that allows DAOs to see all their current and past projects, and their own RoL apps that each team is using.

Automation Phase 3 (V3)

  • Write a new Ownable 1155 standard that takes only the Moloch functionality that we need (member list, shares, ragequit or proportional disperse)
  • Combine that contract with an escrow contract that automates the payment from the client, to the Project DAO and Core DAO.
  • Build a new interface that allows DAOs to see all their current and past projects, and their own RoL apps that each team is using.
  • Build the app so that it can be used by any DAO, not just DAO Masons.


  • A clean, simple, and easy to use interface that allows DAOs to create projects, and manage them all in one place.
  • The interface allows DAOs to see all their current and past projects, and their own RoL apps that each team is using.
  • The contract is minimal and has a small surface area for attacks.
  • Anyone can easily spin up a new project DAO and start using it.

Current Stage of Development

  • Unimplemented
  • Manual
  • Systemetized
  • Partially Automated
  • Fully Automated/Passive

Current State of This Page

  • Empty
  • Rough Draft
  • Editing passes: 4
  • Final Draft
  • Ratified