Page bridge

Messages

Every bridge message stays in the browser. The page posts to its own origin and ignores anything from another origin.

Page to extension

Source yap-app. Type YAP_SIGNER_REQUEST. The methods a page sends are ping and getStatus. The payload is empty.

{
  source: "yap-app",
  type: "YAP_SIGNER_REQUEST",
  requestId: "<uuid>",
  method: "getStatus",
  payload: {}
}

Extension ready

Signer can announce itself with source yap-signer-extension and type YAP_SIGNER_READY. The page treats that as installed, then asks for ping and getStatus.

Extension reply

A reply uses the same source and the same requestId. The page reads payload, then result. Public fields it uses are installed, accountCreated, hasWallet, unlocked, username, and publicKey. It also accepts silentMode and tokenFresh.

{
  source: "yap-signer-extension",
  type: "YAP_SIGNER_STATUS",
  requestId: "<same id>",
  installed: true,
  accountCreated: true,
  hasWallet: true,
  unlocked: true,
  username: "swift-fox-ab12",
  publicKey: "<public address>"
}

Stopped at the extension

Create, restore, unlock, sign, and send stay inside the extension popup. This site never puts a seed, vault password, or private key in a message.