NEAR

Check it yourself

Run our three Python scripts and watch the NEAR checks Hermit does pass on your own computer. No keys, no funds, a few minutes.

Hermit is an iPhone and Mac app, so we wrote three Python scripts that do what its NEAR code does, step by step, against the live services. You don’t need the app, a key or any money for steps 1 to 7. Prices and balances move, so your numbers won’t match ours exactly. The words should.

Script	What it does
`intents-quote.py`	Asks 1Click for a dry quote and checks its signature the way the app does.
`near-account.py`	Works out the NEAR account from a public test phrase and reads its balances.
`verify-attestation.py`	Fetches NEAR AI Cloud’s attestation with a fresh nonce and checks it like the app, plus Intel’s TCB status.

Set up

You need Python 3.10 or later, and 3.12 for steps 7 and 8. Check with python3 --version. On a Mac with an older one, run brew install [email protected] and type python3.12 wherever it says python3 below.

git clone https://github.com/Hermit-Ai-Labs/hermit-app && cd hermit-app
python3 -m venv .venv && .venv/bin/pip install -r near/requirements.txt

Run everything from the repository root. We ran these steps in a fresh clone on 2026-11-11 and got what the See column says.

Run the checks

.venv/bin/python near/intents-quote.py

See

A live dry quote for 10 USDC on Base to wNEAR: amount out, minimum out, 1Click fee 20 bps, a time estimate (35 s for us), deposit address none (dry quote: nothing can be sent) and [PASS] 1Click signature by ed25519:reYaWhvw.... Exit code 0.

.venv/bin/python near/intents-quote.py --selftest

See

Eight [PASS] lines, then 8 passed, 0 failed. The signature code gets the same hashes as the app’s Swift tests, and it rejects a quote whose deposit address was swapped.

.venv/bin/python near/intents-quote.py --from ETH:arbitrum --to BTC:bitcoin --amount 0.01

See

[FAIL] 1Click signature, a note, and exit code 1. That’s expected. Quotes with Bitcoin don’t verify with 1Click’s own SDK either, which is why the app warns about them.

.venv/bin/python near/near-account.py

See

From the public test phrase (abandon eleven times, then about): path m/44'/397'/0', public key ed25519:6j4b6zUa..., implicit account 5510e2b4...ee412, and three [PASS] lines against the app’s test vector. Then that account’s NEAR, USDC, USDT and wNEAR balances from mainnet, read-only.

.venv/bin/python near/verify-attestation.py

See

A fresh nonce, then NEAR AI Cloud’s live report for Qwen/Qwen3.8-27B with one [PASS] per check: the Intel TDX quote, Intel DCAP with TCB UpToDate, the nonce, the signer, MRCONFIGID, RTMR3, the TLS key, the GPU evidence and NVIDIA’s verdict. It ends 23 passed, 0 failed, 1 skipped. The skip is the reply signature, which needs a key.

F=Packages/HermitKit/Tests/HermitCloudTests/Fixtures; .venv/bin/python near/verify-attestation.py --report $F/qwen-report.json --nonce "$(cat $F/qwen-report.nonce)" --offline

See

The recorded report our Swift tests use, checked offline: 17 passed, 0 failed, 4 skipped.

Do · Python 3.12

.venv/bin/pip install -r near/requirements-sdk.txt
.venv/bin/python near/verify-attestation.py --sdk

See

The same checks, plus NEAR’s own nearai-inference-sdk running verify(model): 25 passed, 0 failed, 1 skipped.

Do · Python 3.12, needs a key

NEARAI_API_KEY=... .venv/bin/python near/verify-attestation.py --sdk

See

Also one short completion on the attested connection and the enclave’s signature over it. Our run ended 29 passed, 0 failed, 0 skipped. Get a key at cloud.near.ai, or $10 of credit at nearbuilders.org/dashboard.

More to try

Both of these end in [PASS]:

.venv/bin/python near/intents-quote.py --from ETH:arbitrum --to USDC:solana --amount 0.01
.venv/bin/python near/intents-quote.py --from NEAR:near --to USDC:hyperliquid --amount 5

near-account.py --account near reads any account you name.

Our saved runs

These are the full outputs from our runs on 2026-11-08, so you can compare line by line.

What each check means:

Steps 1 to 3: NEAR Intents
Step 4: Your NEAR account
Steps 5 to 8: The Private Cloud proof

The app’s own Swift tests need a Mac with Xcode. They’re on Run the tests.