Community¶
Where to ask a question, report a bug, and follow releases - and which of those channels is the right one for what you have.
Where to find us¶
| Discord | discord.com/invite/KN8PjyuvG4 |
| X | @wrkzcoin |
| GitHub | github.com/wrkzcoin |
The same three links sit in the footer of every page.
Where to take what¶
Discord is the fastest route for anything operational — a node that will not start, a wallet that will not sync, a question about which flags to use. Bring the daemon log and the exact command line; both matter more than the description of the symptom.
GitHub issues are for reproducible bugs and feature requests against wrkzcoin/wrkzcoin. Use the issue templates: they ask for the version string (Wrkzd --version), the platform, and the steps, which is what makes an issue actionable.
X carries release announcements and network notices, including fork heights. It is a broadcast channel, not a support channel.
Contributing¶
Pull requests go to the development branch of wrkzcoin/wrkzcoin. Build instructions are in COMPILE.md. The repository's README.md has a note for contributing developers about license headers: any open source project may use this software, but the license headers may only be appended to, never altered.
Documentation lives in docs/ in the same repository, and every page on this site has an edit link in its top-right corner that opens the source file on GitHub.
Security reports¶
Do not open a public issue for a vulnerability that affects funds, consensus or node availability. Report it privately to a maintainer on Discord first, so a fix can be released before the detail is public.
Other resources¶
| Website | wrkz.work |
| Latest release version | latest.wrkz.work |
| Public transaction PoW server | txpow.wrkz.work:443 — see Transaction PoW Server |