Partner

EVE

Alpha Trust EVE converts a Yap Signer send into scan, scrape, bid, and merch credits. The ledger stays on EVE. Signer only authorizes the transfer.

Where EVE lives

Live app: https://eve-backup.onrender.com. Product EVE, operated by Alpha Trust. Credits UI: /crypto-credits. Company treasury username on Yap: @alphatrustwallet.

Frictionless path

Sign in to EVE as the agent.
Create a deposit on /crypto-credits (treasury address + memo).
Yap Signer sends the asset to that treasury (manual review, or silent pullTransfer when allowlisted and armed).
EVE confirms the deposit and mints scan/scrape/bid/merch credits.
Start the SEO/GEO scan or scrape from the EVE desk.

EVE holds the credit ledger. Yap Signer only authorizes the send. Keys stay on the device.
Yap referral install credits on yap-pay.xyz are not EVE scan credits.
Silent pullTransfer still needs a live yap_pat_ token, a fresh nonce, and this origin on the extension allowlist.

Allowlist

Silent and platform transfers only run on allowlisted origins. This site lists https://eve-backup.onrender.com on the public allowlist used by the interactive lab. The Chrome extension package must include the same hostname before pullTransfer works without leaving the EVE tab for a manual send.

Bridge from EVE

From https://eve-backup.onrender.com, the page talks to Yap Signer with the same envelopes as Messages: ping, getStatus, then pullTransfer after a deposit exists.

// 1) Public status
{
  source: "yap-app",
  type: "YAP_SIGNER_REQUEST",
  requestId: "<uuid>",
  method: "getStatus",
  payload: {}
}

// 2) After EVE creates /api/me/crypto/deposit → treasury + amount
{
  source: "yap-app",
  type: "YAP_SIGNER_REQUEST",
  requestId: "<uuid>",
  method: "pullTransfer",
  payload: {
    accessToken: "yap_pat_…",
    nonce: "<32 hex chars>",
    networkId: "solana",
    asset: "usdc",
    destination: "<EVE treasury address>",
    amount: "25"
  }
}

networkId values Signer accepts: bitcoin, ethereum, bnb, base, arbitrum, optimism, robinhood, hyperevm, solana. asset is native or usdc. EVE’s accepted labels today: BTC, ETH, SOL, USDC. Map SOL → solana + native, USDC on Solana → solana + usdc, ETH → ethereum + native, and so on. The page never passes raw transaction bytes.

After the send

EVE credits scan, scrape, bid, merch once the deposit is confirmed. Those balances start SEO and GEO scans and scrapes inside EVE. They are not the referral install credits on yap-pay.xyz.

Kept off both origins

No seed, vault password, or private key in EVE or on yap-pay.xyz.
No server-side signing. Signer builds and signs the transfer on the device.
EVE may show treasury and memo instructions; confirmation belongs to EVE’s deposit watcher or operator.

EVE