bug: domain purchase transaction reverted during wallet simulation

[Al629176]

Summary

When attempting to buy a domain, the wallet signing request shows "This transaction was reverted during simulation. An unknown error occurred." The Confirm button is disabled and the purchase cannot be completed.

Environment

• Origin: staging.tiny.place
• Network: Solana Mainnet
• Wallet: Account 3

Steps to Reproduce

1. Find a domain listed for sale
2. Click Buy
3. Wallet signing request appears
4. Wallet simulation runs and immediately shows the revert warning
5. Estimated changes shows "Not available"
6. Confirm button is greyed out — transaction cannot proceed

Expected Behavior

The wallet simulation succeeds, estimated changes are shown, and the user can confirm the transaction to purchase the domain.

Actual Behavior

The wallet shows:

⚠️ "This transaction was reverted during simulation. An unknown error occurred."

• Estimated changes: Not available
• Confirm button is disabled
• Transaction cannot be completed

Transaction Details (from screenshot)

Field	Value
Request from	staging.tiny.place
Account	Account 3
Recipient	7t7R8Kh...cIVqQ
Network	Solana Mainnet
Network fee	0.00001 SOL

Possible Causes

• Smart contract / program instruction is malformed or using incorrect account addresses
• Recipient address (7t7R8Kh...cIVqQ) is incorrect or not a valid program-owned account
• Insufficient funds or missing USDC token account for the buyer
• Transaction is being built against the wrong program ID (staging vs mainnet mismatch)
• Domain is already sold or the listing has changed state since the Buy button was clicked

Impact

Domain purchases are completely blocked — users cannot complete any buy transaction on staging.

[graycyrus]

@Al629176 "Reverted during simulation" is an on-chain failure — the Solana transaction the wallet is being asked to sign fails simulation against current program/account state. That's transaction-construction + on-chain program territory (escrow / x402 settlement), not a client display bug. This needs chain-level debugging (the failing instruction + simulation logs) with the backend/contracts owners — the web app only relays the tx the facilitator/program builds. Please route to backend/contracts; if you can capture the simulation logs (the failing program + error code) that'll pinpoint it fast.