____ _________________________ ________ ___________
\ \ / /\_ _____/\______ \ / _____/ \_ _____/
\ Y / | __)_ | _// \ ___ | __)_
\ / | \ | | \\ \_\ \ | \ 2018 VERGE/XVG
\___/ /_______ / |____|_ / \______ //_______ /
\/ \/ \/ \/
VERGE is released under the terms of the MIT license. See LICENSE for more information or see https://opensource.org/licenses/MIT.
The master
branch is regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of VERGE.
The contribution workflow is described in CONTRIBUTING.md.
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and remember this is a security-critical project where any mistake might cost people lots of money.
Specification | Value |
---|---|
Protocol | PoW (proof of Work) |
Algorithms | scrypt, x17, Lyra2rev2, myr-groestl, & blake2s |
Blocktime | 30 seconds |
Total Supply | 16,500,000,000 XVG |
RPC port | 20102 |
P2P port | 21102 |
pre-mine | N/A |
ICO | N/A |
Block Number | Reward |
---|---|
0 to 14,000 | 200,000 coins |
14,000 to 28,000 | 100,000 coins |
28,000 to 42,000 | 50,000 coins |
42,000 to 210,000 | 25,000 coins |
210,000 to 378,000 | 12,500 coins |
378,000 to 546,000 | 6,250 coins |
546,000 to 714,000 | 3,125 coins |
714,000 to 2,124,000 | 1,560 coins |
2,124,000 to 4,248,000 | 730 coins |
Binary (pre-compiled) wallets are available on all platforms at https://vergecurrency.com.
Note: Important! Only download pre-compiled wallets from the official Verge website or official Github repos.
Note: For a fresh wallet install you can reduce the blockchain syncing time by downloading a nightly snapshot and following the setup instructions.
Check out the contrib/readme
for more information.
-
Download the pre-compiled software.
-
Install
-
In windows file explorer, open
c:\Users\XXX\AppData\Roaming\VERGE
(be sure to change XXX to your windows user) -
Right click and create a new file
verge.txt
-
Edit the file to have the following contents (be sure to change the password)
rpcuser=vergerpcusername rpcpassword=85CpSuCNvDcYsdQU8w621mkQqJAimSQwCSJL5dPT9wQX rpcport=20102 port=21102 daemon=1 algo=groestl
-
Save and close the file
-
Rename the file to
verge.conf
-
Start the VERGE-qt program.
-
Open up VERGE-qt console and run
getinfo
(orgetmininginfo
) to verify settings.
Note: You must re-start the wallet after making changes to
verge.conf
.
- Download the pre-compiled software.
- Double click the DMG
- Drag the Verge-Qt to your Applications folder
- Double click the Verge-Qt application to open it.
- Go grab a ☕ while it syncs with the blockchain
Note: It may look like it is frozen or hung while it is indexing and syncing the blockchain. It's not. It's chugging away, but currently the UI doesn't give you a lot of feedback on status. We're working to fix that. Syncing takes a while to complete (ie. > 10 minutes or more) so just be patient.
Note: If you want to change your configuration the file is located at
~/Library/Application\ Support\VERGE\VERGE.conf
. This isn't required by default.
-
Compile using linux instructions.
If compilation was successful, the wallet GUI and the daemon binaries are
~/VERGE/src/qt/VERGE-qt
and~/VERGE/src/VERGEd
respectively.After full installation, they are also in
/usr/local/bin/
directory.Optional: Copy binaries to your favourite location, e.g.:
sudo cp ~/VERGE/src/VERGEd /path_to_VERGEd/VERGEd sudo cp ~/VERGE/src/qt/VERGE-qt /path_to_VERGE-qt/VERGE-qt
-
Start Verge daemon by running
VERGEd
or/path_to_VERGEd/VERGEd
. -
Redact ~/.VERGE/VERGE.conf, e.g.:
nano ~/.VERGE/VERGE.conf
Using this example, set your specific parameters (Don't forget to change default rpcuser/rpcpassword):
rpcuser=vergerpcusername rpcpassword=85CpSuCNvDcYsdQU8w621mkQqJAimSQwCSJL5dPT9wQX rpcport=20102 port=21102 daemon=1 algo=groestl
-
Start Verge daemon again.
Note: To check the status of how much of the blockchain has been downloaded (aka synced) type
VERGEd getinfo
or/path_to_VERGEd/VERGEd getinfo
.
Note: If you see something like 'Killed (program cc1plus)' run
dmesg
to see the error(s)/problems(s). This is most likely caused by running out of resources. You may need to add some RAM or add some swap space.
You can also check out this Linux Wallet Video Tutorial.
Instead of joining a mining pool you can use the wallet to mine all by yourself. You need to specify the algorithm (see below) and set the "gen" flag. For instance, in the configuration specify gen=1
.
To use a specific mining algorithm use the algo
switch in your configuration file (.conf
file) or from the command line (like this --algo=x17
). Here are the possible values:
algo=x17
algo=scrypt
algo=groestl
algo=lyra
algo=blake
Here is a list of active testnet nodes: ddvnucmtvyiemiuk.onion (sunerok)
We believe in keeping Verge free and open. Any donations to help fuel the development effort are greatly appreciated! 😄
- Address for donations in Verge (XVG):
DDd1pVWr8PPAw1z7DRwoUW6maWh5SsnCcp
- Address for donations in Bitcoin (BTC):
142r3vCAH3AzABiQjFPmcrSCp6TDzEDuB1
Special thanks to the following people that have helped make Verge possible. 🙌
Sunerok, CryptoRekt, MKinney, BearSylla, Hypermist, Pallas1, FuzzBawls, BuZz, glodfinch, InfernoMan, AhmedBodi, BitSpill, MentalCollatz, ekryski and the entire #VERGE community!
If you think you've found a bug or a problem with VERGE, please let us know! First, search our issue tracker to see if someone has already reported the problem. If they haven't, click here to open a new issue, and fill out the template with as much information as possible. The more you can tell us about the problem and how it occurred, the more likely we are to fix it.
Since we are a 100% open-source project we strongly prefer if you create a pull-request on Github in the proper repository with the necessary fix.
Alternatively, If you would like to make a suggestion regarding a potential fix please send an email to contact@vergecurrency.com
Contact the developers privately by sending an e-mail to contact@vergecurrency.com with the details of the issue. Do not post the issue on github or anywhere else until the issue has been resolved.