VargaMesh Desktop v0.3.2

VargaMesh Desktop v0.3.2

Recommended Windows release.

VargaMesh Desktop v0.3.2 fixes the v0.3.1 send regression on sparse/new VargaMesh networks.

Fixed: Method not found while sending

v0.3.1 correctly detected that estimatesmartfee had insufficient history, but attempted to apply the temporary rate through the settxfee RPC. VargaMesh Core v0.1.0 does not expose that RPC, so clicking the send/review flow could end with “Method not found.”

v0.3.2 uses the Core-supported fallback mechanism instead:

• bundled VargaMesh Core starts with -fallbackfee=0.00001000
• this equals a 1 sat/vB baseline for an 8-decimal VMESH network
• estimatesmartfee remains preferred when sufficient history exists
• normal sendtoaddress transaction creation is used; no settxfee RPC is called
• the UI continues to show Fallback while estimator history is insufficient
• if an old/external Core is still running without fallback fees enabled, Desktop returns an actionable restart message

After installing v0.3.2, fully quit the old Desktop instance (including tray/Core) before launching v0.3.2 so the bundled Core is restarted with the new fee setting.

Downloads

• VargaMesh-Desktop-v0.3.2-Windows-x64-Setup.exe
• VargaMesh-Desktop-v0.3.2-Windows-x64-Portable.zip
• SHA256SUMS

Existing blockchain and wallet data remains under %LOCALAPPDATA%\VargaMesh. Keep an independent wallet backup before upgrading.

VargaMesh Desktop is pre-1.0 software. Carefully verify recipient addresses and transaction amounts before sending.

VargaMesh Desktop v0.3.1

VargaMesh Desktop v0.3.1

Recommended Windows release.

VargaMesh Desktop v0.3.1 is a focused transaction-fee reliability update for the Windows x64 self-custody wallet and local full-node client.

Fixed: sending on a sparse/new network

VargaMesh Core's smart fee estimator can legitimately have no estimate when the chain has not yet observed enough transaction and block history. In v0.3.0 that state was shown as “Insufficient data or no feerate found”, and a send could then fail with “Fee estimation failed. Fallbackfee is disabled.”

v0.3.1 handles that condition inside Desktop:

• use estimatesmartfee when a valid estimate exists
• otherwise derive a conservative temporary fallback from the local node's relay/mempool minimums
• never fall below 1 sat/vB (0.00001000 VMESH/kvB)
• refuse an unexpectedly high automatic fallback above 100 sat/vB instead of silently overpaying
• apply the fallback only to the active wallet for the send attempt
• immediately reset the wallet to automatic fee selection afterwards
• show Fallback in the Send UI when estimator history is not yet sufficient

No persistent fallbackfee= setting is added to the user's Core configuration.

Existing v0.3 features

• local VargaMesh Core v0.1.0 full node
• self-custody wallet with local signing
• WIF private-key import with expected-address verification
• watch-only import and optional blockchain rescan
• wallet backup/restore and descriptor/legacy handling
• Windows tray/background mode and optional start with Windows
• local cookie-authenticated RPC only
• no telemetry, advertising or cloud wallet backend

Downloads

• VargaMesh-Desktop-v0.3.1-Windows-x64-Setup.exe
• VargaMesh-Desktop-v0.3.1-Windows-x64-Portable.zip
• SHA256SUMS

Verify the download

Get-FileHash .\VargaMesh-Desktop-v0.3.1-Windows-x64-Setup.exe -Algorithm SHA256
Get-FileHash .\VargaMesh-Desktop-v0.3.1-Windows-x64-Portable.zip -Algorithm SHA256

Compare the values with SHA256SUMS attached to the GitHub release.

Existing blockchain and wallet data remains under %LOCALAPPDATA%\VargaMesh. Keep an independent wallet backup before upgrading.

VargaMesh Desktop is pre-1.0 software. Carefully verify recipient addresses and transaction amounts before sending.

VargaMesh Desktop v0.3.0

VargaMesh Desktop v0.3.0

Current recommended Windows release.

VargaMesh Desktop v0.3.0 is a major usability and wallet-management release. It combines a local VargaMesh Core full node with a hardened desktop interface, private-key recovery/import tools and native Windows background/tray operation.

Highlights

Wallet recovery and import

• WIF private-key import for descriptor and legacy wallets
• expected-address verification before a private key is imported
• Bech32/P2WPKH, P2SH-SegWit and legacy P2PKH import choices
• watch-only address import
• optional full-history rescan for recovered keys/addresses
• descriptor/legacy wallet detection before migration
• legacy migration is disabled when the selected wallet is already descriptor-based
• temporary passphrase unlock for protected import operations followed by wallet relock

Windows background operation

• system-tray / notification-area support
• optional close-to-tray
• optional minimize-to-tray
• optional start minimized
• optional start with Windows in the background
• tray command to lock all loaded wallets
• clean Quit and stop Core command

Node and diagnostics

• bundled VargaMesh Core v0.1.0 Windows x64 runtime
• complete Core runtime directory is preserved in release packages
• automatic local Core startup
• localhost-only cookie-authenticated RPC
• node height, sync, peer, difficulty, mempool and hashrate views
• improved Core startup diagnostics and runtime logging
• hardened Linux/Wine build support for headless VPS builders through Xvfb

Security model

Private keys remain under VargaMesh Core control. The Electron renderer is sandboxed, Node.js integration is disabled, RPC credentials are not exposed to the renderer and arbitrary RPC calls are not available through the preload bridge.

WIF keys and wallet passphrases are used only for the requested local operation and are not persisted in Desktop settings or runtime diagnostics. Sensitive-looking private-key values are redacted from surfaced application errors.

Downloads

Use one of the Windows x64 packages attached to this release:

• VargaMesh-Desktop-v0.3.0-Windows-x64-Setup.exe
• VargaMesh-Desktop-v0.3.0-Windows-x64-Portable.zip
• SHA256SUMS

The portable package must be extracted before running VargaMesh Desktop.exe.

Verify the download

PowerShell:

Get-FileHash .\VargaMesh-Desktop-v0.3.0-Windows-x64-Setup.exe -Algorithm SHA256
Get-FileHash .\VargaMesh-Desktop-v0.3.0-Windows-x64-Portable.zip -Algorithm SHA256

Compare both values with SHA256SUMS attached to this release.

Upgrade notes

Existing blockchain and wallet data remains under:

%LOCALAPPDATA%\VargaMesh

Installing v0.3.0 over an older Desktop version does not intentionally delete this data. Keep an independent wallet backup before upgrading.

Private-key import warning

A VargaMesh address alone is public information and does not grant spending access. Importing an existing spendable address requires its matching WIF/private key or an appropriate wallet backup.

Never paste a WIF/private key into GitHub Issues, chat, Discord, email or a website. Use the Desktop import dialog locally and, when recovering a known address, fill in Expected address so Desktop can verify that the supplied WIF derives the intended address before import.

Bundled software

• VargaMesh Desktop: v0.3.0
• VargaMesh Core: v0.1.0
• Windows architecture: x64

VargaMesh Desktop is pre-1.0 software. Independent backups and careful verification remain strongly recommended.

VargaMesh Desktop v0.2.1

VargaMesh Desktop v0.2.1

Windows x64 full-node wallet hotfix.

Fixes

• preserves the complete VargaMesh Core Windows runtime directory during packaging instead of extracting only the daemon and CLI executables
• hardens the child-process PATH with the bundled Core directory and Windows system runtime paths
• decodes Windows loader exit 0xC0000135 as STATUS_DLL_NOT_FOUND in desktop-runtime.log
• surfaces Core startup failures directly in the Desktop startup banner instead of remaining indefinitely on “Starting VargaMesh Core”
• keeps the existing localhost-only RPC and Core-owned private-key security model

This is a testing pre-release. Verify SHA256 checksums and test with small amounts first.

VargaMesh Desktop v0.1.1

VargaMesh Desktop v0.1.1

Windows desktop wallet and full-node controller for VargaMesh.

Fixes

• fixes Windows startup path handling for %LOCALAPPDATA%
• removes duplicate Core network/RPC command-line arguments; vargamesh.conf is authoritative
• adds fallbackfee=0.00001000 to the generated local vargamesh.conf
• provides a 1 sat/vB fallback transaction fee when VargaMesh Core has insufficient fee-estimation data
• fixes wallet sending when fee estimation would otherwise fail with Fallbackfee is disabled
• keeps the fallback fee configurable through %LOCALAPPDATA%\VargaMesh\vargamesh.conf
• serializes Core startup so concurrent wallet/UI requests cannot start duplicate daemon processes
• adds a local desktop-runtime.log with the exact non-secret Core launch arguments for diagnostics
• replaces the single-file portable SFX build with a portable ZIP package to avoid stale %TEMP% extraction/cache reuse between test builds
• adds a packaged app.asar CI guard that fails the build if stale -bind, -rpcbind, -rpcport, -listen, or -server launch arguments reappear
• release workflow validates that the Git tag matches package.json

Sending VMESH

VargaMesh Desktop supports VMESH transactions through the bundled VargaMesh
Core wallet.

Before sending, the application performs address validation and displays an
explicit transaction confirmation.

Transaction Fees

VargaMesh Core normally attempts to estimate an appropriate transaction fee
from recent network activity.

Because VargaMesh is still a young network and may have periods with relatively
few regular transactions, there may not always be enough data available for
automatic fee estimation.

VargaMesh Desktop therefore configures the bundled Core with:

fallbackfee=0.00001000

This corresponds to:

1 sat/vB
0.00001000 VMESH/kvB

The fallback fee is used when automatic fee estimation cannot provide a usable
fee rate.

This prevents transaction creation from failing with:

Fee estimation failed. Fallbackfee is disabled.
Wait a few blocks or enable -fallbackfee.

The setting is stored in the local VargaMesh Core configuration:

%LOCALAPPDATA%\VargaMesh\vargamesh.conf

Users may review or change this setting manually if required.

Cryptocurrency transactions are irreversible after confirmation by the
network.

Always verify:

• destination address
• amount
• selected wallet
• transaction fee

before approving a transaction.

For early testing, use small amounts.

---

Important VargaMesh Core v0.1.0 Note

VargaMesh Desktop currently bundles VargaMesh Core v0.1.0.

Core v0.1.0 requires an explicit P2P bind in the generated configuration.

VargaMesh Desktop creates a local Core configuration containing:

# Generated by VargaMesh Desktop v0.1.1
# P2P is public; RPC stays localhost-only.

server=1

listen=1
bind=0.0.0.0:29666

rpcbind=127.0.0.1
rpcallowip=127.0.0.1
rpcport=29667

addnode=217.154.93.20:29666
addnode=212.132.80.39:29666
addnode=31.70.81.5:29666

# VMESH transaction fallback fee
# 1 sat/vB = 0.00001000 VMESH/kvB
fallbackfee=0.00001000

The generated vargamesh.conf is authoritative for:

• P2P binding
• RPC binding
• RPC port
• bootstrap peers
• wallet fallback-fee configuration

RPC remains bound to localhost and is not intended to be exposed publicly.

VargaMesh Desktop launches Core using only the required runtime arguments:

-datadir=<path>
-conf=<path>
-printtoconsole=0

Network binding and fee-policy arguments are intentionally not duplicated on
the Core command line.

---

Windows Data Location

VargaMesh Desktop stores blockchain, wallet and Core configuration data in the
normal Windows user profile.

Default location:

%LOCALAPPDATA%\VargaMesh

The Core configuration is stored at:

%LOCALAPPDATA%\VargaMesh\vargamesh.conf

This applies to both:

• installed version
• portable ZIP version

The portable build does not store live wallet data beside the executable.

---

First Start

During first startup VargaMesh Desktop:

1. determines the local VargaMesh data directory
2. creates a safe initial vargamesh.conf if one does not already exist
3. configures public VargaMesh P2P connectivity
4. keeps Core RPC bound to localhost only
5. configures the VMESH transaction fallback fee
6. launches the bundled VargaMesh Core daemon
7. waits for the Core RPC service
8. authenticates using the local Core cookie
9. retrieves blockchain and network state
10. displays synchronization progress in the Desktop interface

The generated configuration includes:

fallbackfee=0.00001000

This provides a fallback transaction fee of:

1 sat/vB

when VargaMesh Core does not yet have enough network history for automatic fee
estimation.

Initial blockchain synchronization may take time depending on:

• current chain height
• available peers
• network connection
• disk performance
• CPU performance

Closing VargaMesh Desktop requests a clean VargaMesh Core shutdown.

---

Windows Artifacts

• VargaMesh-Desktop-v0.1.1-Windows-x64-Setup.exe
• VargaMesh-Desktop-v0.1.1-Windows-x64-Portable.zip
• SHA256SUMS

The portable ZIP must be extracted before launching VargaMesh Desktop.exe.

Bundled node: VargaMesh Core v0.1.0.

---

Status

Pre-release / public testing

This release should be tested with small VMESH amounts before relying on it
for larger wallet transactions.