# Create & Deploy Contract

**Route:** `/create` **File:** `app/create/page.tsx`

The Create page deploys a contract on-chain as a Solana escrow. Funds are locked in the smart contract and can only be released when milestones are approved.

***

## Prerequisites

Before creating a contract:

* Wallet connected (Phantom, set to Devnet)
* Sufficient USDC balance — [claim 1,000 mock USDC](/contractguard-ai-docs/features/claim-usdc.md) from the navbar
* Contract audited (recommended — paste the audit hash for on-chain proof)

***

## Form Fields

| Field                 | Required | Description                      |
| --------------------- | -------- | -------------------------------- |
| Contract Title        | Yes      | Human-readable name              |
| Description           | Yes      | Scope of work                    |
| Client Wallet         | Yes      | Payer's Solana public key        |
| Contractor Wallet     | Yes      | Service provider's public key    |
| Total Amount (USDC)   | Yes      | Full contract value              |
| Milestones            | Yes      | At least one with title + amount |
| Audit Hash            | No       | SHA-256 from the Audit page      |
| Start Date / End Date | No       | Contract period                  |

> **Tip:** If you just audited a contract on `/audit`, click **Create Contract** there — the form will be pre-filled from the audit results.

***

## Defining Milestones

A contract must have at least one milestone. Milestone amounts must add up to the total contract value.

**Example breakdown:**

```
Milestone 1: UI Design Mockups              500 USDC
Milestone 2: Backend API Development      1,500 USDC
Milestone 3: Testing & Deployment           500 USDC
──────────────────────────────────────────────────
Total                                     2,500 USDC
```

***

## Deployment Flow

```mermaid
sequenceDiagram
    participant U as User
    participant UI as Create Page
    participant Sol as Solana Devnet
    participant P as Phantom Wallet

    U->>UI: Fill form + click Deploy
    UI->>Sol: Build create_contract transaction
    UI->>P: Request transaction approval
    P-->>U: Show transaction details
    U->>P: Approve
    P->>Sol: Submit transaction
    Sol-->>UI: Confirmation + Contract PDA address
    UI-->>U: Redirect to Dashboard
```

***

## What Gets Created On-Chain

After deployment, two accounts are created on Solana:

| Account         | Address                                         | Content                           |
| --------------- | ----------------------------------------------- | --------------------------------- |
| Contract PDA    | Derived from `[client, contractor, created_at]` | Contract data, milestones, status |
| USDC Escrow ATA | ATA owned by Contract PDA                       | Locked USDC funds                 |

Additionally, the contract PDF (if uploaded) is stored locally at:

```
D:\frontier\evidence\{pdaAddress}\contract\
```

And contract metadata is saved to Supabase for fast querying.

***

## Contract Statuses

```mermaid
stateDiagram-v2
    [*] --> Active : Deploy contract
    Active --> Completed : All milestones approved
    Active --> Disputed : Milestone rejected
    Disputed --> Active : Contractor revises
    Active --> Cancelled : Client cancels (funds returned)
    Completed --> [*]
    Cancelled --> [*]
```

***

## Next Step

Manage milestones and release funds → [Dashboard & Milestones](/contractguard-ai-docs/features/dashboard.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://contractguard-ai.gitbook.io/contractguard-ai-docs/features/create-contract.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.