
Latest commit build status:
Verge Core requires a modern C++ toolchain and has migrated to reduce external dependencies for better performance and maintainability.
| Component | Requirement | Notes |
|---|---|---|
| Compiler | GCC 9.0+ / Clang 10.0+ / MSVC 2019+ | C++17 support required |
| C++ Standard | C++17 (targeting C++20) | Modern features for better performance |
| CMake | 3.16+ | Recommended build system |
| Boost | 1.70+ (selective components) | Reduced dependency footprint |
| OS | Version | Architecture |
|---|---|---|
| Ubuntu | 22.04, 24.04 | x64, ARM64 |
| Debian | 11+ | x64, ARM64 |
| CentOS/RHEL | 8+ | x64 |
| macOS | 13.0+ (Ventura), 14.0 (Sonoma) | x64, ARM64 (Apple Silicon) |
| Windows | 10 32bit/64bit, 11 32bit/64bit | x86, x64 |
| Specification | Value |
|---|---|
| Protocol | PoW (proof of Work) |
| Algorithms | scrypt, x17, Lyra2rev2, myr-groestl, & blake2s |
| Blocktime | 30 seconds |
| Total Supply | 16,521,951,238 XVG (Complete!) |
| RPC port | 20102 (testnet: 21102) |
| P2P port | 21102 (testnet: 21104) |
| pre-mine | Not Applicable |
| ICO | Not Applicable |
See RPC.md for the complete verged/verge-qt RPC command reference, including wallet, network, raw transaction, mining, and secure messaging commands.
Verge Secure Messaging (SMSG) is paid, encrypted wallet-to-wallet messaging. Messages use a shared chatkey in the form:
vergeaddress-publickey
verge-qt starts with SMSG enabled by default because it is normally used by wallet users. verged starts with SMSG disabled by default as a security measure for infrastructure deployments such as pools, exchanges, explorers, and public RPC nodes. This keeps infrastructure nodes from relaying, storing, and indexing SMSG data unless the operator explicitly opts in.
To enable SMSG on verged, add this to verge.conf or pass it on the command line:
smsg=1
Optional SMSG daemon settings:
# Scan the chain for chatkey funding/public-key data on startup.
smsgscanchain=1
# Scan incoming blocks for new SMSG public-key data.
smsgscanincoming=1
# Target number of validated SMSG relay peers to maintain.
smsgpeers=3
Basic verged SMSG workflow:
# Start verged with SMSG enabled for this run.
verged -smsg=1
# Create or choose a normal wallet address, then publish a local chatkey for it.
verge-cli getnewaddress "chat"
verge-cli smsgaddlocaladdress <youraddress>
# Show your shareable chatkey.
verge-cli smsggetpubkey <youraddress>
# Save another user's dashed chatkey and send a paid message.
verge-cli smsgaddaddress <theiraddress> <theirpublickey>
verge-cli smsgsend <youraddress> "<theiraddress>-<theirpublickey>" "hello" true 31
# Read messages.
verge-cli smsginbox all
verge-cli smsgoutbox all
If the wallet is encrypted, unlock it before creating chatkeys or sending messages:
verge-cli walletpassphrase "your passphrase" 300
SMSG paid messages default to 31 days of retention, and the sender can choose a lower retention period from 1 to 31 days. See RPC.md for the full secure messaging RPC reference.
| Block Number Range | Reward |
|---|---|
| 0 to 14,000 | 200,000 coins |
| 14,001 to 28,000 | 100,000 coins |
| 28,001 to 42,000 | 50,000 coins |
| 42,001 to 210,000 | 25,000 coins |
| 210,001 to 378,000 | 12,500 coins |
| 378,001 to 546,000 | 6,250 coins |
| 546,001 to 714,000 | 3,125 coins |
| 714,001 to 2,124,000 | 1,560 coins |
| 2,124,001 to 3,700,000 | 730 coins |
| 3,700,001 to 4,200,000 | 400 coins |
| 4,200,001 to 4,700,000 | 200 coins |
| 4,700,001 to 5,200,000 | 100 coins |
| 5,200,001 to 5,700,000 | 50 coins |
| 5,700,001 to 6,200,000 | 25 coins |
| 6,200,001 to 6,700,000 | 12.5 coins |
| 6,700,001 to 7,200,000 | 6.25 coins |
| 7,200,001+ | 0.0 coins |
If you only need the Qt wallet without WebEngine, you can build with:
./autogen.sh
cd depends
make -j"$(nproc)" HOST=x86_64-linux-gnu QT_SKIP_WEBENGINE=1 QT_SKIP_QTDECLARATIVE=1
cd ..
CONFIG_SITE="$PWD/depends/x86_64-linux-gnu/share/config.site" \
./configure --enable-scrypt-sse2 --disable-bench --disable-tests \
--disable-dependency-tracking --disable-werror \
--prefix="$PWD/depends/x86_64-linux-gnu"
make -j"$(nproc)"
Notes:
Binary (pre-compiled) wallets are available on all platforms here in Releases.
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.
Download the pre-compiled software from the releases section here.
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 (or getmininginfo) to verify settings.
Note: You must re-start the wallet after making changes to
verge.conf.
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 Unix instructions.
The wallet GUI is in ./verge/src/qt and the daemon in ./verge/src.
Optional - the binaries to your favorite location. for use by all users, run the following commands:
sudo cp src/verged /usr/bin/
sudo cp src/qt/verge-qt /usr/bin/
Run ./verged from wherever you put it. The output from this command will tell you that you need to make a verge.conf file and will suggest some good starting values.
Open up your new config file that was created in your home directory in your favorite text editor
nano ~/.VERGE/verge.conf
Paste the output from the verged command into verge.conf like this: (It is recommended to change the password to something unique.)
rpcuser=vergerpcusername
rpcpassword=85CpSuCNvDcYsdQU8w621mkQqJAimSQwCSJL5dPT9wQX
rpcport=20102
port=21102
daemon=1
algo=groestl
Save the file and exit your editor. If using nano type ctrl + x on your keyboard and the y and hitting enter. This should have created a verge.conf file with what you just added.
Start the Verge daemon again
./path/to/verged
Note: To check the status of how much of the blockchain has been downloaded (aka synced) type
./path/to/verged getinfo.
Note: If you see something like 'Killed (program cc1plus)' run
dmesgto 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.
To use VERGE with Unstoppable Domains for sending coins using Web3 Domains just put the name of the domain (ie: sunerok.crypto) in the "Pay To:" input in the Send tab of the wallet.
Verge Core is actively migrating to modern C++ standards and practices:
std::mutex and std::atomicstd::filesystem instead of boost::filesystemstd::thread over boost::threadstd::unique_ptr/std::shared_ptr instead of raw pointersconst correctness and noexcept specifications# Install modern dependencies
sudo apt update
sudo apt install -y \
build-essential cmake git \
libssl-dev libevent-dev \
libdb4.8-dev libdb4.8++-dev \
libboost-system-dev libboost-filesystem-dev libboost-test-dev \
libminiupnpc-dev libqt5gui5 libqt5core5a libqt5dbus5 \
qttools5-dev qttools5-dev-tools \
libprotobuf-dev protobuf-compiler \
libqrencode-dev libseccomp-dev libcap-dev
# Clone and build
git clone https://github.com/vergecurrency/VERGE && cd VERGE
./autogen.sh && ./configure --enable-cxx17 && make -j$(nproc)
# Modern build approach
mkdir build && cd build
cmake .. -DCMAKE_CXX_STANDARD=17 -DCMAKE_BUILD_TYPE=Release
cmake --build . --parallel $(nproc)
Performance Tip: Use
make -j$(nproc)orcmake --build . --parallelto utilize all CPU cores.
Memory Note: If you encounter memory issues, either add swap space or reduce parallelism with
-j2.
Requirements: macOS 12.0+ (Monterey), Xcode 13.0+, Command Line Tools
# Install Homebrew dependencies
brew install cmake boost openssl libevent berkeley-db4
brew install qt5 protobuf qrencode miniupnpc
# For Apple Silicon Macs, you may need to specify paths
export PATH="/opt/homebrew/bin:$PATH"
export PKG_CONFIG_PATH="/opt/homebrew/lib/pkgconfig:$PKG_CONFIG_PATH"
# Clone and build
git clone https://github.com/vergecurrency/VERGE && cd VERGE
./autogen.sh
./configure --enable-cxx17 --with-boost=/opt/homebrew
make -j$(sysctl -n hw.ncpu)
mkdir build && cd build
cmake .. \
-DCMAKE_CXX_STANDARD=17 \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_PREFIX_PATH="/opt/homebrew/opt/qt5" \
-DOPENSSL_ROOT_DIR="/opt/homebrew/opt/openssl"
cmake --build . --parallel $(sysctl -n hw.ncpu)
Apple Silicon Note: Some dependencies may need explicit paths. Use
brew --prefixto find installation directories.
TODO. Take a look at building/windows.
Check out the contrib/readme for more information.
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:
We believe in keeping Verge free and open. Any donations to help fuel the development effort are greatly appreciated! :smile:
DDd1pVWr8PPAw1z7DRwoUW6maWh5SsnCcp142r3vCAH3AzABiQjFPmcrSCp6TDzEDuB1Special thanks to the following people that have helped make Verge possible. :raised_hands:
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, 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.