Divi 3.0.0

Release Notes - Hard Fork Update.

This MANDATORY update activates hardfork features on time stamp 🕰️ 1692792000 (Aug 23, 2023), deprecates masternodes, and introduces significant new features, improvements, and fixes.

🚀 New Features

• Activation timestamp for new hardfork features: 🕰️ 1692792000 (Aug 23, 2023)
  • Masternode deprecation
  • (BETA) New opcode activation: OP_LIMIT_TRANSFER, OP_CHECKLOCKTIMEVERIFY
    • Hyper-cold UTXOs (can only send to even-deeper cold storage FIRST)
    • Refund-only transactions for in-store purchases (so store attendants can't spend)
• Introduction of Multi-wallet support (loadwallet)
• Improved vault funding by allowing the creation of multiple utxos simultaneously (Repetitions)
• Improve vault withdrawal to support address specific vault withdrawal (debitvaultbyname)
• Added the option to treat accounts names as labels (i.e. restrict spending within labels only)(-accountlabel)
• Added support for sending with flags (sendtoaddress, sendtomany, receiver_pays, sweep_funds)

🛠️ Improvements

• Resolved balance edge cases with zero confirmation spending
• Significantly improved testing coverage
• Improve RPC management for lock/unlock commands (unlocking from staking mode now reverts to original state after unlocking for spending)
• Significant refactoring of the core chain extension logic
• Extensive addition of interfaces for testing and decoupling
• Added automatic rescan after a seed restore
• Improved Vault Staking on withdrawal: Coin Selection Algorithm spends the youngest UTXO
• Encryption of wallet no longer requires daemon shutdown
• Initial steps towards third-party db integration for wallet data (SQL, Postgres, Mongo, etc.)

🐛 Fixes

• Fix crash recovery method bug that results in nodes failing to move past block 100 (-recoverblockdb)

🔄 Changes

• Move initialization settings flags into the Settings state
• Deprecate mempool indices for tracking 'nominal' balance changes

Update Divi Core 2.5.1

Release Notes

This non-mandatory major update includes 3646 commits that benefit all nodes operators. You are encouraged to update and take advantage of staking optimizations, fee modifications, thousands of commits, including new features, enhancements, stability, and bug fixes.

🎁 Features

• Added lookup for transactions by bare txid
• Optimized fees for transactions
• Added customizable coin control algorithms (developer tools)
• Added address indexing for vault UTXOs
• Updated default stake split value to 20k for vaults

🎉 Enhancements

• 1000+ hours of refactoring

• Removed getgenerate and gethashespersec RPC methods

• Removed transaction block logic

• Removed 32bit binaries from deployment in windows

• Removed RPC functions settxfee and sendtoaddressix

• Removed RPC function masternodeconnect

• Removed TON of globals

• Fixed RPC bug in coin availability to display proper balances

• Renamed Bitcoin Miner to Generate Divi in developer notes

• Fixed inconsistency in camel case naming of some files

• Updated URL for deployment from deprecated Divicoin to updated Divi Project

• Separated help and license info into its own file

• Renamed Broadcast to RebroadcastWalletTransactions

• Move additional constants into default values header and made them constant expressions

• Separated shutdown signals for unit tests from shutdown signals for production

• Moved P2P initialization into net.* files

• Renamed variable names to be more explicit in their intent

• Move private header constants into the source

• Fix accidental newline ending version back to Linux default

• Provided explicit naming for block tree database keys

• Encapsulated masternode data sharing methods as part of masternode module

• Encapsulate access to spork manager

• Encapsulated wallet spends in spent output tracker

• Encapsulated initialization of peer to peer connections

• Encapsulated clean up of peer to peer connections

• Partial encapsulation of coin database updates

• Partial refactoring of chain management

• Simplified dependencies on various globals and replaced them with injections

• Abstracted BlockTransactionCollector

• Abstracted ProofOfStake module

• Consolidated global settings for logging

• Added default logging for various classes

• Extracted nodes stats computation

• Extracted network usage stats logging

• Extracted local networking address helpers

• Extracted orphan transaction monitoring

• Extracted thread management helper logic

• Extracted index database updates into index database collector

• Separated various classes into their own files

• Extracted node class into a separate file

• Extracted masternode modules and masternode RPC features into separate files

• Moved masternode broadcast factory to its own file

• Partial decoupling of node state management from node construction and destruction

• Decoupled masternode on disc data loading and saving from instantiation

• Improved thread-safety with node instances by ensuring proper discard of reference copies

• Improved stability of ZMQ tests

• Improved mutex locking debugs and limited lock requirements

• Improved masternode synchronization

• Skip chain sync check for pings owned self

• Consolidated masternode message processing as processing through the masternode message module

• Updated vault tests

• Added tests for address indexing and spent output indexing

• Added tests for removal of transaction indexing

• Added tests for auto-combine dust

• Added tests for masternode restarts

• Added getter method for lottery winner candidates

• Added RPC function for banning peers

• Added FakeWallet class

• Added tests for monthly backups

• Added mempool tests for bare txid

• Added multi-wallet tests

• Added FakeBlockchain class for testing

• Added test for main-net hash proofs

• Added expectation people will appreciate this

MANDATORY UPDATE by December 31, 2020

Release Notes - Hard Fork Update.

This mandatory upgrade includes several enhancements, bug fixes, and establishes a new testnet.

🎁 Features

Major Features

• Staking Vaults (Along with endpoints to fund/defund vaults and require minimum vault deposits [antispam])
• Uniform Lotteries (No Address Repetition)
• MN remote broadcast & MN remote start

Minor Features

• Lottery Data now viewable per block height
• Improved Randomness for Proof-of-Stake generation
• No more needing to restart node for MintableCoins to switch from false to true
• Autocombine stakes can now be disabled in the configs by setting -autocombine=0
• Stake split threshold (100k default) needs to be set in the divi.conf file
• Other changes

🎉 Enhancements

• Improved validation of masternode pings & masternode broadcasts
• Lightened block index by removing redundant lottery data
• Added tests for OP_META transactions
• Optimize timestamp selection for proof-of-stake
• MN blockhash based reward attribution caching for reduced memory footprint
• Re-enabled python test frameworks for quality assurance
• Grouping settings parameters into a settings class
• Loads of automated Testing & Refactoring

Description

• Staking Vaults: Allow delegation of the ability to construct proofs-of-stake to an exclusive third party in a trustless way. One use case is to have two people who know each other to stake on the same node without giving up ultimate control of their funds.

• Uniform Lotteries: In the hope of making lottery rewards more uniform, addresses that have previously won a lottery reward will not be eligible for the next four lotteries. They will resume being considered for a lottery reward afterwards.

• Remote Start: Allows the server on which a masternode is hosted to use their own keys for managing the masternode. The user can now locally pledge the funds with a signature instead of needing to provide a private key.

• Remote Broadcast: Allows delegation of the broadcast step when creating a masternode in order to allow a more streamlined deployment UX

Notes

#This is a Hard Fork update!

Nodes should both (1) remove the mncache.dat & mnpayments.dat from their data directory, and (2) start up with -reindex if running this daemon for the first time. The updates to the masternodes and block indices can trigger an error if disk files are not regenerated by the daemon; hence the indicated steps 1 & 2.

MANDATORY UPDATE

This is a MANDATORY update. Failure to update will cause nodes to fork at block 1,051,200 (1 MILLION, FIFTY-ONE THOUSAND, TWO HUNDRED).

Release Notes

This mandatory upgrade includes several enhancements, bug fixes, and establishes a new testnet.

🚀 Features

• New testnet

🎉 Enhancements

• Block full unlock from unlocked for staking for security
• Refactor codebase to extract intent into named functions
• Extract logging and directory functionality separate files
• Enable monthly wallet backups on a thread not just on startup
• Remove QT & remove Zerocoin from the core (where possible)
• Refactor script evaluation for clarity & modularity
• Remove dead code
• Added google test
• Partial port & re-engineering of the BIP9 activation mechanism
• Refactor Script Interpreter for readability
• Refactor subsidies for clarity

🐛 Bugfixes

• Removed a seed phrase dump occurring on failed recovery
• Removed BTC typos where it should say DIVI
• Guarded against potential masternode vulnerabilities
• Fixed Testnet port issues
• Fixed block subsidy issues
• Redefine block subsidies to avoid block collisions & correct minting

Divi Core Version 1.0.8 Changelog

This mandatory upgrade enhances the overall security and optimizes the Divi core daemon

🐛 Bugfixes

• Fix issue where Windows versions compile to debug version by default, causing a much larger file size than the other platforms
• Exclude unstable nodes

Divi Core Version 1.0.7 Changelog

🎉Enhancements

• Change client revision version (both numbering and string values where present) form 4 to 7 in both configure.ac & clientversion.h
• Add a function to determine the collateral amount from int-encoded masternode tier
• Employ function described in (2) inside CMasternode::Check() && to compare present collateral to expected collateral
• The definition of IsCoinSpent was expanded include a comparison argument to a reference collateral amount for use with the function defined in (2)

Divi Core 1.0.4 Changelog

• move functionality is deprecated.

Version 1.2.2 Changelog

Version 1.2.2 provides a hotfix for a rate-limiting issue caused by Digital Ocean's API and adds a few additional, masternode-related features.

Bugfixes

• Rate limiting issue
• Payment token blocks deployment of higher tiers
• Show 'redeploy' for masternodes without droplet

New features

• Improved remote status retrieval
• Add masternodes tab to the settings page
• Backup/Restore: Easily backup and restore your masternodes manually
• Clear Cache: Get rid of pesky, old masternodes from the cache so they don't appear on a newly restored wallet

Changelog

• Version 1.2.1 fixes an issue that caused balances to display as '0' unless the wallet was currently unencrypted.

This minor upgrade introduces the PayPal integration that allows users to pay for hosting their MOCCI-deployed masternodes in the cloud.

A lot of testing and development has gone into creating a payment flow that makes sense for users and is as easy to use as people have come to expect Divi software to be. Still, there are no doubt things we missed, and we urge all our users to report any bugs or issues to our Telegram support channel.

It is recommended that you subscribe and upgrade your MOCCI subscription as soon as you download the update to avoid any interruption in masternode rewards.

Changelog

• MOCCI UX improvements.
• MOCCI Dismantle optimization. Dismantling now takes about 2 seconds.
• PayPal subscription to MOCCI.
• UTXOs only combine on MOCCI deployment only if the “Transaction too large” error occurs. This update will save staked coins from resetting their age and assist in subsequent deployments.
• Export transaction history to CSV.
• Updates to remote security infrastructure.
• Remove incorrect “Additional bonus” percentages from MOCCI modal.