NEAR competition

Unstoppable DeFi

What cross-chain transfer can a judge verify?

How .x3 fits

An .x3 program specified a Base Sepolia to NEAR testnet transfer. Its source hash was registered on Guard before the source transfer.

The historical transfer program

intent x3_testnet_base_usdc_to_near {
    from BaseSepolia.USDC amount 1000000 receiver 0x5aF0c1BF95B3A158f6Fc48e3DED35903b2fa0721
    to Near.USDC receiver x3lang.testnet
    route {
        bridge NearIntents BaseSepolia.USDC -> Near.USDC min_receive 980000;
    }
    require slippage <= 1%
    require nonce unused x3_base_testnet_trade_001
    timeout 30m refund BaseSepolia.USDC to 0x5aF0c1BF95B3A158f6Fc48e3DED35903b2fa0721
    on_fail rollback
}

Amounts use token base units. These accounts are example or historical testnet identities; use the source guide before adapting a program.

What the evidence establishes

Published result

1.000000 test USDC sent from Base Sepolia; 0.997400 test USDC received on NEAR testnet through the trusted Tidepool relay.

Trust and limits

This is historical trusted-relay testnet delivery. Official funded 1Click mainnet settlement and cryptographic cross-chain atomicity are not established.

Judge walkthrough

  1. Read the mandate and payment source. Identify recipient, asset, amount, nonce, deadline and refund terms.
  2. Run the local policy preview. Change the recipient to attacker.near and inspect the refusal; local results do not prove chain execution.
  3. Open the archived testnet records. Match the source hash, contract, transaction and network to the claim being checked.
  4. For delivery, inspect the source and destination finalized records and the relay assumptions separately from Guard authorization.

Full judge guide