Multi-token payroll dApp for Aragon
Aragon gave communities a framework to run on-chain organizations, but paying contributors inside those DAOs stayed manual: treasurers moved funds by hand and tracked salaries in spreadsheets that lived outside the chain. Protofire built the Payroll dApp inside the Aragon apps framework, covering the aragonOS Solidity contracts, a React and Web3 front end, and an AssemblyScript subgraph that indexed payroll activity for the interface.
The app let a DAO add contributors, pre-authorize recurring payments in multiple tokens, and view each person's payment history and balance in one place. The code is public in Protofire's Aragon apps repository.
“For a framework built around transparent on-chain organizations, handling compensation off-chain and by hand was a visible hole.”
Why DAO payroll was still a manual job
Aragon's framework let anyone deploy a DAO on Ethereum with on-chain voting, a shared treasury, and modular apps for governance. What it did not have was a native way to pay the people doing the work. A DAO with dozens of contributors handled compensation the way an early-stage company would without a payroll provider: someone held the keys, sent transfers by hand each cycle, and reconciled who got paid against a spreadsheet that lived outside the chain.
That gap grew with the ecosystem. As Aragon moved past a couple of thousand active DAOs, the complaints were consistent: inconsistent payment timing, workflows split across separate wallet tools, no support for paying in more than one token, and manual steps that did not scale. For a framework built around transparent on-chain organizations, handling compensation off-chain and by hand was a visible hole.
How Protofire built the Payroll dApp
Protofire built Payroll as an app within the Aragon apps framework, which meant it had to behave like a native aragonOS module, not a bolt-on. The work spanned the full stack.
On contracts, Protofire wrote the Solidity payroll logic against aragonOS v4, so the app installed into a DAO like any other Aragon permissioned app and inherited the DAO's existing governance and access controls. On the front end, Protofire built the React and Web3 interface for the two things a DAO administrator actually does: manage the roster and manage payments.
That covered adding contributors with links to the DAO's identity and finance apps, filtering and sorting the employee list, and requesting or pre-authorizing payments denominated in multiple tokens rather than a single currency.
For read access, Protofire built an AssemblyScript subgraph on The Graph that indexed payroll events, so the interface could show each contributor's historical payments, current balance, and statistics without scanning the chain on every load. Throughout, the team folded in user feedback from DAOs already running on Aragon, tightening the flows for onboarding new contributors and for reporting against the treasury.
What the Payroll dApp delivered
The engagement shipped a working, open-source payroll layer for Aragon DAOs. There are no Protofire-measured performance numbers to report; the concrete result is the app itself and what it let a DAO do:
For scale context, Aragon reported roughly 1,700 DAOs using its framework in Q1 2022, about 41,000 users, and around $900M managed by those DAOs. The Aragon Association wound down in 2023; the Payroll dApp is presented here as the historical build it was.