There are different flavors of downloadable clients (wallets) available for the WGR coin, from the official desktop Qt and command line daemon, to the community developed Android and upcoming modern desktop and mobile app.
The Qt wallet is created using the standard Qt cross-platform application framework, which enables development of a feature rich Graphical User Interface for every major OS. As a widely supported framework for cryptocurrency wallets, it is powerful and far easier to use for most users than the command line. This walk-through guide explains the primary functions of it.
Download the latest official desktop Qt client from https://github.com/wagerr/wagerr/releases.
There is a list of compatible versions for your particular operating system including Linux, Apple Macintosh and Microsoft Windows - if running a 64 bit operating system or processor setup, download that and not the 32 bit version.
Compatibility
Wagerr Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported.
Wagerr Core should also work on most other Unix-like systems but is not frequently tested on them.
Currently, there are known issues with the Gitian release for macOS 10.13 and above and you must download the version labelled for your macOS. You can find this information from the System About screen which is accessed as follows:
Apple Menu > About This Mac
You can also open this directly by holding down the Options key and choose Apple menu 
and then choose System Settings.
How do I find out my Linux kernel version?
Type the following uname command:
$ uname -a
System files
Explanation of downloadable files presented on https://github.com/wagerr/wagerr/releases
* Always check for the latest release version (v3.0.0 is release example listed here). 
SHA256SUMS.asc
This is to verify the downloaded file, if you open the text file included within the zip, you will see some SHA256 checksums. A checksum is a 32-character hexadecimal number that is computed on a released file. If two files have the same checksum value, then the downloaded file is safe and has not been tampered with.
Example checksum:
a984e9c2f83b0f3fdd11ed944d88c0b8f6cbecce53886d33ddbb6c52f171e676
For Linux, navigate to the correct folder that contains the downloaded file and use the command:
Sha256sum <filename>
echo "YourSHA256SUM <filename>.tar.gz" | sha256sum -c
..or if you have sums file:
sha256sum -c SHA256SUMS
For MacOS, open the Terminal by searching for it in Spotlight or Launchpad or open it from Applications > Utilities:
Once the Terminal is open, type
shasum -a 256
Then add a space and type the full path and filename* such as:
shasum -a 256 Users/Downloads/wagerr-3.0.0-osx.dmg
This will then return the checksum that can be verified against the SHA256SUMS.asc file.
*Mac users can drag and drop the disk image (.dmg file) from the finder into the Terminal window to auto-populate the full path and filename.
For Windows, download a checksum utility:
https://www.google.com/search?ei=UWhlXPiJLNiX1fAPxoGzqA0&q=sha256sum+windows
Then open the file from within the software to make sure the checksum value is the same.
Alternatively, there is a Chrome Browser plugin extension at https://code.kliu.org/hashcheck/
WGR Client Wallet downloads:
wagerr-3.0.0-aarch64-linux-gnu.tar.gz
Linux downloadable file, normally from the command console for Daemon instances but can be downloaded via GUI and extracted - contains Daemon Wagerrd and WGR Qt (mainnet\testnet instances).
wagerr-3.0.0-arm-linux-gnueabihf.tar.gz
Linux downloadable file, normally from the command console for Daemon instances but can be downloaded via GUI and extracted - contains Daemon Wagerrd and WGR Qt (mainnet\testnet instances). For Raspberry Pi versions of Linux.
wagerr-3.0.0-i686-pc-linux-gnu.tar.gz
Client wallet for i686 architecture (32 bit) Linux machines (file is archived and needs to be extracted to a folder, desktop location recommended - then run to start WGR Qt).
wagerr-3.0.0-osx.dmg
Client wallet for MacOS X machines (file is archived and needs to be extracted to a folder, desktop location recommended - then run to start WGR Qt).
Client wallet for MacOS X (64 bit) machines (file is archived and needs to be extracted to a folder, desktop location recommended - then run to start WGR Qt).
wagerr-3.0.0-riscv64-linux-gnu.tar.gz
Client wallet for RISC systems architecture running under Linux. (file is archived and needs to be extracted to a folder before running)
wagerr-3.0.0-win32-setup.exe
Attended client wallet setup process and files for Windows 32 bit machines (Executable file download - download and run from its hard drive location)
Client wallet for Windows 32 bit machines (file is archived and needs to be extracted to a folder, desktop location recommended - then run to start WGR Qt)
wagerr-3.0.0-win64-setup.exe
Attended client wallet setup process and files for Windows 64 bit machines (executable file download - download and run from its hard drive location to start setup routine)
Client wallet for Windows 64 bit machines (file is archived and needs to be extracted to a folder, desktop location recommended - then run to start WGR Qt)
wagerr-3.0.0-x86_64-linux-gnu.tar.gz
Linux downloadable file, normally from the command console for Daemon instances but can be downloaded via GUI then extracted - contains Daemon Wagerrd and WGR Qt (mainnet\testnet instances). Has been tested on Ubuntu 16.04 (recommended) and some other flavors of Linux.
Linux download to run WGR Daemon and WGR Qt client locally after extraction. (Tarball archive)
Source code (.zip)
WGR Daemon and WGR Qt source code (Zip archive)
WGR Daemon and WGR Qt source code (Tarball archive)
If applicable with the relevant client software packages, after downloading via your browser, run the executable file to run through the setup installation.
If running command-line functions, download then extract the files as per guides available.
You do not need to change anything unless changing the default location of installation files or customizing your WGR client data directory location.
After downloading via your browser, run the executable file to run through the setup installation.
If you have downloaded a standalone version, one that does not have the setup routine included, just extract the files to a pre-created WGR folder, once extracted, run the wagerr_qt.*** file to run the client.*
*There are many different archive or compressed file utilities such as WinZip, WinRar, 7Zip and others - some operating systems have file extraction utilities ready-built into them, wrong click on the archive you downloaded and see if it is recognized by the operating system, if no ‘extract’ option shows on the context menu, download one of the utilities for your operating system as above.
Wagerr desktop Qt client overview
 |
File menu |
 |
Client navigation area |
 |
WGR client balance overview |
 |
Quickview transactions |
 |
Synchronization progress bar |
 |
Client status indicators |
Now that you have installed the WGR Qt client onto the computer system, go ahead and open it from the ‘Wagerr core’ link on the Applications file menu or via the extracted files folder location by manually starting the wagerr_qt.*** executable file.
(Some antivirus programs may show a false flag on running the client, it may think there is some sort of Bitcoin mining malware running - this is to do with Antivirus heuristics. Eventually, newly released clients are submitted and accepted as false positives then exceptions are made by the AC companies in their next update — however you may need to set an exception in your AV software so it does not quarantine the file every time you open the client...
Upon the first running, the client will create a wallet.dat file and the standard configuration files, it will look for a connection from other peers on the WGR network and once connected, start to download the blockchain direct to the computer's hard disk drive.
When the client has connections (shown in the status bar or via the Tools menu > Peers list) the progress of the blocks downloaded from the WGR blockchain will be shown in the synchronization status bar at the bottom of the client.
As the blocks are downloading, any transactions made after the current downloaded block will not be shown in the client or available for use. For instance, if while the client is synchronizing and a transaction is sent to the client at block 408100. The transaction will only show (and start to confirm for use) from block 408101. As the blocks are downloading from the Genesis block of number 0, it can take some time to update to the current latest block.
WGR bootstrap file
There is a way to speed this up this process using a Wagerr developer released ‘Bootstrap’ this is a set of blockchain files that can be imported into the client, the link is at https://github.com/wagerr/wagerr/releases/tag/wagerr-bootstrap - you do not need to use this necessarily but can wait for the client to synchronize on its own - this can be a long process if restricted on peer connections or you have a slow internet connection/rate limiting, but once completed you do not need to re-download the whole blockchain again but only catch up to the updates current block or set of blocks if the client has been off / or lost connection, for instance.
Encrypt the wallet.dat file
The wallet.dat file that was created earlier contains all the receiving addresses in the client, to begin with a single WGR address is created but as time goes on more and more addresses will be created by yourself manually or even automatically when a ‘change’ address is created.
The wallet.dat is, therefore, a very important and valuable file, encrypting it with a secure passphrase will prevent unauthorized funds being sent from the client and advanced functions being accessed.
It is very important when choosing and entering the wallet.dat clients' passphrase for usage that you do not forget it afterward. After encryption, basic wallet function will be inaccessible and it is a (sometimes impossible) process using advanced tools and scripts to retrieve the passphrase again - if using a third-party service this can be very costly and has security implications too.
Choose a secure passphrase that you will not forget.
Now Click File > Encrypt Wallet…
Enter the chosen secure passphrase twice, one after the other in each box provided, then click Ok..
The computer will take some computational time and it may appear to have hung but it has not so be patient - after some time the ‘Encrypt Wallet’ window will disappear and you will be returned to the client overview page.
You did remember that chosen passphrase, didn’t you?
Now, from the Settings menu> Unlock Wallet. Enter the passphrase then click ok.
After a successful client unlock, the padlock icon in the status indicators area will show as unlocked:
Your Wagerr Qt clients wallet.dat file is now encrypted making it much more secure than in its previous default state and the client will need to be unlocked for operations such as when sending funds or allowing access to performing advanced functions.
Now shutdown and restart the client, let it fully sync, once complete a green checkmark will appear in the status bar and it will then be fully synchronized with the WGR blockchain:
---
Wagerr Qt client FAQ
How do I create a wallet backup?
Your WGR coin (essentially the private keys that prove ownership) are stored in the data file (in the data directory) is named wallet.dat. It is, therefore, a good idea to have a regular off-device (and even off-site) wallet backup routine so as to save your wallet file in the case of device or software failure.
A guide on how to backup your wallet is available at:
You can name this file whatever you like, for instance, a descriptive name and today’s date. The Backup Wallet feature will always add the filetype extension ‘.dat’.
How do I create a receiving address?
If you click on the ‘Receive’ button, a pop up window will display with a new address shown via a QR code for mobile clients to scan with their cameras, and a Character string starts with a ‘W’ - this is your publically distributable address, on this popup window, you can request specific payments or just create new wallet addresses and references for payment types / amounts.*
Remember, that for each of these newly created addresses, they are stored within the wallet.dat but can be separately backed up via the ‘dumpprivkey’ command in the console on the client.
A guide on how to backup the private keys to your public addresses is available at:
Where is my default WGR core client data directory?
The data directories vary on different operating systems and platforms as follows:
- Windows: %APPDATA%\Wagerr\
Windows users can copy %APPDATA%\Wagerr into the search pane and press return
- Linux: ~/.wagerr/
- Mac: ~/Library/Application Support/WAGERR/
How do I backup the private keys for an address?
It is sometimes safer to separately back up WGR addresses if they contain significant holdings, also the same if you should use an address regularly, like a staking or regular use betting wallet, follow the guide on how to perform this:
How do I import the private keys for an address?
If you have a data failure or are consolidating wallet addresses, the separately backed up private keys can be imported from following the guide:
What is staking, how do I take part in it?
There is a guide on how to setup your client for staking if you have a good amount of coins:
I want to run a masternode, how do I do this (remotely)
25,000 WGR coins are required to run a masternode, a local Qt client and correctly configured VPS with a minimum 2Gb of installed memory is required for ongoing operation. A guide on how to set this up is linked at:
https://github.com/wagerr/wagerr/wiki/Setting-up-a-masternode
How to use the WGR wallet client coin control
Follow the guide at https://wagerr.zendesk.com/hc/en-us/articles/360022387312-How-to-use-the-WGR-wallet-client-coin-control in order to enable coin control and its advanced features.
What is a ‘change’ address
A ‘change address’ is an address within the client that is sometimes created if a set of coin inputs in a block (shown in ‘coin control’) on your local money supply are not accessible. For example, if a single input block of 10,000 WGR needs to split for staking, it would split into two blocks of 5000 normally, but in this instance because there are no other coin blocks available to split into - as it cannot split into itself again, the client must then create a new address for the currently staking / splitting coins that are shown as immature / not available, when these newly created coins are confirmed into the new ‘change’ address, they are then ready for usage.
You can set a custom change address for your client (remembering to select all the coin inputs with the coin control feature) and entering a wallet address within the ‘custom change address’ box. This will then use the available coin blocks from the overall balances to split into. Even then, occasionally a change address may show up for whatever reason.
Make sure you have a backup of your change addresses
Change addresses are fine and perfectly normal. They help run the WGR network. Since change addresses are generated automatically, there are a few things you can do to protect your assets.
Each change address, just like each main address in your wallet, is a public key with a corresponding private key — and ownership of that private key is your only way to access funds stored in the change address.
The wallet.dat file contains the private keys for change addresses, so it’s important to make and keep regular backups of the file.
The main point to remember is that if you have significant holdings in a change address, then later you lose access to the wallet.dat (due to file corruption, for instance), you will only have access to funds associated with addresses for which you have private keys. So even if you maintain a backup of your main addresses, but fail to maintain access for all change addresses, your funds will be irretrievable.
You can remedy this situation by setting the custom change address as above and periodically checking in coin control for change addresses (Then sending those coin blocks back to a regular (private key backed address). If you don’t want to send the coins, you can always create a backup of the private key for each change address, as well.
How can I backup the blockchain files?
It is possible to backup the local blockchain files in case of a sudden power loss or corruption of the local blockchain index files.
With the client shut down, open the data directory:
The data directory varies on different operating systems and platforms as follows:
- Windows: %APPDATA%\Wagerr\
Windows users can copy %APPDATA%\Wagerr into the search pane and press return
- Linux: ~/.wagerr/
- Mac: ~/Library/Application\ Support/wagerr/
Then, copy the four folders named:
- Blocks
- Chainstate
- Sporks
- Zerocoin
Choose a readily accessible location that could be on the actual computer where the client is hosted, you could use a USB flash drive or another storage medium if hard disk space is at a premium.
In the event you want to restore the blockchain files, such as in the case of a corruption of the local blockchain index, simply copy the four folders back into the data directory over the old files, and restart the client. Upon restart, it will reindex the local disk files and sync to the latest blockheight. This takes some time but will be much quicker than a total blockchain download and reindex directly off the WGR network.
Wagerr Qt does not connect to the network to synchronize on the first install, why not?
This could be because the Wagerr DNS and/or the nodes regional to you do not have a connection slot available. It could also be because of a restriction in your local antivirus and/or firewall port blocking.
If after some time, half an hour or so, and there are still no connections; check the following:
First, let’s check that your port is open. Go to https://canyouseeme.org and enter 55002 into the port checker box:
(It is also handy to be able to see your own local IP address too, it may be required later if setting up advanced Qt client functions such as remote masternode hosting).
If the port is showing connected and you still do not get connections there may be some software or hardware such as the router port that needs unblocking. Refer to your OS firewall, and your router/gateway or ISP provided user manual to find out how to do this.
If after allowing the port 55002 and you still do not get connections, follow the guide at:
https://wagerr.zendesk.com/hc/en-us/articles/360016454792-How-to-Enable-WGR-Addnodes-for-connections
Relaunch the Wagerr Qt client after adding the addnodes. When the client restarts, it will connect to those peers and download the blockchain. You can monitor the syncing progress from the bar at the bottom of the client window:
| |
Synchronization progress bar |
|
Client status indicators |
Remember to subsequently remove the addnodes from wagerr.conf when fully connected and synchronized because they can actually cause problems in the future.
If, after doing all the above, with client restarts in between and you still do not get connections; email support@wagerr.com and our support staff will be happy to assist you.
Wagerr Qt does not connect to the network to synchronize anymore, why might this be?
- Is the client fully synchronized? - you can see this from the status bar and indicators.
- I sent some mainnet WGR to the client, why is it not showing yet? (see above).
- Are you running the latest client wallet that is available from: https://github.com/wagerr/wagerr/releases
- Have you had a new internet router or network setup - sometimes the ports need opening in DMZ or the port forwarding section on admin manager?
- Can you access port 55002 from https://canyouseeme.org - goes with about port mapping solution too.
- Is there an active internet connection, can you open a random not visited before page on your web browser?
- Is the client on the correct chain? (do getblockhash with the latest block and check hash is the same on an ION blockchain explorer).
- If you get connections and the client stops syncing at a certain block around 300,000+ - try using the bootstrap at https://github.com/wagerr/wagerr/releases/tag/wagerr-bootstrap
If you still cannot get active connections, email support@wagerr.com
-
Wagerr Home: https://wagerr.com
Wagerr Discord: https://discord.gg/tkcXS34
Wagerr Telegram: https://t.me/wagerrcoin
Wagerr Github: https://github.com/wagerr/wagerr/releases
Wagerr Electron GitHub: https://github.com/wagerr/wagerr-electron-app
Wagerr Twitter: https://twitter.com/wagerrx
Wagerr Facebook: https://www.facebook.com/wagerr/
Technical Support: support@wagerr.com
Comments
0 comments
Article is closed for comments.