Dedicated full nodes
PAC and DeFCoN are monitored via local full-node RPC, not a third-party explorer API.
PAC Protocol migration
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.
No login or account is required. Enter your DeFCoN payout address to generate a unique PAC deposit address.
Continue tracking by Migration ID. Recent IDs are stored only in this browser.
Recent on this browser
Send a direct issue report to the operator. Contact address stays private.
Want status emails? Enter a valid address in the Status email field above. For verification, keep the same DeFCoN payout address in the form and the service will enable email updates automatically for this migration.
Send PAC only to the deposit address generated for this migration request. Payout starts after the required confirmations. 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.
Simple four-step migration flow with explicit state tracking and confirmation gating.
We generate a unique PAC deposit address for this migration request.
Send PAC to the generated deposit address for this request only.
The service waits for the required confirmation threshold before payout.
The payout worker sends DeFCoN to your provided address once eligible.
Operational parameters are fixed and monitored. Some values are shown live below.
PAC and DeFCoN are monitored via local full-node RPC, not a third-party explorer API.
Blockhash changes and confirmation drops trigger reorg detection and payout freeze protection.
Operational payouts come from a monitored hot wallet, while treasury storage should remain in cold wallets.
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.
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.
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.
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.
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.
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.
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.
PAC Protocol source: github.com/pacprotocol/pacprotocol. DeFCoN source: github.com/defcon-project/defcon.