Skip to content

Sell a trading accountlike an NFT.

Your key is an NFT on NEAR. Behind it sits a private trading account inside a sealed enclave. Whoever holds the key controls the money. Sell the key and the account moves with it; the seller is refused on their next request.

Launch appTry it free — testnetWatch a real handover
NEARNEAR
USDCUSDC
ETHETH
SOLSOL
BTCBTC
ZECZEC
ARBARB
BaseBase
KEYHOLE Key #1

Reading NEAR mainnet · keyhole-devmo.near

Keys minted
…
Holders
…
Active liens
…
Latest key event
…

Proof, not promises.

Each number opens the place where you can check it.

Keys held by users
6
Worker code hash
ed0f614a
Checks in your browser
37
Public orders
6
Verify it yourselfVerification path, 5 min, no wallet

The handover, on NEAR mainnet.

One key, two holders. Each step is a real call or transaction, and its proof opens in one click.

  1. Allowed

    A withdraws from the vault.

    Holder A signs a withdraw. The enclave checks that A owns the key before it pays out.

    440c2378…Open proof
  2. Transferred

    The key moves to B.

    One NFT transfer on NEAR mainnet. The trading account goes with the key.

    G35r5pmC…Open on NEAR
  3. Refused

    A asks again, and is refused.

    The enclave reads the owner on every request. A no longer owns the key, so the call returns not_owner.

    e805f050…Open proof

Both wallets are team test wallets on mainnet. A payout already in flight when the sale lands still completes, to the holder who signed it.

Check a key before you buy it.

Anyone can read the enclave's signed statement for a key. Your browser checks each part, with no wallet.

Browse keys

A layout example, not a live result. Run a real check on /key. /key

Example from /key

PASS

The enclave signed this statement, and the holder still holds the key on chain.

  1. Signature valid

    ed25519 over the exact statement bytes, checked in your browser.

  2. Signer is the contract's minter

    Compared with the minter the contract reports on NEAR.

  3. Proof is for this key

    The token id in the statement is the key you are looking at.

  4. Holder read from chain

    The current holder, read from NEAR when you check.

  5. Signed

    When the enclave signed it, and how old that is.

  6. Log head

    The enclave's log head at the time of signing.

Trade anything, from anywhere.

Swaps route through NEAR Intents 1Click, across 230 tokens on 39 chains.

  • wNEARNEAR
  • USDCNEAR
  • USDTEthereum
  • ETHEthereum
  • wBTCNEAR
  • SOLSolana
  • ZECZcash
  • ARBArbitrum
  • USDCBase

The count is read from the 1Click token list each time this page renders, at most once a minute.

Open swapSee real settled and refunded orders

Private by design.

Balances and trade history stay sealed in the enclave. Here is what each side can see.

The enclave sees

  • Each key's custody wallet. It never leaves the enclave.
  • Balances, positions and trade history.
  • Every request, checked against the current owner.

Anyone else sees

  • The holder of each key and its token id, on NEAR.
  • Each attested call, its result and the worker build that ran it.
  • The swap pair and amount, to the 1Click solvers that route it.

Keys to the money never leave the enclave.

Verify a callTry to steal a keyAsk NEAR AI privately

Verify the live deployment in two minutes.

No account and no wallet. The script reads public sources and writes nothing.

git init keyhole && cd keyhole && git remote add origin https://github.com/mohamedwael201193/keyhole.git && git fetch --depth 1 origin 33bc30728866088ad7c4d70f4fe4ceeb5a77d216 && git checkout --detach FETCH_HEAD
run the claims checker (see the repo README)
open /verify
open /attack

Hold the key. Sell the account.

Get your keyRead the proof