Releases: Actinium-project/Actinium
0.18.6.0-BETA
New features, bugfixes, and performance improvements
Recommended Update
For a detailed description of all changes check our release notes document.
Installation
Windows: unpack the ZIP file and double click Actinium-qt.exe
macOS: double click the DMG file and move the Actinium- icon to Applications icon to start the installation.
Malware Reports
Windows ZIP
SHA256: 8c31c6c1eaceb21a223bc291df1018482c31fabb025bceae350bbef71f8a1c5d
Report
macOS DMG
SHA256: * f7392893387a1a3b6eb2121bd635d42827f9da96b1d07222c7b4c0c291e026f0*
Report
0.18.5.0
Atomic Swaps on Testnet
This release contains the new testnet chain parameters and should be used for testing of the new atomic swaps functionality.
The NG variant of Actinium doesn't support the deprecated (now removed) RPC methods which are needed for atomic swap tools to work. To use atomic swaps you must run this release.
Malware Reports
Windows ZIP
File: Windows.zip
SHA256: 4e0e36bb2080db23c90155d2df2bb06cbea1325b18c856d97eeb61899ae52cf6
Report
macOS DMG
File: Actinium-Qt.dmg
SHA256: 449748e0315097ab59952eacc981d89c852f348a8d2dcde985470df1fac514f8
Report
v0.18.4.0
Bugfixes + Tor update
This release contains numerous bugfixes ported from Bitcoin as well as the latest Tor version 0.3.4.9.
If you are following the new branch based on Bitcoin this update is not relevant to you.
Virus Scan Reports
macOS DMG
SHA256: c7613325144eac7526dceaadebabe6e377f8b66978caa08e38dd7aac82709d5f
Report
Windows ZIP
SHA256: ef131f91ed9ababfa156ef2b8fbdb2067f778000835890807dac1dcfd33ee3d7
Report
0.18.3.1
Seed nodes support
This is a non-mandatory release that supports seed nodes.
The nodes participating in the Actinium network synchronize their peer tables via fixed nodes. Those nodes have their IP addresses built into the wallet's code thus making them directly available. And as long as their operators take care of them there is seldom a reason to change anything.
However, seed nodes offer a more dynamic and decentralized approach by continuously scanning the network, updating their internal peer tables, and answering DNS-requests from other nodes.
For more info on how they operate consult the readme of our acm-seeder project.
VirusTotal Reports
Windows ZIP
SHA256: f842b9089bb97c98d8a15cd077b2a3da604a69b9b5c8e93ad7ff8a5edd588c57
Report
macOS DMG
SHA256: 52544612447b1bd9c3031051fbaec14695b2b8708a48059f3e6732174ea41e4b
Report
0.18.3.0
UI design, code stabilization, and new RPC commands
User Interface
Main window
Send funds
Request payment
New RPC commands
More info on getblockstats
Code stabilization
Numerous bugfixes and improvements ported from Bitcoin and/or Litecoin.
Virus-Scan Reports
Windows ZIP
SHA256: ca543cb3596d7dd1fc28ce0d0077e321fb403e72ab1372f346f48ce168882e6d
Report
macOS DMG
SHA256: b44de10beb6622ffa88f03e8211bbc078fa8bce6f4b1dbe1802dcbfa71a1eed1
Report
0.18.2.0
Stability Updates
This release contains several bugfixes and stability updates ported from Bitcoin & Litecoin. It also contains a small fix regarding the qr-code URLs to make it compatible with the upcoming Trezor HW integration.
The same fix also was deployed in the latest version of the Android Mobile App.
Virus-Scan Reports
Windows ZIP
SHA256: da4fd6602f86b31a3582c01eb6b484224096b389e3065c887a1ef9046d142ce9
Report
macOS DMG
SHA256: 2e413c333c9555f7b4539b745a981b705b0d162a4e73fe178877f1fa2d0af877
Report
v0.18.1.0
Bugfix Release - Recommended Update
This release contains several improvements and one important security fix ported from Bitcoin.
Further improvements are ZeroMQ v4.2.5 and a new RPC command: getnodeaddresses.
Virus-Scan Reports
Windows ZIP
SHA256: 2dfc7d4f5986f9dd1f2cf595a9580144f1a9ec9b1ec5c20d0fd17f631a4d0de3
Report
macOS DMG
SHA256: * 2edfc77eb3ce7fe4cb3a43d8765455931aee097aa57f9d7a5806c8fa59c0d615*
Report
0.18.0.0
Mandatory Update - Hard Fork at height 85,000
LWMA Diff readjustment algo & reactivation of the original block reward
This release contains:
- Latest patches & updated from Litecoin project
- LWMA Difficulty Readjustment Algorithm will replace our current algo, Dark Gravity Wave v3 at block 85,000
- At the same block we will switch back to our original block reward of 50ACM
The hard fork will happen in 9 days approx.
Please, update as soon as possible!
Virus Scan Reports
macOS DMG
SHA256: b923bf29ee7499a80059f075a3035dca31203d65906deddaf2f2045c3944ddbd
Report
Windows ZIP
SHA256: 9ece5c3a7f04368ceef282c3e8fb550dd83786af7ffbbd0a5f5617188b9d13de
Report
FAQ
Q: What is a hard fork?
A: A hard fork is a permanent change in the Consensus Rules. Therefore all nodes that want to continue supporting the updated rules must install the new version. However, unlike Bitcoin and other, bigger projects we don't face the additional political problems.
Q: Why did you change the block reward amounts?
A: Our coin began as a Litecoin-based Scrypt algo mineable currency. But due to the lack of proper, ongoing mining support we decided to switch to a more GPU-friendly algorithm, Lyra2z. However, because of negative past experiences with ASIC-miners that jumped the chain on & off, we decided to lower the reward to 40ACM after we've switched to Lyra2z. In hindsight, we shouldn't have changed the reward rule at all. Therefore, we are now going back to the original Consensus Rules regarding the block reward. This decision wasn't made by one person but in discussion with the community. We think that our GPU-miners deserve the original block rewards.
Q: When will the hard fork happen?
A: At block 85,000. In 9 days approx.
Q: What would happen to my coins if I don't update?
A: Nothing. Coins never leave the chain. But you wouldn't be able to trade them, or mine new coins, as exchanges and mining pools are currently switching to the new version.
Q: But I have my coins in my mobile wallet!
A: No, you can't have your coins in your mobile (or any other) wallet. Coins never leave the chain. What you have are the private keys that allow you to access them. Anyway, if you only use a mobile wallet to access your coins the hard fork won't affect you at all. Mobile wallets don't download the whole chain but only the block headers. And the predefined seed nodes for mobile wallets have already been updated to the latest version.
0.17.5.0 - TOR Integration & Sync Fix
STABLE Version - Integrated Tor & Synchronization Fixes
Synchonization Fix
This release contains a fix which helps to properly synchronize the chain. Several users have reported Script-Parsing Errors during initial blockchain sync.
TOR Integration - Anonymous Networking
Additionally, this release contains integrated Tor Libraries. If you are only interested in solving the synchronization problem you can safely ignore Tor as it's disabled by default. Otherwise, visit this Wiki for more information on how to use it.
Virus-Scan Reports
Windows ZIP File
SHA256: 1f927eed8a9b2b17ff68a9ec03f9debbd9527d2d6e449d274c73396cf98dbcef
Report
macOS DMG
SHA256: 53cc7beeb25dbe2661efd0ccd0d9a5a420103f886a8e34ccd103c4be38b55507
Report
0.17.4.0
SegWit & Bech32 Release
This release supports SegWit addresses by default.
Read below FAQ before installation!
Whenever a new address is generated it will be prefixed with P instead of the legacy prefix N.
The Request Payment Tab offers the option of generating Bech32 addresses as well.
However, do not use Bech32 for mobile payments as the mobile app won't be able to scan them.
Only use SegWit addresses for mobile payments.
SegWit Payment Request
Bech32 Payment request
For users who don't want to use SegWit there are two options for default address and change-type (the addresses generated automatically by Wallets or ACM-daemons):
addresstype=legacy
changetype=legacy
Virus Scan Reports
Windows ZIP file
SHA256: 3dc2f46cbb33459e18a015e9e46bafe1a0e18257c1a4bd59cdfefd38103529fb
Report
macOS DMG
SHA256: d7217bbf261a3536d60b46ac32e15e280672f787e0e7e068bc588e970e5b1dec
Report
FAQ
Q: Can we send funds from legacy addresses to SegWit and/or Bech32 addresses?
A: Yes, it works both ways. There is no problem to send funds between all those address formats.
Q: I am a mining pool operator, do I have to update the daemon for SegWit support?
A: As long as you are running a version >=0.17.2.0 all you have to do is to activate SegWit support in your mining framework (YIIMP or similar). But you don't have to do this. All miners who only support legacy addresses will simply continue to mine blocks that only contain those address types. However, from economical point of view it's always better to support the widest range of your customers.
Q: Can I send funds to SegWit addresses with my mobile application?
A: Yes, the mobile app is able to scan SegWit addresses (P-prefixed). However, Bech32 addresses (with acm1 prefix) can not be scanned by the mobile application.
Q: Why do we support SegWit?
A: Although our network is very small and not as congested as Bitcoin's we need SegWit support for our future Lightning Network onboarding. SegWit not only makes transaction payloads smaller, but also fixes some very important security issues like the transaction malleability. Without SegWit we wouldn't be able to develop and port tools needed for our future Lightning Network implementation.
Q: What are those Bech32 addresses?
A: Bech32 or "native SegWit" addresses are the only address types which can be used in our future Lightning Network implementation. For more detailed info and the many advantages of Bech32 addresses, please, read this article.
Q: I have a problem with syncing the chain. My wallet is crashing with a weird message!
A: In some rare cases users have experienced synchronisation problems. One way to avoid such problems is to download the bootstrap.dat file and put it into the Actinium folder. Please, don't forget to remove any traces of previous data except your wallet.dat. Delete all existing folders & files, even the Actinium.conf file (you can bring it back later). Then start the Wallet and let it unpack bootstrap.dat and resync with the network. This operation will take some time, so be patient.