Qortal Project

The future of blockchain platforms

User Tools

Site Tools


Sidebar

Qortal Project Wiki

Introduction

Project Model

Minting

Communications Plugin

Trade Portal

Voting System

Data Hosting

Hardware

Important Notices

Frequently Asked Questions (FAQ)

How-To Guides

Node Setup Guides

Third-Party Services

qortal_status_updates

Qortal Status Updates

This page will contain information about the current status of the Qortal project, any known upcoming additions, and whatever else to be aware of. The person’s messages being relayed referring to “I” is @crowetic FYI.

CURRENT CORE VERSION: 3.0.1

CURRENT UI VERSION: 1.7.0

January 13th

  • @here 3.0.1 auto-update has been SIGNED!!! Network should begin updating shortly! WOOOOO!!!!! REMEMBER - if you haven't updated your UI to 1.7.0 before now, you need to do that or older versions will STOP WORKING after 3.0.1 hits! ALSO - QDN 'go live' is set for TOMORROW, Friday, Jan 14th! This means you can start publishing WEBSITES AND APPS on QDN TOMORROW!!!!
  • I have updated the stop script commands in the announcement above - this one is newer and uses a slightly different method that should be superior, then falls back to the method of the one from yesterday. (We would suggest using this one as opposed to the other, but both of them should work, so if you updated yesterday it's not 100% necessary, just recommended.) We are doing final tests before the 3.0 auto-update I will post again once the transaction has been signed. This update is very unique, and so we will NOT be putting the release up on github until after the QDN go live takes place, to avoid any potential issues. So auto-update is the method to ensure you get the update as soon as possible.
  • I noticed today when attempting to update my Mac UI… it seems the auto-update from 1.6.2 (and probably 1.6.3) might not work in some cases. If your Mac doesn't auto-update, simply manually download the update from github or qortal.org, mount the dmg, and drag n drop the Qortal UI application to your applications folder, overwriting the existing, and you'll be good to go. From 1.7.0 on the auto-update should work regardless, apologies for the confusion.

January 12th 2022

  • There was an unforeseen issue with the old transaction version on the 3.0 core, we are going to have to put off the update until tomorrow. It was an issue with the update transaction itself. It will be resolved in the morning and we'll go to 3.0.1
  • This is one of the best announcements I have made in a very long time! ALL VERSION 3.0 PRE-RELEASE TESTS HAVE PASSED DEVELOPMENT INSPECTION! Version 3.0 Auto-Update transaction is being prepared now! The go live timestamp for QDN Data Publishing is set for 4 PM GMT on Friday, Jan 14th! I will post again once the update transaction has been signed by the required development admins! WOOO!
  • Here is a link to the new stop script that you will need for linux and mac to stop after 3.0. - https://cdn.discordapp.com/attachments/873564589109952552/930937250072653914/stop.sh

Here is an easy way to acquire it:

Linux:

rm stop.sh && wget https://cdn.discordapp.com/attachments/873564589109952552/930937250072653914/stop.sh && chmod +x stop.sh

Mac:

rm stop.sh && curl -L -O https://cdn.discordapp.com/attachments/873564589109952552/930937250072653914/stop.sh && chmod +x stop.sh

So the above commands from your terminal in the qortal folder. cd qortal first. (this is also on GitHub.)

January 11th 2022

@here - version 1.7.0 of the Qortal UI has been released!

EVERYONE will need to UPDATE TO THIS VERSION of the UI BEFORE 3.0 of the core is released, or the API key functionality and the new transaction version will NOT WORK. So this update is very important to get done before version 3.0 of the Qortal Core goes live (version 3.0 of the Qortal Core should be going live sometime within the next day or so.)

There are two plugins surrounding QDN - these two plugins will NOT FUNCTION UNTIL AFTER THE 'GO LIVE' TIMESTAMP WE SET WHEN 3.0 IS LAUNCHED - so do not worry when you see these non-functional plugins in the UI. I will make another announcement when 3.0 is live, and we have set the 'go live' timestamp, so that everyone knows the EXACT time that QDN transactions will be able to take place.

ENJOY!

https://github.com/Qortal/qortal-ui/releases

A few notes:

  • Windows and Mac - WILL auto-update as long as you're on version 1.6.3+
  • Linux - WILL auto-update if you're using the appimage version only for now, we will work on getting deb auto-updates back shortly.
  • Pi users - can now use the appimage version as well, and get auto-updates now too, and no longer need to build from source! - you CAN of course, continue building from source, and if you're running ELECTRON (not using the server/browser) it will auto-update as well. For our Pi images, you will use THIS version - https://github.com/Qortal/qortal-ui/releases/download/v1.7.0/Qortal-Setup-arm.AppImage - you can rename the file to ANYTHING you like, the next release will be called Qortal-UI-arm.appimage - that is what I suggest you call it. all you have to do, is download, right click the file, go properties, and security, and check the box to allow EXECUTABLE - I will write up a how-to guide on this for the wiki today.

January 10th 2022

Crowetic posted this in Discord today @ 3:07pm PST

@here - the updates that are coming in the next couple days are MASSIVE, we're talking about HUGE new functionality, BIG changes on both sides…

The new core will require API key for 'sensitive' API calls (this is a big and nice feature for added security, but requires some changes as well), this means even things like stop.sh will need to be updated. The core itself will auto-update, but the script will need to be manually updated before it will function. There will be MANY things that people will need to be aware of for this update.

This is BY FAR the biggest single update in Qortal history, so there will be a little bit of effort required from most people's environments to ensure it all goes well.

The new UI will manage the API keys automatically, but if you're using a headless system, there will be other considerations, I will give more details regarding everything once the new versions are out.

The UI will need to be updated before the core, so that the core 3.0 will work.

The UI version 1.6.3 should auto-update for Mac and Windows users, we're still working on linux. So linux users will need to download the new release.

Windows and Mac users should be the EASIEST overall for this, as both the core and the UI should auto-update and not have any major changes required on the user side, as long as they are on version 1.6.3 of the UI, and 2.1.3 of the core.

pi and QORTector users - will most likely want to SWITCH from using the UI update script, to using the newer .appimage file for the UI, this is a binary version of the UI, which will enable auto-updates on the UI side for the pi.

but the first time users will have to manually switch from using the update script, to using the new appimage. I will announce in detail how to do this AFTER 1.7.0 UI launch (which will most likely be tomorrow.)

you CAN use the update script like you have been before, to update the UI, if you prefer to keep building from source, but from source versions will NOT auto-update in the future, so it will be my recommendation to use the new ARM-compatible appimage binary for this version and beyond. (This is also what I will be modifying the QORTectors to use from here on out.)

essentially, just STAY AWARE AND PREPARED, and watch for my announcements, we will be announcing how to do things, and making changes to the wiki to reflect all the new additions as everything is updated and guides are created. Until then certain environments may have a little more effort required than others.

NO MATTER WHAT - if your node is running, it will auto-update to 3.0 unless you have updates disabled. So be sure you have the NEW UI setup first, if you're not running a headless machine. The new stop script if you are.

More details coming soon. Thanks!

December 13th 2021

Core version 2.1.2 auto-update has been signed. This update was was to make sure that Qortal's version of log4j was not affected by the new exploit. We were pretty sure it was a very low likelihood anyway, but made a change to ensure that it was 100% not able to be taken advantage of.

December 9th 2021

UI version 1.6.1 is released - UI does not update automatically so you’ll need to run the UI installer (just install on top of the existing version now - you don’t need to delete anything)

December 8th 2021

Core version 2.1.1 is live which fixes the bug with the ACCTv2 code

November 24th 2021

Core version 2.1 is live which includes:

  • Added LitecoinACCTv2 and DogecoinACCTv2 with sleeping AT support
  • Switched new listings to use ACCTv2 by default
  • Fix for zero timestamps in trade history
  • Default min level for block submissions increased to 3 (to reduce block candidates)
  • Increased frequency of automatic repository maintenance attempts (now around twice as frequent)
  • Add API option to return inverse price (thanks to QuickMythril)
  • Updated BTC electrum servers (QuickMythril)
  • Added some German translations (thanks to Tocoolmh58)
  • Added another bootstrap host
  • Include the initial peers when creating bootstraps
  • "Lists" feature is now generic (in preparation for data hosting)
  • Improved trade bot backups so that the current order being bought is included
  • Prevent any kind of trading unless the blockchain is fully synced

October 13th 2021

Core version 2.0 is live which creates greater ease of use and scalability: automatic bootstrapping, older block data archived, top-only sync nodes, backup and restore for trade states and minting accounts, etc. Read more here: https://qortal.org/qortal-2-0-is-here/

August 1st 2021

Qortal now supports DOGE both in local wallets and on the Trade Portal! RVN then ARRR were to be next prior to going to community to vote on coins to implement after RVN and ARRR. We have since decided RVN will wait until sometime after version 3.0 and we can’t support ARRR until the Pirate Chain implements locking transactions. We also decided against DGB implementation due to lack of community and lack of Electrum servers. Sponsorship and Minting system modifications, voting system, and the App Store are on the priority list after version 3.0 is launched.

June 2021

DevTeam is focused on developing version 2.0 for greater scalability. DevTeam is considering changes to the minting and sponsorship system to combat the gaming and strengthen its integrity. See Future Modifications page for more info.

May 2021

Qortal consists of Cross-Chain trades with Litecoin, in the Trade Portal. BTC wallet exists but BTC trades are not live in the Trade Portal.

Q-Chat is live. It is extremely under-developed so please bear with us as we get this massive project going!

The mainnet Genesis block was launched on 6/29/20. The basic Trade Portal was launched on 8/6/20. BTC trades were too slow and expensive so LTC was implemented. BTC trades have been removed at this time. BTC and LTC wallets remain an on-chain feature and secure way to store these coin! Voting System is the next big development to be implemented. Then the community can vote on things like what changes to make on the Sponsorship System and what coins the Dev Team should implement next on the Trade Portal.

The next big development will be the Voting System. Thereafter, Qortal will be able to be truly community-driven as it has always been intended to be!

What else do we have now?

Authentication System: Qortal's authentication system (which is currently utilized for obtaining the authorization by which transactions may be carried out on behalf of a specific Qortal account). The authorization system does not require a centralized database and does not send any private information that could be utilized to gain authorization over an account if the information is ever sent anywhere outside of the local machine running Qortal. This means that the authorization system has no centralized oversight needed and as such, is much more secure than a typical centralized authorization system that we see being utilized with nearly every service on the Internet.

When utilizing the Qortal authentication system, a centralized service provider may allow any Qortal user to utilize their centralized service, WITHOUT the need to create an 'account' within the service itself. Any Qortal user (unless decided by the service provider to only allow certain users which is also an option by way of the existing 'groups' system) may make use of the service, without any need for any other account creation and subsequent need for remembering user/password for each individual provider (like we have with the Internet currently.)

Soon To Come

Future Options (applications and UI plugins): The options below could be built now to be utilized on the Qortal Network. These options could be built by any member of the community in coordination with the current lead developers or on behalf of a partner built for them by the current lead development team. With a small amount of effort the following ideas may be created within a short time. Qortal-Authorized UI Plugins: Using the method described above and the EXISTING UI, a plugin that would be self-installed after the initial UI installation could be created. This plugin would show up just like all of the 'default plugins' in the UI, but would do so after being installed by the user looking to make use of the plugin.

Qortal 'App Store' (future option): 'Non-default plugins' made by any user or service provider (meant to be inside the existing UI) could be published in a Qortal 'app store’. The apps allowed to be displayed as 'approved' will be voted on by the Qortal Network users. A 'private' app could also be created for government or internal company use cases.

Qortal-Authorized Web Apps: Should any developer decide to, they may create a web application making use of Qortal as authentication. Any application that requires authentication for users to accomplish actions within the app could utilize Qortal for said authentication. Just as the applications that make use of other blockchains do, they may make use of Qortal in a similar fashion. The application could be built without the need for registration, storage, and verification by centralized means.

qortal_status_updates.txt · Last modified: 2022/01/13 17:22 by gfactor