glyph.
GitHub (opens in a new tab)Get Wallet

Glyph / developers

Build with a maintained path

The current integration path is direct: create a typed request, open Glyph Wallet, handle approval or rejection, then continue your application flow.

01

Start with Connect

Install the current MIT-licensed package from npm. It is framework-agnostic, fully typed, and has no runtime dependencies.

  • bun add @glyph-oss/connect
  • Create a request and envelope
  • Launch the glyph:// URL
  • Handle signed, connected, or rejected results
02

Failures are part of the contract

Applications should treat rejection, expiry, invalid callbacks, and unavailable desktop handling as expected outcomes, not exceptional UI states.

03

The wider stack

SDK, CLI, Devkit, API, and shared Docs are in development or planned. They are not required to use Connect today.

01
dApp

Application creates intent

The dApp defines the requested action and its return path.

02
Glyph Connect

Connect builds the request

Glyph Connect encodes a typed envelope for Glyph Wallet.

03
Glyph Wallet

Wallet validates and explains

Wallet checks the request boundary and presents the action for review.

04
Local approval

User makes the decision

Approval signs locally. Rejection returns an explicit result.

A typed request moves from application intent to a decision inside Glyph Wallet. Keys never cross into the application.
npm install @glyph-oss/connect