Bridge USDC to POA

1. Connect the Ethereum wallet holding your USDC. Enter the amount and the recipient’s POA address.
2. Approve USDC if needed. Approval gives the bridge permission to use that amount; it does not send it.
3. Select Transfer to POA and confirm the Ethereum transaction. The bridge contract locks the USDC while the transfer completes.
4. Track the transfer in Transfer history. USDC usually arrives on POA 12–15 minutes after Ethereum confirmation.

You need ETH on Ethereum for transaction fees. The current minimum and recovery window are shown under Contract details after connecting. Closing the page does not cancel a submitted transaction.

If the transfer is taking longer

Open the transfer page and the Ethereum transaction link. “Waiting for finality” means the bridge has observed the Ethereum transaction. “Waiting for USDC on POA” or “Waiting for mint” means the POA credit has not yet been confirmed by that view. A delay or an unavailable explorer does not prove that the transaction failed. Do not send the same transfer again without checking its status.

Recovering an unclaimed Ethereum transfer

The usual 12–15 minute wait is not the refund deadline. Recovery is possible only after the lock’s on-chain deadline and only if that Ethereum lock has not already been claimed or refunded.

1. Keep the Ethereum transaction hash, bridge contract address, sender, recipient, amount and transfer-page URL. From the transaction’s Locked event, save the hash (hashlock) and deadline. The hashlock is different from the transaction hash and the explorer’s transfer ID.
2. Check the POA transfer record, Ethereum receipt and current contract state. If POA already shows the completed credit, stop: this is not a failed transfer to refund. Inspect the proxy’s event history from the original lock through the latest Ethereum block. A confirmed Claimed or Refunded event with the same sender and hashlock means stop. Confirm the deadline has passed and the lock remains unclaimed and unrefunded. If the event history or current state cannot be verified, do not submit a refund. A missing POA explorer result alone is not sufficient.
3. The Ethereum bridge contract exposes refund(sender, hash). Use the same proxy contract that emitted the original Locked event and a verified contract interface (for example, Etherscan’s Write as Proxy when available). Enter the original sender and hashlock. No new USDC approval or secret preimage is needed; the caller pays the ETH transaction fee.
4. After confirmation, verify the Refunded event and USDC returned to the original Ethereum sender. The contract sends the refund to that sender, regardless of who submits the call.

The transfer form does not currently include a refund button. If you cannot verify the contract or lock state, resolve that before signing a recovery transaction. The contract’s isActive helper also becomes false after the deadline; do not use that value alone to decide whether a lock was already claimed.

Protocol details

The Ethereum HTLC locks USDC under a hash and deadline. After Ethereum finality the bridge records a bridge_lock on POA; settlement credits the intended recipient. An Ethereum claim releases the locked USDC to the configured claimer. The dApp does not receive the secret preimage.

Transfer USDC · Transfer history