OpenViSTAI · Agents · Blockchain · Crypto
Menu
Layer 1

Verge

Verge is an open-source Layer 1 blockchain network and C++ core node implementation for running Verge Core, building a compatible client, and supporting node-based wallet, transaction, mining, and secure-messaging operations.

Independent OpenViST project profile, based on linked sources.

Verge — OpenViST project profile in Layer 1.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Verge when the task requires source-level access to the Verge blockchain client, a locally operated node, or the repository’s documented RPC functionality.

Who it is for

  • Developers working with C++ blockchain core software
  • Operators running Verge full-node or infrastructure environments
  • Teams building local tools around Verge Core RPC interfaces
  • Users evaluating a documented wallet-to-wallet secure messaging feature

Documented uses

  • Build the Verge Core software from source
  • Run a Verge full node
  • Create a node or mining operations environment
  • Interact with a local node through wallet, network, transaction, mining, and secure messaging RPC commands
  • Configure SMSG for wallet-to-wallet messaging
Before you choose

Requirements & limits

The repository is public and MIT-licensed. The project lists Windows, Linux, and macOS support with CLI, server, and desktop environments; exact supported versions and architectures are specified in the repository.

  • The build requires C++17, CMake 3.16 or newer, and supported compiler versions.
  • Boost 1.70 or newer is required for selected components.
  • The implementation uses proof of work with scrypt, x17, Lyra2rev2, myr-groestl, and blake2s algorithms.
  • The documented RPC surface includes wallet, network, raw transaction, mining, and secure messaging commands.
  • SMSG is enabled by default in verge-qt but disabled by default in verged for infrastructure deployments.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare a Verge Core build environment

Set up the documented compiler, build system, dependency, and operating-system prerequisites for Verge Core.

Before you start

  • C++17-capable GCC 9+, Clang 10+, or MSVC 2019+
  • CMake 3.16 or newer
  • Boost 1.70 or newer for selected components
  • A listed Ubuntu, Debian, CentOS/RHEL, macOS, or Windows environment

Steps

  1. Choose a supported operating system and architecture from the repository’s requirements table.

  2. Install a supported C++ toolchain with C++17 support.

  3. Install CMake 3.16 or newer.

  4. Provide Boost 1.70 or newer for the components that require it.

  5. Continue with the repository’s build documentation and source tree instructions.

Expected outcome

A documented prerequisite environment for building Verge Core.

Guide limitations

  • The supplied material specifies prerequisites but does not provide the complete build command sequence or verify a successful local build.
Source-based practical guide

Enable secure messaging on a Verge daemon

Configure a Verge daemon for the documented SMSG wallet-to-wallet messaging workflow.

Before you start

  • A running Verge daemon and wallet
  • A normal wallet address
  • The recipient’s address and public chatkey
  • An unlocked wallet before creating chatkeys or sending messages

Steps

  1. Enable SMSG with the daemon configuration setting or the documented command-line option.

  2. Create or select a wallet address and publish its local chatkey.

  3. Add the recipient’s address and public chatkey.

  4. Send a paid message using the documented SMSG command and retention value.

  5. Read incoming and outgoing messages with the documented inbox and outbox commands.

Expected outcome

A daemon configured for the repository’s SMSG workflow, with commands for publishing keys, sending messages, and reading messages.

Guide limitations

  • SMSG is disabled by default for verged infrastructure deployments.
  • Messages default to 31 days of retention, with a documented lower range of 1 to 31 days.
  • The supplied material does not verify a live transaction or message delivery.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
2 October 2026
Original website title
vergecurrency/verge · Official homepage title · retained in its source language