grenadeandClaude Opus 5.5
52ac684661
ci / gate (push) Failing after 1m35s
The intents panel now moves QTC across the PoA bridge (#75). In: the bridge's permanent Quantus deposit address for the account, checked as a Quantus address before it is shown. "Send QTC here" opens Send with it filled in (Send takes ?to= now), so a deposit is an ordinary transfer reviewed and signed like any other. Out: a withdrawal to one of the wallet's own Quantus accounts. It is the ft_withdraw #72 proved, qtc.omft.near to itself with the WITHDRAW_TO: memo: - qtc_withdraw_call in wallet-core builds it and refuses anything under the bridge's 0.01 QTC minimum. - The command checks the Intents balance and the sponsor's terms, signs a delegate action with the phrase's NEAR key (nonce one past the key's, valid for about 120 blocks), and hands it to the sponsor, which relays it and pays the gas. - The bridge keeps 0.002 QTC, and the panel says so. NearRpc::final_block now returns the height with the hash, for the delegate's expiry. QtcBridge is the new port and PoaBridge its adapter. Checked in a dev run with the dev-phrase account: - the deposit address appeared (qzkgR6o1…); - Send opened with it filled in; - a 0.05 QTC withdrawal was refused because the account holds no QTC. A live test (ignored) confirms the bridge gives #72's account the address it used on mainnet. A full round trip with real QTC is still to do before #75 closes. Refs #75 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NUx7SPonBnB3ofU4mH41WT