A map of the Zond developer stack
Get oriented across clients, browser wallets, and the example dApp before choosing where to contribute.
The QRL organisation contains more than one generation of tooling. When exploring Zond, keep its client and wallet integrations separate from QRL v1 assumptions.
Read across the stack
These repositories provide useful entry points:
- go-qrl for client-side source and its setup documentation.
- qrysm for another part of the Zond client stack.
- qrl-web3-wallet for the Zond browser extension.
- zond-web3-wallet-dapp-example for an example of connecting a dApp to the wallet using EIP-6963.
Choose one boundary
For a first contribution, pick a small boundary: a client configuration explanation, a wallet connection state, or an error message in an example application. Read the repository’s contribution instructions and reproduce the existing behaviour before changing it.
Keep versions together
Note which client, wallet, and example revisions you tested together. Follow each project’s current README for network configuration and toolchain requirements. A working example from one revision does not guarantee compatibility with another.