OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Wallets

Frame

Frame is a desktop Web3 wallet interface for managing chain accounts and connecting them to browsers, command-line tools, and native applications through local JSON-RPC endpoints or a companion browser extension.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Frame — OpenViST project profile in Wallets.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Frame when you want a desktop wallet connection shared across browser, command-line, or native applications, or when you need its documented hardware signer support and local provider interface.

Who it is for

  • People who want desktop-managed crypto accounts available to multiple applications.
  • Users of GridPlus, Ledger, or Trezor hardware signers.
  • Developers connecting native applications to a local Ethereum JSON-RPC provider.
  • Web app users whose app lacks a native Frame connection option.

Documented uses

  • Connect applications to accounts managed through Frame.
  • Use hardware or software signers with dapps.
  • Control dapp permissions and monitor network requests.
  • Review decoded transaction calldata when verified contract ABIs are available.
  • Route dapp use across multiple chains.
Before you choose

Requirements & limits

  • Frame documents macOS, Windows, and Linux support.
  • Its connection methods are a local JSON-RPC endpoint and a separate browser extension that injects an EIP-1193 provider.
  • Software account options include mnemonic phrases, keystore files, and standalone private keys.
  • The repository identifies the project as open source under GPL-3.0.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Connect a native application to Frame

Configure an application to connect to Frame through its local JSON-RPC endpoint.

Before you start

  • Frame running on the same system as the application.
  • An application capable of connecting to a JSON-RPC endpoint.

Steps

  1. Use the WebSocket endpoint ws://127.0.0.1:1248 or the HTTP endpoint http://127.0.0.1:1248 in the application.

  2. For an Ethereum provider connection, the project recommends eth-provider and documents the connection form ethProvider('frame').

Expected outcome

The application can connect to Frame through its system-wide JSON-RPC interface.

Guide limitations

  • The guidance describes the connection endpoint and provider option, not application-specific configuration or transaction execution.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for Wallet connections

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
FrameConnect applications to accounts managed through Frame.Browser Extension, Linux, macOS, Windows
ShangoConnect a mobile wallet to a personal LND node.Android, iOS, MobileThe README lists iOS TestFlight and Google Play beta installation routes and describes the app as a public beta. Its cloud-node instructions are for testnet.
Walletconnect Expo ExampleStudy or prototype a wallet connection and authentication screen in a React Native dapp.Android, iOS
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
14 October 2026
Original website title
floating/frame · Official homepage title · retained in its source language
How we review sourcesSuggest a correction