Skip to content

Releases: Raptor3um/raptoreum

41803f0
Compare
Choose a tag to compare

THIS IS A MANDATORY RELEASE YOU HAVE A MONTH FROM TODAY TO GET UPDATED FOR BLOCK 420420

From block 420420 rtm "futures" will be live which brings changes to the following RPC functions:

createrawtransaction with additional fields being available for the addition of block based or time based locktimes.

sendtoaddress with additional fields being available for the addition of block based or time based locktimes.

*Remember to avoid setting both locktimes as negative or you will freeze the coins for ever! More documentation on the docs site soon!

Also, we have added our fee setting spork so we will never find ourselves in a "gas" crisis.

Apart from the above main features, we have a speed up for the syncing of clients using a POW cache, a much smaller file that can significantly increase the speed of syncing a wallet!

Additional various functional fixes have been added to the QT wallet that include multiple bug fixes as well as additional optimizations for wallets with large numbers of transactions and improved thread handling.

Apart from the above mentioned RTM changes, this update brings a plethora of changes from its updates to Dash code:

The full details can be found here

They involve numerous RPC changes as well as backports form BTC 17 and 18 as well as updates and upgrades to most of the Dash features!

DUAL CHECKSUMS FOR EACH RELEASE IS PACKAGED WITH THE OS APPROPRIATE ARCHIVES INSIDE EACH ZIP! ALWAYS CHECK BOTH! THERE HAVE BEEN INSTANCES OF MALWARE IN FILES MODDED TO MEET SINGLE CHECKSUMS!

COMPULSORY BOOTSTRAPS AND POWCACHE FILES TO SPEED UP THE NEW SYNC AND STAVE OFF A REINDEX ARE HERE POWCACHE CAN BE USED ON ITS OWN AND SIGNIFICANTLY SPEEDS UP A SYNC FROM SCRATCH! JUST DROP THE POWCACHE FILE IN THE DATA DIRECTORY! EITHER USE THE BOOTSTRAP WITH THE WHOLE SHEBANG OR JUST DROP THE TINY POWCACHE IN AND SYNC FROM SCRATCH WHICH SHOULD NOW TAKE 1-2 HOURS AS OPPOSED TO EARLIER

Compare
Choose a tag to compare

Updated builds for the Futures with a Dash of Fees Testnet

Fixes an issue with nodes deadlocking during the handling of new nodes being added to the network.

ARM 32 and 64 support confirmed working on RPI 2-4 as well as several more custom set ups!

NOTES FOR 1st gen builds:
Changes, Fixes, and Features
This is a large two stage update which brings our codebase up from DASH 15 to DASH 17 as well as providing multiple RTM specific features in stage one. Stage two will be bringing multiple changes on how RTM binaries operate. Too many changes and fixes to list so will just give a very general and brief list including RTM specific changes and features. Links to DASH release notes at bottom if you want all the details on those.

Bounties for participating in testing will be posted on the RTM Discord on Monday the 4th of April!

Stage 1:

Raptoreum Specific Changes

Futures code: Input selection. Futures transactions no longer require the manual selection of specific inputs to use.

Integrate future transaction creation into send (remove Future tab).

GUI bug fixes: SmartNode lists sorting properly. Transactions from “Watchonly” addresses display correctly.

Performance improvements: Introduction of POW powercaching which speeds up sync by several orders of magnitude. Initial sync will still be slow but anything post that is now drastically improvced.

UI changes and optimizations.

Added hard fork block for futures.

Added Futures disable option (SPORK).

Added Fee adjustment spork for futures and upcoming asset transactions.

DASH 15 > 17 Notes

Network fixes and performance improvements resulting in less load, greater efficiency acroos nodes / Smartnodes.
Improvements to PrivateSend mixing algorithm.
Increased privacy and security for PrivateSend.
PrivateSend is now CoinJoin.
Various RPC changes.
Various CLI changes.
Build system and depends upgrades.
Python 2 has been discontinued for all tests and tools.
Opcode updates.
Crash fixes.
Added translations.
Dash Release Notes

Dash 16.0.1 (major release): https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.16.0.1.md
Dash 16.1.0 (minor release): https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.16.1.0.md
Dash 16.1.1 (minor release): https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.16.1.1.md
Dash 17.0.2 (major release): https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.17.0.2.md
Stage 2: WILL HAVE ITS OWN RELEASE! SO IT IS NOT HERE YET!
Raptoreum Specific Changes:

• Update crc32c subtree (ref: bitcoin/bitcoin@fac1c13)
• Update univalue subtree (ref: bitcoin/bitcoin@3043193)
• Update leveldb subtree (ref: bitcoin/bitcoin@20a6bab)
• refactor: depends build env
• refactor: build configuration (comply with autotools 2.69)
• Integrate univalue into our build system (ref: bitcoin/bitcoin@0f95247)
• crc32c build system integration (ref: bitcoin/bitcoin@9ebdf04)
• fixed placeholders at QT
• Support to checking HW functions at compile-time
• Support for HW 256-bit RNG (where available)

This is a fairly massive update to how binaries operate and thread and should give RTM a considerable boost.

Compare
Choose a tag to compare

This release mainly introduces additional stronger DNS seeds as well as updated caching to improve sync times.

This release is mandatory for smartnodes from May 3rd 2022. As well as regular nodes from May 10th 2022

This is not a mandatory release however it is for very highly recommended for Smart Node operators as the improved networking should lower the chances of accruing PoSe Ban score.

Main differences between this and 1.2.15.2 are:
A) Significantly improved sync times
B) Significantly improved networking making PoSe accrual less likely!
C) Improved in client CN code handling.
D) Fix of an as of yet undisclosed upstream bug!

Compare
Choose a tag to compare

this is a pre-release, do not use this on mainnet

Compare
Choose a tag to compare

Minor update to ensure a smoother transition for including smartnode payments in blocks.

Additional possible fix for clients locking following complete net failure.

6655fcb
Compare
Choose a tag to compare

Raptoreum's first mainnet client