Back to dashboard
Grant / Bounty Mode

Bring ecosystem grants into a manual milestone contract

Keep the original source context, lock the full treasury once, and release each milestone only after explicit human review. This flow is built for grants that need attribution, governance memory, and careful payout control.

Source attribution stays attached
Fund once, release milestone by milestone
Manual review before every payout
How It Flows
Import the original grant or bounty source
Define milestones and the total treasury amount
Fund the full amount once after creation
Review and release each milestone manually
Source Intake

Anchor the original grant context

Capture where this work came from so reviewers can evaluate milestone proof against the original treasury intent, not just the rewritten contract.

Attribution first
Start with the forum thread

Paste the Nervos grant thread first. PactAgent will pull the title, summary, budget references, and milestone draft structure before you fill the remaining fields.

Paste the original DAO proposal, forum post, or bounty page link here first.

Operator

Imports the source, defines milestones, and prepares the full grant for one treasury funding action.

Builder / Grantee

Delivers each checkpoint and submits proof against the imported scope, notes, and review expectations.

Choose where the work originated so the attribution reads correctly.

A human-friendly source name, not the full URL.

Optional but recommended: the discussion thread PactAgent should keep synced over time.

Optional external ID from the source system.

Optional sponsor, program, or DAO treasury name.

Use the title exactly as the community or DAO published it.

Recommended: copy the original scope so reviewers can compare what was promised.

Optional: use this for proposal conditions, quorum notes, or reviewer instructions.

Agreement Terms

Define the formal milestone contract

This is the live PactAgent agreement. The sponsor funds the full total after creation, and each payout only moves after manual reviewer approval.

Manual release only

Optional: leave blank to reuse the bounty title.

Paste the builder payout address exactly. Testnet addresses usually start with `ckt1`.

Optional only if the bounty description above already explains the work clearly.

Needed only for Fiber payouts. Leave blank for standard CKB settlement.

Grant Milestones

Define every deliverable the builder must complete. The total below is what the sponsor will fund once after the agreement is created.

Milestone Funding Pattern

The treasury funds a CKB reserve once. PactAgent then converts each approved USD-equivalent milestone target into CKB at payout time using a fresh quote.

Recommended Reserve To Lock
0 CKB

Includes the current live estimate of 0 CKB plus a 20% volatility buffer so the grant can tolerate moderate price movement before a top-up is needed.

Milestone 1

Reviewer-approved payout checkpoint

Short checkpoint name, for example “Prototype shipped”.

This milestone is tracked against a canonical USD target.
USD is the obligation reference for imported grants. PactAgent still pays the worker in CKB using the live quote at payout time.

Explain the deliverable, proof expected, and what counts as “done”.

How many days the builder has to deliver the full grant.

How long reviewers or counterparties have to challenge a decision.

Pick the proof format reviewers should expect from the builder.

Choose `Fiber` only if the worker can provide a valid Fiber public key.

This creates a manual PactAgent grant that keeps source attribution visible, tracks the real obligation in USD, and settles payouts in CKB through a treasury-backed reserve.