Skip to content

warthog_extension 1.2.14

Latest

Choose a tag to compare

@github-actions github-actions released this 26 Oct 21:08

The recovery phrase and the Warthog private key stay in the signing worker. A send asks that worker for a signature. The page does not keep the key.

Security

  • The session token is a random id. The wallet password is not written to extension storage. A token that still contained the password is replaced when the extension starts.
  • Showing the recovery phrase or private key asks for the password or passkey again. The revealed value hides after 30 seconds.
  • A website can request accounts and submit a transaction. It cannot approve, reject, list connections, or open the wallet window.
  • SafeTrade API secrets are sealed. The key stays in the browser and a script cannot export it.

Sends and nodes

  • Warthog sends use the same 0.01 WART default fee as the rest of the wallet.
  • Transaction links open on https://wartscan.io unless the build sets VITE_APP_EXPLORER_URL.
  • A node on plain HTTP is labeled on the home screen and in the node list.

Also

  • Ethereum, Bitcoin, and Solana signatures are produced in the same worker when a recovery phrase is present. A private-key import with no phrase still cannot sign those chains. Ledger signing is unchanged.
  • Removed the unused deBridge path and the old background copy the build no longer loads.