Skip to content

Releases: KingricharVD/vivo

Release list

v24.0.0.1

v24.0.0.1 Latest
Latest

Choose a tag to compare

View all tags
@KingricharVD KingricharVD released this 26 Sep 11:34
v24.0.0.1
d657063

New Version 24.0.0.1

Patched a Send Coins transaction that previously produced Fee needed > fee paid bug

922f94ca9f02d7ef5e8a2e101b44de02f4122183733f3b759e4754c39e07d9d9 vivo-24.0.0.1-x86_64-linux-gnu.tar.gz
97a6c9837a612bb3628cce12d10a4e9e44833911cf485a4a6040dbadb4360f60 vivo-24.0.0.1-win64.zip
68581fec0327573e11ac2873c229ce0be6e24a1d928caef289f066910f3320cc VIVO-24.0.0.1-macOS-x86_64-unsigned.zip
It is 27MB so will have to download off Google Drive HERE----> https://drive.google.com/file/d/1zTWzV6GWLuRyCoZtgyjugYLdOEPE5TZr/view?usp=sharing

Assets 4
Loading

v24.0.0.0

v24.0.0.0

Choose a tag to compare

View all tags
@KingricharVD KingricharVD released this 25 Sep 07:03
v24.0.0.0
d9be113

8601e493328ffac84847e9a29108cee211b9c6823c8d727b31edc470ff368f49 vivo-24.0.0.0-x86_64-linux-gnu.tar.gz
283bca53a56461b31827c08f646a1ad6794f9b80a28752cdab1ca90a3a972850 vivo-24.0.0.0-win64.zip

VIVO Core v24.0.0.0

Major Network Upgrade

VIVO Core v24.0.0.0 is a major release representing the relaunch and modernization of the VIVO network.

This release introduces a modernized Dash-derived codebase, updated VIVO branding and application identity, a new consensus reward schedule, deterministic masternode rewards, a new network protocol version, and the foundation for VIVO's next generation of development.

Mainnet users, masternode operators, mining pools, exchanges, explorers, and service providers must upgrade before V2 activation.

V2 Mainnet Hard Fork

VIVO V2 is scheduled to activate at:

Activation Block: 2,176,696

This block is the consensus hard-fork boundary.

Deployment Lead

Lead: approximately 7,200 blocks

The activation was scheduled approximately 7,200 blocks in advance to provide node operators, exchanges, pools, explorers, masternodes, and other infrastructure providers time to complete the upgrade.

Nominal Activation Time

October 2, 2026 at 01:01:50 UTC

The block height, rather than the wall-clock time, is authoritative.

Because blockchain block production can run faster or slower than its target interval, the actual time at which block 2,176,696 is mined may differ from the nominal activation time.

Release Information

Version: VIVO Core 24.0.0.0
Numeric Version: 240000
P2P Subversion: /Vivo_Core:24.0.0.0/
Network Protocol: 70250

VIVO Applications

The modernized VIVO distribution uses the following application names:

  • vivod — VIVO Core daemon
  • vivo-qt — VIVO Core graphical wallet
  • vivo-cli — command-line RPC client
  • vivo-tx — transaction utility
  • vivo-util — VIVO utility application
  • vivo-wallet — wallet utility
  • vivo.conf — primary configuration file

The VIVO URI scheme is:

vivo://

What's New

Modernized VIVO Core

VIVO has been migrated from its legacy codebase to a substantially newer Dash-derived architecture.

The migration provides a modern foundation for:

  • improved networking
  • deterministic masternode operation
  • updated peer management
  • modern wallet infrastructure
  • improved RPC functionality
  • modern build environments
  • future security updates
  • future VIVO protocol development

The project remains VIVO Core while retaining applicable Bitcoin and Dash open-source licensing and attribution.

V2 Consensus Upgrade

VIVO v24 introduces a new V2 consensus era.

The transition is activated by blockchain height.

The critical activation point is:

Block 2,176,696

At block 2,176,696:

  • V2 consensus becomes active
  • the new VIVO block subsidy becomes active
  • the new reward distribution becomes active
  • the one-time developer allocation is created
  • protocol 70250 becomes mandatory
  • legacy pre-V2 consensus behavior ends

Nodes must be upgraded before block 2,176,696.

Hard-Fork Boundary

The V2 transition uses an explicit blockchain-height boundary.

Block 2,176,695

This is the final block operating under the legacy pre-V2 consensus rules.

Block 2,176,696

VIVO V2 HARD FORK

This is the first block operating under the V2 consensus rules.

At this block:

  • V2 consensus activates
  • the new 1.00000000 VIVO subsidy becomes active
  • the 60% miner / 40% masternode distribution becomes active
  • the one-time V2 developer allocation is applied
  • protocol 70250 enforcement begins

Block 2,176,697

Normal V2 consensus operation continues.

The developer allocation is not repeated.

New Block Reward

Beginning with V2 activation at block 2,176,696:

Base Block Reward: 1.00000000 VIVO

The reward follows a scheduled 50% reduction every:

262,800 blocks

Reward Schedule

Era Block Reward
V2 Launch 1.00000000 VIVO
After 262,800 V2 blocks 0.50000000 VIVO
After 525,600 V2 blocks 0.25000000 VIVO
After 788,400 V2 blocks 0.12500000 VIVO
Next era 0.06250000 VIVO

The halving process continues according to VIVO consensus rules.

This provides VIVO with a predictable long-term emission schedule.

Block Reward Distribution

Beginning at block 2,176,696, normal V2 block rewards are distributed:

60% — Miner
40% — Deterministic Masternode

For the initial 1.00000000 VIVO block reward:

Recipient Reward
Miner 0.60000000 VIVO
Masternode 0.40000000 VIVO
Total 1.00000000 VIVO

Future halvings reduce the underlying subsidy while maintaining the V2 consensus reward distribution.

V2 Developer Allocation

At V2 activation block 2,176,696 only, the network includes a one-time:

1,000,000 VIVO Developer Allocation

This allocation occurs exactly once at the V2 consensus boundary.

It is:

  • not a recurring block reward
  • not repeated on subsequent blocks
  • not repeated at future halvings
  • specifically tied to the V2 activation block

Block 2,176,695 does not contain the allocation.

Block 2,176,696 contains the one-time V2 allocation according to the V2 consensus rules.

Block 2,176,697 returns to normal V2 block reward operation.

New Network Protocol — 70250

VIVO Core v24 introduces:

Protocol Version 70250

Before block 2,176,696, applicable pre-activation compatibility rules remain in effect.

Beginning at block 2,176,696:

  • peers below protocol 70250 are considered obsolete
  • newly connecting legacy peers below 70250 are rejected
  • already-connected obsolete peers are disconnected according to the V2 network rules
  • protocol 70250 and compatible later versions are permitted

This prevents obsolete VIVO nodes from remaining unintentionally connected across the V2 consensus boundary.

Upgrade Requirement

Operators should confirm their node reports:

/Vivo_Core:24.0.0.0/

and:

protocolversion: 70250

before block 2,176,696.

Activation Schedule

Setting V2 Value
Activation height 2,176,696
Last legacy block 2,176,695
First V2 block 2,176,696
Deployment lead ~7,200 blocks
Nominal activation date October 2, 2026
Nominal activation time 01:01:50 UTC
Required protocol 70250
Required release VIVO Core v24.0.0.0

Important

Block 2,176,696 is authoritative.

The October 2, 2026 01:01:50 UTC timestamp is the nominal activation time based on expected chain progression.

The blockchain may reach the activation height slightly earlier or later depending on actual block production.

Wallet Modernization

VIVO Core v24 includes the modernized VIVO wallet architecture associated with the new Core codebase.

Users upgrading from older VIVO software should preserve their existing wallet before performing any migration.

Before Upgrading

Back up your legacy wallet, especially:

wallet.dat

Keep multiple offline copies before attempting a wallet migration.

Do not delete your legacy wallet or legacy VIVO data directory until you have confirmed that your addresses and balances are accessible from the upgraded environment.

New VIVO Identity

The v24 release standardizes VIVO's software identity throughout the project.

The migration includes VIVO-specific:

  • executable names
  • application names
  • configuration names
  • package identity
  • desktop integration
  • URI handling
  • service names
  • RPC identity
  • P2P identity
  • GUI resources
  • splash screens
  • network-specific artwork

VIVO now identifies itself to the network as:

Vivo_Core

rather than exposing upstream Dash application branding.

Network-Specific Wallet Artwork

VIVO Core v24 supports distinct graphical identities for its individual networks.

Separate resources are included for:

  • MAIN NET
  • TEST NET
  • DEV NET
  • REG TEST

This makes it easier for developers and operators to visually distinguish production wallets from development and testing environments.

Masternodes

VIVO v24 moves the project to the modern deterministic masternode architecture provided by the upgraded Core codebase.

Masternode operators should not assume legacy configuration and operating procedures remain unchanged.

Before block 2,176,696, operators should:

  • upgrade to VIVO Core v24.0.0.0
  • verify blockchain synchronization
  • verify protocol version 70250
  • verify masternode configuration
  • verify collateral configuration
  • verify ownership/operator configuration
  • confirm deterministic masternode status
  • ensure firewall and network configuration are correct

Masternodes that remain on incompatible legacy software after V2 activation should not be relied upon for V2 network participation.

Mining Pools

Mining pools must upgrade before block 2,176,696.

Pool operators must account for the new V2 consensus rules:

  • activation height 2,176,696
  • 1.00000000 VIVO initial subsidy
  • 262,800-block halving interval
  • 60% miner allocation
  • 40% deterministic masternode allocation
  • one-time activation-block developer allocation
  • protocol 70250 network requirements

Pools should verify candidate block ...

Read more
Loading