Integration fixture / NEAR Intents
This walkthrough separates user-triggered live provider calls from deterministic local evidence. Pilot transaction signing and broadcast remain disabled; external owner manual funding is exposed only after a durable reservation.
Provider-connected · read only
Pilot calls the same-origin Harbor proxy. Credentials remain server-side; execution, deposits, and signing remain unavailable.
Not checked. Configure the live Harbor service and, when required, its server-side 1Click partner key; then use the button above.
Live executable review · manual owner funding only
This fixed route can request a provider-verified review through Harbor. Pilot never builds, signs, broadcasts, or funds the owner transfer.
Executable review disabled
The public UI capability is off. No executable quote or status request can be made from this panel.
Live owner-control and economic approval
The live route below requires the default-off browser-wallet, executable-review, principal-bootstrap, and owner-approval gates plus an active Pilot wallet session. Every server gate remains independently authoritative.
Live owner-controlled route · default off
Bootstrap the server principal, request a provider-verified quote, prove control of the exact source account, and separately approve a durable reservation. Pilot never signs or broadcasts a transfer.
Browser wallet adapter: disabled. The browser NEAR wallet adapter is disabled. No wallet prompt can open.
Live native-route flow disabled
All four public gates and an active Pilot wallet session are required. No principal bootstrap, executable quote, wallet prompt, proof, approval, reservation, funding instruction, or status request can start from this panel.
Separate local owner-control fixture
The review below models the chosen native-NEAR funding route without opening a wallet or requesting a live executable quote.
Owner-controlled route · default off
Review the source-account proof and the separate quote-bound economic approval before any manual native-NEAR transfer. This local demo does not request a quote or open a wallet.
Browser wallet adapter: disabled. The browser NEAR wallet adapter is disabled. No wallet prompt can open.
Fixture provenance: the exact digest and bindings below use deterministic local data. No provider signature, NEP-413 wallet proof, owner confirmation, reservation, or transfer occurred on this page.
Step 01 · source-account control
The nonce, recipient, expiry, principal, account, and network are one proof scope. This signature proves source-account control only; it does not approve or transfer NEAR.
Step 02 · distinct economic approval
A fresh wallet-control proof is necessary but insufficient. Owner confirmation must separately bind every economic field and expire before the provider refund-start deadline.
B6059AE4AF7E782350DC7DBA6CC1ECAAFCEFC466CEC3ED2FB75575203CAFBC60
Step 03 · manual owner funding
Only after separate acceptance gates pass, the owner wallet—not Pilot—would manually send native NEAR to the exact provider deposit account.
Funding remains blocked until independent source and destination receipt verification is accepted. The signed NEP-413 message does not transfer funds, and Pilot budgets cannot stop an owner from sending outside the app.
Separate local evidence
The walkthrough below never replaces the provider-connected result above. Use it only to inspect Pilot's disabled executable-review, manual owner-funding, reconciliation, and evidence boundaries.
Local fixture · no provider or wallet calls
Inspect the only executable-shaped route in this fixture. Every value is deterministic local data; nothing below is a current quote, wallet instruction, transaction, or settlement claim.
Fixture provenance: this walkthrough models a provider-signature-verified executable quote, but this page did not request or verify one. Real funding requires a fresh provider response and a fresh owner review.
Stage 01
Fixture transcript only. It demonstrates the fields Pilot must obtain from a provider-signature-verified executable response.
Fixture provenanceStage 02
A dry quote is preview evidence only. It cannot be upgraded, reused, or treated as approval for this executable-shaped fixture.
Fresh approval requiredStage 03
The owner—not Pilot—is the transaction actor. These exact fixture fields are shown for review and are not a request to transfer funds.
Owner action · disabledPilot does not build, sign, or send this transfer. Pilot budgets can block Pilot-mediated actions, but cannot stop an owner from transferring outside the app. Manual funding remains blocked until recipient wNEAR token-storage registration is independently confirmed.
Stage 04
An owner-reported hash is bound to this principal, quote, deposit address, and amount before status tracking. Reporting is not chain confirmation.
Local owner reportStage 05
Status must be queried against the exact provider tracking identity. This sequence is illustrative and was not observed live.
Illustrative progressionStage 06
Missing or contradictory evidence becomes UNKNOWN, not failed and not safe to retry. Funding again remains blocked while reconciliation is incomplete.
Reconciliation requiredStage 07
Provider SUCCESS is a provider claim. Destination delivery requires separate NEAR-chain evidence for the exact recipient, token storage, and asset.
Evidence not collected