How to fund a paid rollup proposal

To fund a paid rollup proposal, turn the promised work into a treasury request with a defined amount, recipient, delivery schedule and release path. The proposal describes what the rollup team will deliver and what the DAO will pay for it. Governance voters decide whether the request meets the DAO’s rules; a treasury contract, multisig or designated operator then carries out the approved payment. The exact route depends on the DAO, so start by finding its proposal process and treasury rules.

What should a paid rollup proposal include?

A useful proposal connects each payment to work that voters can inspect. Name the team or legal entity receiving funds, explain why the rollup needs the work, and describe what will count as completion. A budget without deliverables asks voters to approve an amount without a way to judge the result.

Break the request into parts that can be checked. For each part, state its cost, output and expected timing. A proposal might pay for engineering, audits or maintenance, but each line should say what the DAO receives. If work depends on a launch or an integration, define the condition clearly. A milestone is like a checkpoint on a route: it gives the DAO a point to verify before the next payment.

• Scope: the work, its boundaries and what is out of scope.
• Budget: the amount, token and basis for the estimate.
• Recipient: the wallet or treasury address that will receive payment.
• Delivery: milestones, evidence of completion and a reporting plan.

Also say whether the request is a one-time grant or recurring support. Recurring payments need an end date or renewal decision. If the DAO’s rules require a discussion period, proposal deposit or minimum voting threshold, account for those before submitting. These steps vary across governance systems; the proposal interface and governing documents determine the actual requirements.

How do you move the funds to the right chain?

First identify where the treasury holds the asset and where the payment must arrive. A rollup may use a different network from the DAO’s governance chain, and the same token name can refer to different assets on different networks. If the treasury’s funds must move to Manta Pacific, this guide explains the Manta Bridge route for moving assets. Check the destination network, token representation and recipient address before sending.

Next, confirm that the proposal specifies the asset and chain for payment. The amount approved in governance must match the amount the recipient can receive after any conversion or transfer costs. Keep enough of the relevant network’s native token for transaction fees. A bridge transfer may also involve a waiting period or a separate claim step, so include those actions in the payout plan instead of treating “sent” as “received.”

How does the DAO release payment after a vote?

Approval records the DAO’s decision, but it does not always send funds automatically. Some systems encode the transfer in an executable proposal; others require a multisig or treasury operator to act after the vote. Read the execution step before voting or submitting: who can trigger it, what transaction they must sign, and whether it pays the full amount at once or in stages.

For milestone payments, make the release rule observable. The proposal can identify the evidence that should be posted, the person or group that reviews it and the wallet authorized to release the next tranche. If the DAO cannot automate that review, publish the decision and transaction record so members can compare the payout with the approved terms.

Before execution, check the proposal’s final on-chain text against the budget and recipient voters reviewed. Confirm the token, chain and address from the official proposal record, then verify the transaction after it is sent. The practical standard is simple: every transfer should lead back to a voted request, and every request should say what the DAO gets for its money.