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

Independent software built for Qubic.

Build on Qubic without rebuilding the basics.

Glyph creates dependable wallets, libraries, and infrastructure as one coherent system.

Explore the ecosystemStart buildingGet Glyph Wallet

Mission

Make Qubic easier to build on
and safer to use.

Available now

Two current products establish the working path between Qubic applications and local user approval.

Available

Glyph Wallet

A desktop wallet that keeps encrypted vault data on your device and reviews every signing request before approval.

  • Send, receive, burn, and stake
  • Encrypted vaults with AES-256-GCM and Argon2
  • Local signing boundary in the native application
Explore Glyph Wallet
Available

Glyph Connect

A framework-agnostic TypeScript package for creating Glyph Wallet requests and handling approval, rejection, callback, and redirect results.

  • Transfer requests
  • Smart-contract call requests
  • Message signing and verification
Explore Glyph Connect

One system. Clear boundaries.

Products are organized by the role they play, not presented as an undifferentiated suite.

System architecture

Four layers. One maintained path.

The product family is arranged by responsibility, from user control to network access.
01

User

Hold, inspect, and act through user-controlled interfaces.

  • WalletAvailable
  • ExplorerIn development
  • TradePlanned
02

Application

Express application intent through typed integration boundaries.

  • ConnectAvailable
  • SDKIn development
03

Developer

Build with repeatable workflows and shared references.

  • CLIPlanned
  • DevkitPlanned
  • DocsIn development
04

Infrastructure

Reach Qubic data and network integrations consistently.

  • APIPlanned
  • Qubic integrationsNetwork boundary
Availability and license status remain explicit on each product page.

From application intent to user approval

Connect creates a typed request. Wallet validates it, displays it, and returns an explicit result.

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.
bun add @glyph-oss/connectPackage (opens in a new tab)

Local control

The signing boundary stays in the wallet.

Vault data is encrypted before disk storage. Signing requests pass through the desktop application for review. Glyph Connect never receives private keys.

Read the security model

The planned system

Future products are included to show direction. Their status is not hidden behind promotional language.

11

Glyph Explorer

A legible view of Qubic network activity

In development
06

Glyph SDK

Coherent libraries for Qubic applications

In development
06

Glyph CLI

Repeatable Qubic development workflows

Planned
09

Glyph Devkit

Examples, templates, and development workflows

Planned
06

Glyph API

Consistent access to Qubic data

Planned
07

Glyph Docs

One documentation system for Glyph products

In development
08

Glyph Trade

Transparent market interaction

Planned

Maintained in public,
licensed product by product.

Connect is open source under MIT. Wallet is source available. Planned products will publish a license when their implementation is released.

Review repositories and licenses

Clear interfaces. Local control. Predictable tools.

Choose the path you need.

Start buildingGet Glyph Wallet