I have read Abstract’s Bridging FAQ and understand that Abstract currently considers assets delivered to an AGW address on a non-ZK Stack chain unrecoverable.

I am NOT submitting this report simply to request redistribution or compensation. I am reporting a cross-chain transaction/guardrail failure that resulted in the exact condition Abstract states its guardrails are intended to prevent.

My Abstract Global Wallet:

0x135711F06B057C9c863949d04169E57d4fd8e137

On August 1, 2026, I initiated a cross-chain transaction from Abstract through Relay.

Abstract source transaction:

0x88dd9e4994f46271b418e7a20b55c64838fe4beeede314b5506205a599eabd1

Robinhood Chain destination transaction:

0xcbdb9240152a543544ee0de01ba400fce9230a53edc087bd4cd056e6362b2fa1

Approximately 38,512.585294818 HOODRAT was purchased on Robinhood Chain and delivered to the same numerical AGW address:

0x135711F06B057C9c863949d04169E57d4fd8e137

HOODRAT contract:

0x8e62F281f282686fCa6dCB39288069a93fC23F1c

The on-chain transaction trace shows the route through RobinHoodSettler, UniswapV2Pair, Relay Router, and finally my AGW address.

My concern is not whether Abstract currently supports recovery. My concern is why a cross-chain transaction was allowed to complete to an address that could not operate on the destination chain.

Expected behavior:

The transaction interface/provider should prevent or prominently reject use of an Abstract-only AGW address as the destination on an unsupported non-ZK chain before the transaction can be signed.

Actual behavior:

The cross-chain route successfully executed on Robinhood Chain and delivered the purchased tokens to my AGW numerical address, where they cannot be moved.

Please investigate:

Whether Abstract exposed my AGW address to Relay as the destination recipient.

Whether Abstract communicated programmatically that this address was Abstract-network-only.

What guardrail should have prevented this destination from being used.

Whether that guardrail was missing, failed, or was bypassed.

Whether a destination-chain incompatibility warning was displayed during this specific transaction.

Whether Abstract can coordinate with Relay regarding the original quote/request and recipient-selection behavior.

Whether any future account-abstraction or recovery mechanism could make assets at this address recoverable.

Relay support ticket:

#127982393

Abstract Discord support directed me to the official support system and subsequently closed my ticket under the non-ZK AGW policy. I am submitting this separately as a product/transaction bug.

Please preserve transaction, wallet-session, recipient-selection, integration, and routing metadata relating to this transaction.

I have screenshots of the complete on-chain transaction trace, token transfers, Relay response, balance, failed transactions, and Abstract support responses.