Open-source tools for building and using Qubic.
Website · Docs · Explorer · Starter
Glyph is an independent Qubic-focused organization. We build practical software for users and developers: a desktop wallet, a signed dApp connection stack, developer documentation, and a network explorer.
| Project | Purpose | Links |
|---|---|---|
| Glyph Wallet | A native desktop wallet for Windows, macOS, and Linux. It keeps vault data local, supports Qubic accounts and requests from compatible apps. | Repository · Download |
| Connect | A typed TypeScript SDK for Qubic dApps to request connections, signatures, transfers, and smart-contract calls from Glyph Wallet. | Repository · npm |
| Relay | The capability-based transport used by Connect and Wallet for signed request results. | Repository |
| Explorer | A data-first view of the Qubic network, identities, ticks, transactions, tokens, contracts, and rich list. | Repository · Open Explorer |
| Docs | Integration guides, protocol reference, API documentation, and release notes. | Repository · Read Docs |
| Starter | A compact reference dApp showing Connect, signed messages, and a Qubic smart-contract request. | Repository · Open Starter |
graph LR
App["Qubic dApp"] --> Connect["Connect SDK"]
Connect --> Relay["Glyph Relay"]
Connect --> Wallet["Glyph Wallet"]
Wallet -->|signed result| Relay
Relay --> Connect
Connect --> App
A dApp builds a typed request. Glyph Wallet presents it for the user to approve or reject locally. The dApp receives a signed, bound result that it must verify before acting on it. The Relay transports results, while the request and result checks remain in the application and wallet.
- Using Qubic? Download Glyph Wallet.
- Building a dApp? Begin with the Connect overview and the Starter.
- Exploring the network? Visit Glyph Explorer.
- Contributing? Read the repository-specific contribution and security guidance before opening an issue or pull request.
- Qubic-native. Clear request types, mainnet binding, and Qubic-focused developer tools.
- Local user approval. Wallet actions are reviewed and approved in the desktop application.
- Verifiable results. Integrations validate request and callback bindings instead of trusting a transport response alone.
- Open development. Source, issues, and release work happen in the open. License terms are defined by each repository.
Please use the security policy for responsible vulnerability reporting. Do not include secrets, seed phrases, private keys, session capabilities, or signed callback payloads in public issues.
