Questions

A post-quantum Layer-1 blockchain built for payments between AI agents. It uses only hash-based signatures (SLH-DSA roots, LMS/XMSS keys for agents, PayWord micropayments), enforces agent spending budgets (MandateTree) in consensus, and settles in a shielded pool with scoped one-time disclosure. It runs Malachite BFT and is compatible with x402, AP2 and MCP. A public testnet (testnet-1) is running; its explorer and network map are on hashkinetics.org, and the code is open source.

An ERC-20 token on Base: the pre-mainnet form of HKN, the native token planned for the HashKinetics network (the target and its conditions are in the risk block at the bottom of this page). Its total supply is fixed at —: all of it is created once, when the token is deployed, and there is no function that can create more, so the supply can only go down, by burning. Before mainnet its only function is the 1:1 conversion through the burn portal. It gives no revenue share, no staking rewards, no governance and no claim against the issuer other than that conversion.

The source of the Base contracts used by this sale (token, sale, Liquidity Vault, burn portal) is published and verified; each address on the signed address list links to the explorers where its source can be checked against the deployed code. These contracts have been reviewed in independent rounds by an AI system, Claude Fable 5.1, in October 2026, and by the issuer's own review; the review reports are not published. No audit report by a human firm exists on them. A review is not a proof, and a review of the Base contracts is not an audit of the chain.

— is set aside for this sale, at — per HKN, both fixed in the sale contract when it is deployed and shown live on the sale page with how much is still left. The same price for everyone in this sale, however much you buy and whenever you buy; a later sale, through another sale contract named on the signed address list, may be at another price and on other terms (the Terms, section 14).

Each purchase is filled in full or refused in full. A purchase that asks for more HKN than is left is refused by the contract and nothing moves; there are no partial fills. The buy page caps the amount you can enter at what is still left and re-reads it, and simulates your purchase, before you sign. When what is left is less than the minimum per purchase, no purchase can take it: the sale page then reads “All HKN sold” and names the remainder, the sale contract stops selling, and the remainder can only go back to the issuer's timelock once the issuer's Safe ends the sale.

At least — per purchase. There is no cap per buyer: anyone, a person or an automated agent, may buy as much as is left, in one purchase or several. One buyer may therefore buy the whole round in the first block after the start; the start time is fixed in advance so everyone has the same start.

It starts at the start time fixed in the sale contract (the sale page shows it in UTC with a countdown read from the contract), unless the issuer's Safe has paused purchases; the sale page shows it from the contract. There is no end date: it runs until every HKN set aside for it is bought (or what is left is less than one minimum purchase, which no purchase can take), or until the issuer's Safe ends it, which it can do only once and for good. After that, the unsold HKN can only go back to the issuer's timelock.

Exactly what the contracts allow, through its Safe. On the sale: pause and unpause purchases; close USDT purchases once and for good (USDC continues); switch the sanctions check off once and for good, only if the oracle stays broken; end the sale once and for good; return unsold HKN to the timelock, only after ending the sale; and move tokens someone sent to the sale by mistake, never the HKN for sale while it is open. On the token: pause and unpause it at any time, a power meant for emergencies (burning always works), and freeze it for good, which it can do at any time and plans for 60–90 days after mainnet (plan). It cannot change the price, the amount for sale, the minimum, the start time or the split, cannot take back HKN from a buyer, and never holds a buyer's money in the sale contract. Outside the Safe's powers over these contracts: wallets the issuer funds, including its liquidity bot's, may buy HKN in this sale and in any pool, and the issuer may trade HKN in any pool; and the HKN in its timelock can be moved anywhere after the timelock's notice period, including into later sales at other prices and on other terms (the Terms, sections 11 and 14).

Not to buy. The sale asks for no documents, no e-mail and no registration, and checks no location. Identity verification (KYC) happens at mainnet, under the process the issuer publishes before it, for every holder of HKN on Base, whether or not they bought here; this site has no part in it.

It gates conversion: a holder who has not completed it cannot convert HKN on Base into native HKN until they do, and may complete it at any later time. Nothing else happens to their HKN on Base. After the final freeze, their HKN on Base can only become native HKN once they verify. The burn portal does not check verification, and a burn cannot be undone, so follow the issuer's published process before you burn (the Terms, sections 3 and 7).

The sale contract checks the buying wallet against the Chainalysis sanctions oracle on Base on every purchase. The oracle holds a list Chainalysis keeps of wallet addresses under US sanctions; a wallet on that list is refused and nothing moves. That is the only check: no other list, no country or IP check, no risk score. The oracle does not know where you are, so the warning about sanctioned countries is yours to respect; a purchase it lets through is not thereby lawful for you.

If the oracle cannot answer, purchases are refused rather than let through. If it stays broken, the issuer's Safe may switch the check off for good; that is visible on-chain and shown on the sale page.

• The contract checks that the sale is open, the token is USDC or USDT (USDT only while it is not closed), the amount is at least the minimum, the purchase carries the Terms fingerprint, and enough HKN is left.
• It checks your wallet against the sanctions oracle.
• It takes exactly the amount from your wallet: — goes directly to the issuer's Safe and — directly to the Liquidity Vault, and it checks that each received exactly its share.
• It sends the HKN from the sale contract to your wallet: the amount divided by the price, rounded down to a whole micro-HKN.
• It records a Purchased event with the amount, the HKN, the split and the Terms fingerprint, on-chain and for good.

All of it happens in one transaction: either everything happens or nothing does. There is no escrow, no claim step and no waiting period.

The Terms and the buyer statement are one text file on this site. Its keccak-256 fingerprint was fixed in the sale contract when it was deployed. Your browser downloads the file, computes the fingerprint itself and compares it with the contract's; if they differ, this site refuses to offer a purchase. Every purchase sends that fingerprint to the contract, which refuses any other, so each purchase records on-chain exactly which Terms the buying wallet accepted. A change of Terms would need a new sale contract.

No. Every purchase is final once it is confirmed: there are no refunds, for any reason, and nothing to cancel. Check the preview before you sign.

USDC or USDT on Base. USDC is Circle's native USDC on Base. USDT on Base is the bridged “Tether USD”: it comes from Ethereum through the Base standard bridge and is not issued by Tether on Base. Both count 1:1 as US dollars; both addresses are on the signed address list. Not tokens on other chains, not ETH. The issuer's Safe can close USDT purchases once and for good, for example if bridged USDT loses its peg; USDC cannot be closed.

You need a small amount of ETH on Base for gas; your wallet shows the estimate before you sign. Bridging to Base is your responsibility. This site charges no fee.

USDC from a regular wallet: you sign one authorization (EIP-3009) for exactly the amount, payable only to the sale contract, and send one transaction. USDT, or any wallet with code (a smart wallet, or an address with EIP-7702 delegation): you approve exactly the purchase amount and then buy; wallets that support batching do both in one step. This site never asks you to approve more than the amount and never uses a standing allowance. Before every signature and transaction the purchase is simulated against the chain, so a purchase that would be refused is shown to you before it costs gas.

You never send USDC or USDT to an address. Tokens sent straight to the sale contract are not a purchase and may not be recoverable. Any message asking you to “send USDC to 0x…” is a scam.

The HKN is in your wallet when the transaction is confirmed. The buy page shows the transaction, the HKN received (read from the Purchased event) and a button to add HKN to your wallet's token list. HKN can be moved freely from then on.

— of every purchase goes to the Liquidity Vault, which also received HKN of its own when it was deployed. The vault adds its USDC, with the matching amount of HKN at the current pool price, to one full-range position in the official Uniswap v3 HKN/USDC pool, in rounds that anyone can trigger (the issuer's bot is planned to check continuously and to send a round whenever the vault can add). It adds only while the sale is open — started, and neither the sale nor the token paused: before the start and during a pause a round adds nothing and the USDC waits in the vault. The USDT share of USDT purchases is forwarded to the issuer's Safe, which plans to swap it to USDC and send it back to the vault only while the sale is open and the pool's price is within about — of the sale price, just before a round that can add it — never during a pause, during a run of skipped rounds, or after a removal from the vault's position until its next add; what it has not sent back when the sale ends stays with it (the Terms, section 11, leave the send-back to the Safe's discretion).

Before adding, the vault checks the pool's current price against references that a push in the round's own transaction cannot move, and skips the round when they disagree:

• Once the vault holds a position of its own in the pool, it goes by the pool's average price over the last —. The current price must be within about — of that average, of the average over the last — and of the price at the start of the block. A price lifted in the round's own transaction is therefore refused, unless the move it undoes happened in that same block, which no pool price can see; a lift held across blocks right after a real move gets through only shortly after it, before the average over the last — has followed the move; and a price held long enough for the averages to follow it counts as the pool's price, within the band of the last point.
• While it holds no position of its own — before its first add, and after liquidity was removed from its position through the timelock, until its next add — it goes by the sale price (—) and checks only the current price against it, so a price lifted back near the sale price for that one round passes; that round therefore adds at most — of USDC. The rest is left for the next round, which may follow at once, even in the same transaction, and is checked as in the first point, with the same gaps: after a crash and a lift inside one block, which no pool price can see, that next round pairs the rest, so the cap bounds each such round, not what waits in the vault.
• Every price it checks — the current one, the averages and the price at the start of the block — must lie within about — of the sale price, up or down. While HKN trades further from the sale price than that, the vault waits.

These rules are fixed in the vault's verified code on Base, and nobody can change them. The Terms (section 11) state what is promised: the vault adds only under these rules, which can hold additions back, and what it holds idle goes only into the pool or to fixed destinations.

Liquidity can only be removed from the vault's position, and the trading fees it earns collected, through the timelock, announced on-chain at least — ahead (anyone may add liquidity to it, as to any Uniswap position). The sale page shows what the vault has added so far and what the pool holds now.

Liquidity additions end with the sale. The vault adds only while the sale is open; once the sale has been ended, or what is left is less than one minimum purchase, the vault never adds again, whatever happens later. The position already in the pool stays there unless the timelock removes liquidity from it: only the timelock can remove liquidity from it or collect its fees, by an operation announced on-chain at least — ahead, to the address the timelock names, and nothing locks the liquidity in the pool. What is left in the vault can only go to fixed destinations: its HKN to the timelock and its USDC and USDT to the issuer's Safe, by a timelock operation announced on-chain at least — ahead (USDT can also be forwarded to the Safe at any time). That operation opens only once the sale no longer sells: if the sale were paused and then never resumed or ended — for example because the issuer's Safe could no longer sign — the vault's idle USDC and HKN would stay in it for good. The sale page shows when the additions have ended.

Only the pool on the signed address list. It was created and set to the sale price on deployment day, before the start. HKN can be moved freely, so anyone can create other pools at any price; they are not the issuer's. The price in any pool is set by trading, including any trading by the issuer.

Yes, by the issuer's Safe, at any time; the power is meant for emergencies. While it is paused every transfer stops — wallets, pools, the sale and the timelock — except burning. Burning, and so conversion through the burn portal, is never stopped by a pause. Token scanners show “transfer pausable” on HKN for that reason, until the final freeze gives up the power for good.

The issuer plans to freeze HKN on Base for good 60–90 days after the mainnet launch (plan), on a date announced in advance; its Safe can freeze it at any time. One call pauses the token and gives up its ownership: from then on HKN on Base can only be burned, and only a burn through the burn portal converts it 1:1; nobody can undo it. Liquidity providers and trading venues must withdraw their HKN from pools and other contracts before the announced date: HKN left at the freeze in a pool, or in a contract that cannot call the burn portal, cannot be converted by its owner. The Terms say so from day one. Hold your HKN in a wallet whose keys you control before that date.

At native mainnet, the burn portal on Base lets you burn ERC-20 HKN and receive native HKN 1:1 on the HashKinetics network. There is no deadline. Native HKN uses smaller units than the ERC-20 (1,000,000 micro-HKN per HKN), so the amount you convert must be a whole number of micro-HKN; every amount the sale delivers already is. The burn portal is inert until the issuer activates it; 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. Conversion requires the identity verification at mainnet (section 3 of this page), which the burn portal does not check; a burn cannot be undone and a wrong native address cannot be corrected, so follow the issuer's published process before you burn. Only a burn through the burn portal counts: HKN burned with the token's own burn function is destroyed and converts nothing. Conversion depends on the issuer delivering mainnet; if mainnet is delayed, conversion is delayed with it, and if mainnet never launches, there is nothing to convert to.

• No refunds. Whatever happens after your purchase — the price, a delay of mainnet, a pause, the final freeze — your purchase is final.
• The token can be paused, or frozen for good, by the issuer's Safe at any time; a pause stops every transfer except burning, and the freeze makes HKN on Base conversion-only for good. HKN left at the freeze in a pool, or in a contract that cannot call the burn portal, cannot be converted.
• Smart-contract, key and operational risk in the token, the sale, the Liquidity Vault, the burn portal, the Safe and the timelock. The contracts' source is published and checkable from the signed address list; their review status is stated above.
• The sanctions oracle is run by one company; if it breaks, purchases stop until it answers again or the check is switched off.
• USDT on Base is a bridged token, not issued by Tether on Base; a bridge or peg problem can affect USDT payments, and the issuer's Safe can close USDT purchases.
• USDC is issued by Circle, which can pause it or block an address; that would stop USDC purchases while it lasts, with no remedy in the sale contract.
• One buyer may buy the whole round, and wallets funded by the issuer, including its liquidity bot's, may buy HKN in this sale and in any pool. The price in any pool can be below the sale price at any time, including right after the start; it can be moved by others, pools may be thin, and other pools at other prices may appear.
• Most HKN went to the issuer's timelock at deploy; the issuer can move it anywhere after the timelock's notice period, including into later sales at other prices and on other terms, and every such movement is announced on-chain first. HKN released from it, by a sale or otherwise, adds to the HKN in circulation and can lower the price.
• Identity verification at mainnet gates conversion: a holder who has not completed the issuer's published process cannot convert HKN on Base into native HKN until they do, at any later time; after the final freeze, a holder's HKN on Base can only become native HKN once they verify.
• Regulatory risk, including the laws where you live, which may not allow you to buy; the native chain's shielded-by-default design may limit where native HKN can be traded or serviced by supervised providers in some jurisdictions.
• Tax is your responsibility; the issuer gives no tax advice.
• Scams. Fake tokens, pools, sites and “support” messages will appear. Only the signed address list is authoritative.

No promise that HKN will trade anywhere, at any price or with any depth of liquidity; the price in any pool is set by trading, including any trading by the issuer. No price targets or predictions. No refunds. No rewards for inviting others, for posting about the sale, for buying first or for buying more. No offers of HKN by direct message, private deal or giveaway: the issuer sells HKN only through sale contracts named on the signed address list. No promise of when mainnet launches, or that it launches. No financial, legal or tax advice. If you see any of these attributed to HashKinetics, it is not from the issuer.

A Node Key is sold separately at nodes.hashkinetics.org. Holding one gives no priority, discount or HKN in this sale.

• The signed address list of this site: the only source of the token, sale, Liquidity Vault, pool and burn-portal addresses, verified in your browser against the Safe's on-chain signature and cross-checked against the sale contract.
• The Terms page: the Terms text, its fingerprint as computed by your browser, and the contract's.
• Basescan, Blockscout and Sourcify: the verified source of every contract, linked from each address on the signed list.
• hashkinetics.org for testnet-1 numbers (explorer, network map) and the source code on GitHub. Official channels are named there; anything else is not the issuer.
• The issuer's contact: hello@hashkinetics.org (also at the foot of every page).