Convert to native HKN (the burn portal)
At native mainnet, burn ERC-20 HKN on Base and receive native HKN 1:1. There is no deadline: conversion never expires, and nothing in the contract can add a deadline.
What conversion is
The burn portal on Base takes ERC-20 HKN from your wallet, burns it, and records an on-chain event naming the native address you chose. The native chain releases the same amount of native HKN to that address from its genesis migration reserve. One ERC-20 HKN becomes one native HKN. The native unit is the micro-HKN (1,000,000 per HKN), so the amount you convert must be a whole number of micro-HKN; every amount the sale delivers already is.
When
The burn portal is deployed with the sale but inert: it accepts nothing until the issuer activates it at native mainnet. Activation is one-way; its owner can activate it once and can hand that power on, but no owner can pause it, add a deadline or touch anyone's HKN. There is no deadline and no snapshot. Conversion never expires.
The token's pause never stops it
The issuer's Safe can pause HKN on Base at any time, a power meant for emergencies, and plans to freeze it for good 60–90 days after mainnet (plan), which it can do at any time. Both stop every transfer except burning — and conversion is a burn, so it keeps working through any pause and after the final freeze. HKN left at the freeze in a pool, or in a contract that cannot call the burn portal, cannot be converted by its owner: take it out before the announced date.
How, once active
Two steps from the wallet that holds the HKN: approve the burn portal for exactly the amount, then call migrate with the amount and your native address (a permit variant does both with one signature). The HKN is burned in that transaction; the native release follows from the on-chain event. This page shows the form once the burn portal is activated; until then it is a description.
The reverse path
There is none. Native HKN cannot be turned back into ERC-20 HKN, because nothing can create HKN on Base: the supply there can only go down.
What it depends on
Conversion depends on native mainnet existing. If mainnet is delayed, conversion is delayed with it; if mainnet never launches, there is nothing to convert to. It also requires the identity verification at mainnet, under the process the issuer publishes before it: a holder who has not completed it cannot convert until they do, at any later time, and the burn portal does not check it. A burn cannot be undone and a wrong native address cannot be corrected, so follow that process before you burn. The target and its conditions are in the risk block at the bottom of every page.
You may lose all of the money you put in. The ERC-20 has no use until mainnet other than the 1:1 bridge. Mainnet may be delayed.