Direct Agreement Mode

Create Milestone Agreement

Use this flow when the client and worker already know each other. Define the scope, lock the full amount once, then move milestone-by-milestone through proof, review, and settlement.

Client Operator

Creates the agreement, funds it once, and decides when each milestone should pay out or move into dispute.

Worker Role

Delivers each checkpoint, submits proof, and stays aligned with the agreement description and milestone acceptance criteria.

Lifecycle

Create → fund → deliver → review → settle. PactAgent keeps that sequence visible on the agreement detail page after creation.

When To Use Grant Mode Instead

If the work came from a DAO program or ecosystem bounty, use the import flow so source attribution and treasury context stay attached.

Wallet Access

Finish wallet access before creating an agreement

Agreement creation requires a connected wallet, sign-in approval, and a wallet that can approve funding actions.

Current state

Wallet not connected yet.

1. Connect wallet2. Approve sign-in3. Start using PactAgent

Connect your wallet, then approve the sign-in request to unlock agreements, invites, webhooks, and profile settings.

Current

Connect wallet

Choose a CCC-compatible wallet and link it to PactAgent.

Approve sign-in

Approve the wallet sign-in request so PactAgent can open your agreements safely.

Start using PactAgent

Create agreements, accept invites, and approve onchain actions once your wallet is ready.

Guided Setup

Move through the agreement with less guesswork

Build the structure first, then use the summary rail to spot anything unclear before you create the draft.

Agreement Basics

Define the relationship and the scope

This becomes the reference point for proof, review, and any later dispute handling.

Keep the title short and the scope specific enough that someone outside the conversation could understand what “done” means.

Agreement Title

Use a short agreement name both parties will immediately recognize.

Agreement Description

Explain the scope clearly enough that disputes can be resolved against this text later.

Worker Address

Enter the worker CKB wallet address for agreement participation, proof submission, and CKB fallback settlement.

Counterparty check

If this is the wrong wallet, every later proof, payout, and invite action becomes harder to recover from.

Agreement Summary

See the draft build up as you work

This rail keeps the important consequences visible while you edit the structure on the left.

Draft title

Untitled agreement

Describe the scope so both parties can point back to it later.

Escrow total

0 CKB

Milestones

2 total

Ready milestones

0/2

Timing and payout

Deadline7 days

Dispute window24 hours

Payout networkCKB

Release modePartial

Readiness Check

Basics are clear

The title, scope, and worker wallet make sense.

Milestones are actionable

Each checkpoint has a title, acceptance detail, and amount.

Workflow rules are safe

Deadlines, dispute window, proof, and payout rules are set.

Most useful habit

Write milestones as if someone else will have to review them without context. That makes approvals smoother and disputes easier to resolve.

What happens after create

The agreement is saved as a draft first, so you can review it before funding.

Once funded, the first milestone becomes the operational starting point.

The detail page becomes the live workspace for proof, review, payout, and disputes.

If the draft stays unfunded, you can still share it, refine it, or invite the worker later.