PAC Protocol migration

Secure fixed-ratio migration to DeFCoN

Fixed 10:1 migration ratio from PAC Protocol to DeFCoN (1 PAC = 0.1 DFCN).

This portal enables a secure, fixed-ratio migration of PAC to DeFCoN following the network transition. Generate a unique PAC deposit address, send PAC, and receive DeFCoN automatically after the required confirmations.

No account or login required. Test with a small amount first if this is your first migration.

Swap State Machine

The backend uses explicit state transitions, blocking invalid moves and preventing duplicate payouts after restarts.

  1. CREATEDRequest created
  2. DEPOSIT_SEENDeposit observed
  3. CONFIRMINGWaiting for confirmations
  4. CONFIRMEDEligible for payout
  5. PAIDDFCN payout broadcast
REORG_DETECTED

If blockhash changes or confirmations regress, payout flow is frozen automatically until the chain is stable.

Start Migration

No login or account is required. Enter your DeFCoN payout address to generate a unique PAC deposit address.

You send PAC Protocol (PAC)
1,000,000 PAC
You receive DeFCoN (DFCN)
100,000 DFCN
- DFCN

PAC amount -> automatically show estimated DFCN receive.

Fixed migration rate: 1 PAC = 0.1 DFCN

Send PAC only from a wallet you control. Do NOT send from exchanges.

Optional. If provided, the service sends automated updates when the request is created, when PAC is first detected, and when the DFCN payout is completed. This address is stored privately and is never shown publicly.

The system returns a unique PAC deposit address, fixed ratio, minimum deposit, and expiration timestamp. Deposits below the minimum are not eligible for payout and may not be refunded unless the same request is topped up to the minimum before expiration.

Migrations above 51,000,000 PAC (5,100,000 DFCN) are subject to manual review and may take up to 24 hours to process.

Resume Existing Migration

Continue tracking by Migration ID. Recent IDs are stored only in this browser.

How It Works

Simple four-step migration flow with explicit state tracking and confirmation gating.

  1. 1

    Enter your DeFCoN payout address

    We generate a unique PAC deposit address for this migration request.

  2. 2

    Send PAC

    Send PAC to the generated deposit address for this request only.

  3. 3

    Wait for confirmations

    The service waits for the required confirmation threshold before payout.

  4. 4

    Receive DFCN automatically

    The payout worker sends DeFCoN to your provided address once eligible.

Migration Details

Operational parameters are fixed and monitored. Some values are shown live below.

Migration Parameters

  • Migration ratio1 PAC = 0.1 DFCN (10:1)
  • Minimum depositShown after request creation
  • Confirmation requirement100 blocks
  • Payout modeAutomatic fixed-ratio payout

Operational Controls

  • Hot wallet liquidityMonitored continuously
  • Daily payout limitEnforced by backend policy
  • Reorg handlingFail-closed freeze protection
  • Wallet unlockOnly around sendtoaddress

Dedicated full nodes

PAC and DeFCoN are monitored via local full-node RPC, not a third-party explorer API.

Reorg detection

Blockhash changes and confirmation drops trigger reorg detection and payout freeze protection.

Hot/cold separation

Operational payouts come from a monitored hot wallet, while treasury storage should remain in cold wallets.

FAQ

What happens after the migration period ends?

Requests created after the service is paused or closed may be rejected. Follow official project communication for the final migration deadline and post-period process.

Can I send multiple PAC transactions to the same migration request?

The backend can detect multiple deposits, but you should follow the documented policy for your migration campaign. Using a fresh request per transfer is the safest approach.

What if my transaction is delayed?

The payout waits for the configured confirmation requirement. If the network is slow or paused due to a safety event, payout may be delayed until conditions recover.

Will my migration stop if I close the browser?

No. Migration processing runs on the backend and continues even if you close the page or your device goes offline. You can restore the same request later with the Resume section using your Migration ID, or by opening your saved tracking link.

Can I receive email updates about my migration?

Yes. The request form includes an optional status email field. If provided, the service can send automated notifications when the request is created, when a PAC deposit is first detected, and when the DeFCoN payout is completed.

Is this custodial?

This is a migration service, not a trading exchange. Funds sent to the migration deposit address are processed for fixed-ratio migration according to the published rules.

What if I send below the minimum deposit or after expiration?

Always verify the minimum deposit and expiration before sending. Deposits below the minimum are not eligible for payout and may not be refunded unless the same request is topped up to the minimum before expiration. If a request expires before the minimum is reached, no automatic payout is sent.

Where can I review the official project repositories?

PAC Protocol source: github.com/pacprotocol/pacprotocol. DeFCoN source: github.com/defcon-project/defcon.

Total PAC Migrated — PAC
Total DFCN Issued — DFCN
Completed Migrations — swaps