Skip to content

Shark Net - v0.3.0.0
Compare
Choose a tag to compare
@Sn1F3rt Sn1F3rt released this 01 Jan 13:28
v0.3.0.0
9931ca5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Xolentum Release v0.3.0.0 - Shark Net

What's new?

  • Introducing transaction proof-of-work, which will be effective post fork v4, at height 180000. In simple words, transaction PoW has been implemented to prevent spamming of transactions on the network, forcing users to mine a transaction before they are relayed on the network. For technical documentation, please refer to our whitepaper which will be released shortly.

  • Sub-addresses prefix has been changed to S to avoid conflicting with the sub-addresses of Monero. This comes with a few things to note. Firstly, once users upgrade to v0.3.0.0 of wallet CLI, they can issue the command address all and find their new address. Users on v0.2.0.0 can still send transactions to the old addresses with the 8 prefix and they will end up in the right addresses, however that is no longer possible after upgrading to v0.3.0.0 (which is mandatory for the v4 fork). Hence, users are recommended to update their sub-addresses as soon as possible.

  • Docker support is now enabled, which means you can run a Xolentum node using Docker. => https://hub.docker.com/r/xolentum/xolentum

Change-log

  • v4 fork at height 180000.
  • Sub-address prefix changed from 8 to S for mainnet.
  • Added Docker support for xolentumd.
  • Removed libnorm as a required dependency for Linux binaries.
  • Added the validate_address endpoint to daemon RPC
  • Added the already_generated_coins and base_reward fields to the get_info endpoint.
  • Removed RPC login requirement for enabling CORS in restricted RPC.
  • Various other updates from upstream.
  • Minor bug fixes and improvements.

Contributors

Contributors for this release are @ngeojiajun and @sohamb03 and the Monero Developers.

Using

No special requirements, binaries can be used as-is. (Check the third under Change-log above)

Users can also pull the Docker image from here.

Verifying

SHA-256 checksums of the binaries are as follows:

97e280408e178c58f34f63552b6203d45747d6dbc26364b860188e8a656bba05 *xolentum_v0.3.0.0_linux.zip
71cecf7c48d1f3b2ba0d3b22b374e79cbf3ccd0e31c67adff2602ce1a4855c26 *xolentum_v0.3.0.0_macos.zip
dc35a58beb92e81ad9b2fb2aa36366a9aadfb2a539bcb27ea8be5c27ae691cb3 *xolentum_v0.3.0.0_windows.zip

The binaries have been signed by @ngeojiajun 's PGP key available at public-keys/sakura.asc in the repository. A .sig file has been shared for verification of the binaries. To verify the binaries, you have to download the .sig file for the platform you are using, and verify using GPG.

For example, on Linux, use gpg --verify xolentum_v0.3.0.0_linux.sig xolentum_v0.3.0.0_linux-x64.zip.

Assets 8
Loading