Alice · HNS seller
SENDS HNSAlice gives HNS on Handshake and receives the listed payment asset on its specified network. Alice may be either the offer creator or the person accepting it.
No active trades yet. Browse the alpha atomic swap order book or start a P2P trade.
Liquidity.spot helps an HNS seller and an HNS buyer find each other, agree on the details, and keep one shared trade record. It does not hold, send, or automatically exchange either person’s funds.
Know this first
You remain responsible for checking amounts, wallet addresses, transactions, and confirmations. Do not send anything just because an offer was accepted.
The two sides
It does not matter who posted the offer. The person selling HNS is always called Alice, and the person buying HNS is always called Bob. Every trade room also spells this out in plain language.
Alice gives HNS on Handshake and receives the listed payment asset on its specified network. Alice may be either the offer creator or the person accepting it.
Bob sends the listed payment asset and receives HNS on Handshake. “Bob” is a trade role here—it does not mean the Bob Wallet app.
Main product path
Follow the room in order. Its large green button changes to show the current shared next step.
Filter offers by payment asset and network. If none fit, choose Buy HNS or Sell HNS, select the payment route, and enter your amount and rate. Posting creates a public listing—it does not move funds.
Review the HNS amount, price per HNS, exact payment total, payment network, token contract, offer note, and any maker Gems bond. Accept only if your wallet supports that exact route. Network fees are additional.
Accepting fixes the amount, rate, asset and network for one shared room. At the top, check your role plus exactly what you send and receive. Acceptance does not transfer funds or bridge assets.
Most important step
Use room chat to confirm both receiving addresses, the payment network and contract, the exact transfer total, who sends first, and how many confirmations you will wait for. Human P2P does not force Alice or Bob to send first—the two parties must agree.
The room guides both parties through First transfer, Verify, and Other side. Add public TXIDs or confirmations to chat. Click the next-step button only after the described event really happened.
After both people independently verify that the expected HNS and payment asset arrived on the agreed networks, mark the trade complete. Then leave factual feedback and download a PDF or text receipt if you need a record.
Same ticker does not mean same route
ERC-20 is a token standard, not a network. Ethereum mainnet, Base and Optimism are separate networks. HNS in these trades stays on Handshake mainnet.
The same 0x address is not proof of the right network. Check the selected network in your wallet and, for tokens, the exact contract shown in the offer and room. Do not substitute a wrapped or bridged token with a similar name.
No automatic conversion: a USDT quote is an amount of USDT, not a guaranteed US-dollar value. No market rate is supplied for non-BTC routes; the maker sets the price. The transfer total is rounded to the token's precision, with gas paid separately.
No automatic bridging or escrow: only listed routes are supported. If you hold funds on a different network, do not send them to this trade as a substitute. Resolve the mismatch before accepting.
Inside the room
Confirm the full plan in chat.
One party sends as agreed.
The receiver checks it independently.
The remaining asset is sent.
Both parties verify settlement.
Milestones are a shared record, not blockchain verification. A button records what a participant says happened. Always confirm transactions yourself in the correct wallet or block explorer.
Before any transfer
Verify the HNS amount, rate, and exact payment total.
Confirm each receiving address in the wallet that generated it.
Match the payment network and exact token contract, not just the ticker.
Keep enough of the network gas asset to pay fees separately.
Agree who sends first and how many confirmations are required.
Send a small test amount first when appropriate.
Check TXIDs independently; do not trust a screenshot by itself.
Stop if the amount, address, or terms change unexpectedly.
Keep important confirmations in the shared room record.
Open a dispute before taking another irreversible step if something is wrong.
Never share a seed phrase, private key, wallet password, two-factor code, or Liquidity.spot guest recovery key.
Identity and reliability
Guests can browse, post, accept, and use trade rooms. Save the recovery key immediately if you want to return as the same guest from another browser.
GFAVIP login connects an account identity and account-linked features. It is optional for ordinary P2P trading.
An offer creator may lock optional Gems before the offer goes live. Gems are account points—not a payment asset or trade escrow.
Read the Gems guide →Common questions
The offer is still waiting for another person. Open its shareable page and send the permalink to someone who can take the opposite side. A room appears only after acceptance.
Read the “Your role,” “You send,” and “You receive” cards at the top of the room. Do not proceed until those three cards match your intention.
Do not send more funds. Write the facts in room chat, then use “Open a dispute” near the bottom of the room. Manual correction and no-show controls are also kept there.
If neither person sent funds or has a transfer in progress, open the room and use “Cancel before payment.” Confirm the statement only if it is true for both sides. Recorded payment activity blocks this option. Closing a website record never reverses a blockchain transfer.
Use the Guest Recovery option on the login page with the recovery key you saved. Liquidity.spot cannot reconstruct a lost recovery key.
The Atomic Swaps pages describe an HNS/BTC HTLC flow with hashes, timelocks, wallet scripts, and a fixed on-chain order. This is not the normal P2P room described above. Adding ETH, USDT or USDC payment routes does not add atomic-swap support for those assets.
Only in this experimental mode, Alice is the HNS seller who locks HNS first and Bob is the HNS buyer who locks BTC second:
Use testnet, simnet, regtest, or very small experimental amounts until the wallet-assisted path has been independently proven safe.
Browsing is public. You can inspect the available offers before deciding whether to participate.
Browse P2P offers