Verus Coin - this coin was backdoored by it's lead dev and should not be trusted! https://git.hush.is/duke/backdoors/src/branch/master/vrsc.md
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

43 lines
1.6 KiB

<!--- Remove text and sections that do not apply -->
This issue tracker is only for technical issues related to verusd
General Verus questions and/or support requests and are best directed to [Discord](https://discord.gg/VRKMP2S)
### Describe the issue
Please provide a general summary of the issue you're experiencing
### Can you reliably reproduce the issue?
#### If so, please list the steps to reproduce below:
1.
2.
3.
### Expected behaviour
Tell us what should happen
### Actual behaviour + errors
Tell us what happens instead including any noticeable error output (any messages displayed on-screen when e.g. a crash occurred)
### The version of Verusd you were using:
Run `verusd -version` to find out
### Machine specs:
- OS name + version:
- CPU:
- RAM:
- Disk size:
- Disk Type (HD/SDD):
- Linux kernel version (uname -a):
- Compiler version (gcc --version):
- Linker version (ld -v):
- Assembler version (as --version):
### Any extra information that might be useful in the debugging process.
This includes the relevant contents of `~/.komodo/VRSC/debug.log`. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
Please also include any non-standard things you did during compilation (extra flags, dependency version changes etc.) if applicable.
### Do you have a backup of `~/.komodo/VRSC/` directory and/or take a VM snapshot?
- Backing up / making a copy of the `~/.komodo/VRSC/` directory might help make the problem reproducible. Please redact appropriately.
- Taking a VM snapshot is really helpful for interactively testing fixes