Glyph ecosystem

Software organized by responsibility.

The product family connects application intent, developer workflows, infrastructure, and user-controlled approval.

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.

How a dApp reaches Wallet

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.

Current and future architecture

Available products work today. In-development and planned products describe the intended system without implying availability.