Build on Qubic without rebuilding the basics. Glyph creates dependable wallets, libraries, and infrastructure as one coherent system.
Make Qubic easier to build on and safer to use. Available now Wallet, Connect, and Explorer cover local approval, application integration, and readable Qubic network data.
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 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 Glyph Explorer Live Qubic network data for identities, transactions, contracts, tokens, ticks, and the rich list.
Network statistics and live Qubic price Identity balances and activity Transactions, ticks, contracts, and tokens Explore Glyph Explorer Glyph Docs Guides and references for integrating with Glyph Wallet, Connect, and Relay.
Integration guides Protocol references Wallet and Relay documentation Explore Glyph Docs One system. Clear boundaries. Products are organized by the role they play, not presented as an undifferentiated suite.
User Hold, inspect, and act through user-controlled interfaces.
Application Express application intent through typed integration boundaries.
Developer Build with repeatable workflows and shared references.
Infrastructure Reach Qubic data and network integrations consistently.
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.
Application creates intent The dApp defines the requested action and its return path.
Connect builds the request Glyph Connect encodes a typed envelope for Glyph Wallet.
Wallet validates and explains Wallet checks the request boundary and presents the action for review.
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.
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 modelWhat comes next In-development and planned products are kept separate from the tools that are ready to use today.
Glyph SDK Coherent libraries for Qubic applications
In development
Glyph CLI Repeatable Qubic development workflows
Planned
Glyph Devkit Examples, templates, and development workflows
Planned
Glyph API Consistent access to Qubic data
Planned
Glyph Trade Transparent market interaction
PlannedBuilt in public, ready to use. Choose the path you need.