Guides

These guides use the released v2 contract implemented by @glyph-oss/connect 4.0.1, Relay v2, and Glyph Wallet 0.16.5.

Start with Understand Glyph Connect and Relay v2 for the roles, lifecycle, delivery choices, and signed binding model.

Integration path

1. Launch a request with a typed builder and a v2 envelope.
2. Use Relay v2 when the dApp needs a read channel instead of a direct callback route.
3. Verify callbacks with strict bindings and @qubic.org/crypto@1.0.0.
4. Handle results with discriminated TypeScript narrowing.
5. Understand the protocol before persisting or forwarding request data.
6. Troubleshoot rejections using the SDK and relay error boundaries.

The examples use placeholder identities and trusted callback-key configuration. The dApp verifies signed callbacks with @qubic.org/crypto; Glyph Wallet performs request signing after user approval. Do not accept a result before the verification step required by your delivery path, and do not put private keys in browser examples.