🔊 Qortal Core v5.0.7 - Git Release COMPLETE 🔊

See Release Notes at link below:
https://github.com/Qortal/qortal/releases/tag/v5.0.7

🔊 ANN - please check your chain to be sure you're not still on a fork 🔊

There are still quite a few nodes that are not following the main chain.

If you are one of them, you will not be able to leverage everything on the network until you resolve this issue. You are also not minting the correct chain, therefore you are not actually gaining any QORT.

Do the following to check if you're on the correct chain. If you are not, then you should bootstrap your node.

1. Check your chain - you can use the following call to check your chain - curl localhost:12391/blocks/byheight/2424270

you can also simply click - http://localhost:12391/blocks/byheight/2424270 - that will give you the same output.

That should give you the result of -

"signature":"2apPfPJpSMRyxHDvc8JQMVKMowZsnHcZkKE2iubfpDwnxKXsCiiPHFE6FAE4WGVmQLJY3STCurLrQm4EoEQzVmM93njxmeycLYUTS2hT9cXXqhqPkDtkG8KFd4zN1ucRiHmqaD9eUhpBmx2kefKfVgT6jfpSWWTTnHFACjk6X2Nc1jR"

if your signature for block 2424270 does NOT match the above, you are on the fork, and you should bootstrap your node immediately.

There are multiple ways to bootstrap. You can either utilize the bootstrap button in Hub or Node Control app, or you can stop your node, delete your 'db' folder, and restart your node - if you have questions feel free to reach out.

Thank you.

# Qommunity-Importer v0.0.2

The Qortal Development group and explicitly crowetic, are pleased to announce the Qortal Qommunity Importer App - an app that allows EASY IMPORTING OF COMMUNITIES TO QORTAL. The Qommunity-Importer app GENERATES A ‘QOMMUNITY HUB’ APPLICATION WITH NO CODING REQUIRED for the user’s community.

It creates a BRANDED, FUNCTIONAL APP on Qortal, with a FEW CLICKS, tracks new user engagement, and allows creation of Qortal-Hub-Compatible communications threads, and a private messenger that utilizes encrypted identifiers, so that you cannot tell who is messaging whom by simply reading identifiers.

## Qommunity-Importer App:

- Takes an input communityName
- Guides the user to creating two groups (with names default {communityName}-public and {communityName}-admin.
- Takes a LOGO input by user.
- Creates a THEME based on the logo colors.
- Allows user to invite any other Qortal users (names/addresses) to their groups after creation and confirmation
- Creates a Branded App for the User
- Allows user to publish app directly, without having to download or save anything
- Gives the user the option to download either source files, or publishable zip of the app created.
- Gives user links to the app and copy link button to share, and explains they should follow the name, will add follow button in next release.

## The app it generates (Custom Branded Qommunity Hub):

- Themed and named based on the input of user on qommunity-importer
- Logo published as a group avatar and used for the app avatar
- App themed and branded for their community
- Reddit-like threads inside the app, threads are also compatible with Qortal Hub default threads. (Private Threads coming in the future, at the moment only the public group’s threads are used.)
- encrypted messenger with encrypted identifiers - really cool with encrypted identifiers so you can’t see who is messaging whom.
- Easy announcements location for the community (Hub compatibility coming soon.)
- Ability to publish links to other Qortal apps, that show up on home page.
- Community growth tracking - keeps track of NEW users based on the same checks used in the FreedomCells alpha app, only tracking ACTUALLY NEW USERS, not existing Qortal users.

## qortal://Qommunity-Importer

qortal://Qommunity-Importer

For a Demo of an app generated with Qommunity-Importer, see qortal://Qortal-HostedHardware

I'm not super stoked with the theme generated from the HostedHardware icon, so I'll likely generate again to get a different theme. You may run the Qommunity-Importer multiple times, if you wish to generate the same app again, make sure you copy/paste the groupNames of both groups, or it will create another app with different identifiers that will not be compatible with one another. The app generated will stay compatible with old identifiers if you use the same groups for both public and private groups.

Qortal Hub version 0.6.0 has been RELEASED

See release notes here for changes - https://github.com/Qortal/Qortal-Hub/releases/latest

🔊Qortal Core version 5.0.8 auto-update has been SIGNED

Network should begin updating shortly. Github release and release notes will be published soon.

🔊 MAJOR ANNOUNCEMENT - Qortal Core Version 6.0 🔊

Today, we are pushing a MAJOR VERSION of Qortal Core. Version 6.0! This represents a HUGE step forward for the project.

Version 6.0 introduces a separation of concerns on the low-level networking layer of Qortal. Making QDN data capable of MAXING OUT any connection. it also opens the doors for things like real-time data connections to be developed. (Which is something that will be worked on as soon as possible, and will be faster if we start getting the attention the project deserves, and increase in volume/value.)

There are a few things to be aware of with this release:

1. This release introduces a SECONDARY DATA PIPE which utilizes a SEPARATE PORT for QDN DATA.
- This means you will need to port-forward anoither port if you wish to have incoming connections for QDN data, and if you do not have uPnP enabled on your router.
- Port 12394 by default, becomes the QDN port (change this port with 'listenDataPort' setting in settings.json) .
- if you do not have uPnP enabled on your router, and want incoming data connections (especially important for publishers) you will need to port forward port 12394 tcp to your Qortal Node.

2. Since QDN is now able to make the most of any connection, the limiting factors on transfer speeds become the slowest of upstream or downstream between two peers.
- Meaning, if you are the first and only node with the data, your upstream is very important for the speed at which the rest of the network can obtain your files. (This has always been true, but now we can take advantage of the full connection speeds, so it may become more 'noticeable' when most things are much faster.)

3. Having followers will now dramatically increase speeds for next access to your data.
- This has always been true to a degree, but this change makes it very true, and very obvious. Data will get out MUCH faster to others if there are many good peers that have it.

If you would like to read more about this update, Ice has published a document outlining the changes, and I have re-published that document on Q-Assets' Wiki.

https://github.com/IceBurst/qortal/blob/master/v6.md

The 6.0 Auto-Update is being signed now, and should be fully signed within the next 20 minutes. Thank you!

Auto-Update has been SIGNED. Network will begin updating shortly.

Github release will be published in a moment. Qortal Hub release will also be pushed.

### ℹ️ Qortal Core 6.0 Auto-Update – Manual Action Required for SOME Nodes

Qortal Core 6.0 has just been released and rolled out via auto-update.
This is a major version upgrade, and older nodes will no longer be able to use QDN without updating.

During the auto-update process, a random and inconsistent failure affected some nodes across different operating systems. When this occurs, the node does not update successfully and will require a manual update.

You may see an error similar to:

Failed to apply update: Cannot run program ".../java": Failed to exec spawn helper

At this time, the issue appears random, not OS-specific, and not tied to any single configuration. We are actively diagnosing the root cause.

---

## 🖥 What You Need To Do if Your node did NOT update

### Linux / macOS

Run the following command exactly as shown:

cd ~/qortal && ./stop.sh && rm qortal.jar && curl -L -O https://github.com/qortal/qortal/releases/latest/download/qortal.jar && ./start.sh

This will:

- Stop Qortal
- Remove the old qortal.jar
- Download the latest 6.0 release
- Restart the node

---

### Windows

1. Download the latest qortal.jar from:
https://github.com/Qortal/qortal/releases/latest/download/qortal.jar
2. Navigate to:

   C:\Program Files\Qortal\
   

3. Find the downloaded one which will by default be in Downloads folder, copy it, and paste into C:\\Program Files\\Qortal, and OVERWRITE the qortal.jar.
4. Restart Qortal

---

## ⚠️ Important ⚠️

- Nodes that did not successfully update to 6.0 will have limited or broken QDN functionality
- If your node appears stuck on an older version, manual update is required
- This is not a consensus issue, but a client-side update failure

We appreciate everyone’s patience while we track down the underlying cause and harden the auto-update process to prevent this in the future.

If your node updated successfully, no action is needed.

\-Qortal Development Group

@everyone - A more detailed announcement will be published soon.

We want to let everyone know that we are aware of a few issues reported since the 6.0.0 release and are actively working on a patch release. Given the scale of the 6.0.0 upgrade and the fundamental networking changes involved, it is expected that some issues may only surface on MainNet, even after extensive DevNet testing.

If you are experiencing connection drops, instability, or general networking issues, we currently recommend lowering your overall peer counts.

The new networking layer works very differently than before and does not require the same number of connections. In simple terms, this is a shift from many smaller, less capable connections to fewer, significantly more capable ones. On lower-powered machines or weaker internet connections, maintaining too many of these larger connections can cause instability.

Suggested values to try:

"maxPeers": 32
"minOutboundPeers": 16

These values should be more than sufficient under the new networking model. Nodes with limited CPU, RAM, or bandwidth are the most likely to be affected and should benefit the most from reduced peer counts.

We are also testing additional changes related to the connection issues some users are experiencing, with favorable results so far.

Separately, we are aware of foreign coin–related issues, and another targeted change addressing those is about to enter testing.

We expect to have a test release available soon for users affected by these issues, followed by a patch release shortly thereafter.

Thank you for your patience and for reporting issues as we work through this transition.

- Qortal Development Group

🔊 ANN- Qortal Core Version 6.1.0 🔊-

including MAJOR improvements and HTTP2 connectivity, dramatic build time improvements for QDN, ARRR and LTC fixes, and much more!

AUTO-UPDATE transaction has been SUBMITTED and is now AWAITING ALL DEV SIGNATURES.

WILL BE APPROVED VERY SOON.

🔊 ANN - Qortal Hub Version 1.0.0 RELEASED 🔊

See release notes here - https://github.com/Qortal-Hub/releases/latest

- Hub now supports http2
- New Chat Widget
- New Home page design
- Search function in qortal://address bar
- Many more

@everyone Qortal Core version 6.1.1 patch release auto-update SIGNED

This is a simple release primarily focused on resolving issues with certificate generation on non-openjdk java versions.

Network should begin updating shortly.

🔊 Qortal-Auto-Update - version 6.1.2 - SIGNED 🔊

- This update is a VERY simple change that was causing duplication in encrypted qortalRequests.
- There as a new deduplication feature added to the core, to prevent additional qortalRequests that were identical.
- However, the feature was not robust enough, and it caused a bug with multiple DECRYPT_DATA calls back to back. Making the response to the first call duplicate the subsequent.

🔊 Qortal Core Version 6.1.3 Auto-Update has been published, and is awaiting signatures. 🔊

🔊Qortal Core version 6.1.3 AUTO-UPDATE has been SIGNED - Network will begin updating shortly. 🔊

- This version is primarily focused on performance improvements related to database queries.
- This version also prevents the issue seen a few days back regarding Q-Chat messages delaying core processing. (related to spamming, and unoptimized queries)
- Full release notes will be published with git release that will follow shortly.