1 <!--- Remove text and sections that do not apply -->
3 This issue tracker is only for technical issues related to zcashd.
5 General Zcash questions and/or support requests and are best directed to the [Zcash Forums](https://forum.z.cash) or [Community Rocket.Chat](https://chat.zcashcommunity.com).
7 For reporting security vulnerabilities or for sensitive discussions with our security team, please contact [
[email protected]](mailto:
[email protected]). You can use the [GPG key](https://z.cash/gpg-pubkeys/security.asc) (fingerprint: `AF85 0445 546C 18B7 86F9 2C62 88FB 8B86 D8B5 A68C`) to send an encrypted message. The key and fingerprint are duplicated on our [Public Keys page](https://z.cash/support/pubkeys.html).
10 Please provide a general summary of the issue you're experiencing
12 ### Can you reliably reproduce the issue?
13 #### If so, please list the steps to reproduce below:
18 ### Expected behaviour
19 Tell us what should happen
21 ### Actual behaviour + errors
22 Tell us what happens instead including any noticable error output (any messages displayed on-screen when e.g. a crash occurred)
24 ### The version of Zcash you were using:
25 Run `zcashd --version` to find out
33 - Linux kernel version (uname -a):
34 - Compiler version (gcc -version):
36 ### Any extra information that might be useful in the debugging process.
37 This includes the relevant contents of `~/.zcash/debug.log`. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
38 Please also include any non-standard things you did during compilation (extra flags, dependency version changes etc.) if applicable.
40 ### Do you have a back up of `~/.zcash` directory and/or take a VM snapshot?
41 - Backing up / making a copy of the `~/.zcash` directory might help make the problem reproducible. Please redact appropriately.
42 - Taking a VM snapshot is really helpful for interactively testing fixes