Hartii developer docs
/

HartiiSwap

Hartii.org exchange

The native workspace puts swaps and liquidity on Hartii.org itself, reached through the home page's Swap door. It uses a constant-product pool model with explicit wallet reviews. A pool has two ERC-20 assets; native QUAI is wrapped or unwrapped through WQUAI when the selected action calls for it. QUAI and WQUAI are distinct balances. WQI is an ERC-20 called Wrapped Qi; trading it is not native Qi conversion or a guarantee about its backing or redemption.

Supported assets and liquidity

The curated assets include QUAI, WQUAI, WQI, HBOME and QAXE. A token can be supported by the client while having no liquid route in the selected factory. A mainnet read on 15 October found no WQI/WQUAI, HBOME/WQUAI or HBOME/WQI pair in the existing HartiiSwap factory. That snapshot is not a permanent availability promise: quote the current factory before trading.

An explicit token import reads a user-supplied contract address and displays its metadata. Metadata is untrusted text, not proof of legitimacy. Only supported account-ledger addresses and standard ERC-20 behavior are in scope. Fee-on-transfer, rebasing, malformed-return and other unusual token behavior is not advertised as supported. An address or ticker alone never proves provenance, liquidity or backing.

Review and wallet actions

  1. Choose the assets and an exact amount to pay or receive. Read the available route and the quote's age.
  2. Read the slippage limit. Exact input fixes the payment amount and sets a minimum received; exact output fixes the requested receipt amount and sets a maximum spend. Quotes can become stale.
  3. If an allowance is required, review an exact approval separately. A token that needs a reset may first require a zero-allowance transaction. Each is a separate wallet action; there is no automatic approval-and-swap sequence.
  4. After approval confirms, request a fresh quote. Review the amounts, account, network, pool generation, spender, expiry and maximum gas before confirming the swap.
  5. The wallet signs the transaction. A returned hash means pending, not successful. Only a final status1 receipt is confirmed; status0 is a revert. An uncertain outcome remains unresolved until recovery checks the original transaction.

The read provider supplies the gas estimate and zone-specific gas price; the wallet is used for signing. The wallet's active chain and account are checked immediately before sending. Browser requests omit chainId for supported wallet compatibility, while checking actual mainnet chain9. An expired or changed review needs a new review, rather than silently changing the authorized terms.

Native Max is unavailable when the exact transaction's gas reserve cannot be established. A dash is an unknown value, not zero fees or zero risk.

Fees

Each pool hop charges 0.30% of its input. A multi-hop route pays that fee in each hop. Most fee growth accrues to liquidity providers; when enabled, the protocol receives one-sixth of fee growth as newly minted LP tokens on a later liquidity event. This is not a second flat swap charge or an immediate transfer on every trade. See Liquidity for the formula and dilution.

Network gas is separate. Approvals, swaps, liquidity changes and failed transactions may each consume gas. A maximum displayed for one action does not include an unsubmitted later action.

Liquidity and optional migration

Pool and position lists are bounded pages with continuation controls. They identify the pool generation and token contracts. The LP token represents a share of current reserves; that share is not an exact historical earned-fee statement. Missing fee history remains unknown. Returns are not guaranteed and token prices can change.

Adding to a new pool sets its starting ratio and needs explicit review. The structural minimum-liquidity seed is retained; it is not an optional user lock. Removing liquidity applies rounded minimum amounts. Depositing or receiving native QUAI is an explicit choice for a WQUAI pool leg, rather than an assumption based on the token address.

For an addition, the quoted inputs describe the current pool ratio. The final confirmation also shows both maximum deposit amounts, which are the desired-input caps encoded in the router call, alongside the minimums. A changed ratio can use more than the initial quote while remaining within those explicitly reviewed maxima.

Old pools remain accessible. Migration is opt-in: remove from the old pool to your wallet, inspect what arrived, then separately authorize adding to a new pool. Prices and gas can change between those transactions. There is no automatic move, company-funded deposit or guaranteed ratio.

Pool generations and later features

The current deployment is identified as generation1 in the browser client. That label is separate from the general term Uniswap V2, which describes the market model. The generation2 successor source is a separate candidate. It must pass local invariant tests, review and Orchard rehearsal, then a concrete deployment decision; no successor address is claimed by this page.

Limit orders and recurring buys follow the reviewed core in later stages. This page does not claim an active order executor, scheduled fill, guaranteed execution, new farm or automatic trading service.

Privacy and recovery

The page makes public-chain and token-service reads, including queried public account and contract addresses. The services handling those requests see network information. Connecting a wallet requires a user action; the site never takes custody of a private key. Transactions and approvals are public on-chain.

Unresolved transaction metadata is retained on the device for recovery across reloads. Activity displayed in the current tab is separate from that durable recovery check. Do not clear an unresolved record and send again before checking the original outcome. Read the Hartii.org privacy notice for the final storage details. Browser tests and mock receipts do not establish a real wallet transfer or a deployed contract.

Quai Network mainnet · chain 9 · Cyprus-1. Figures marked "read on" a date were read from the chain that day; re-read before relying on them.