Here is an unofficial ‘grey paper’ of sorts by Crowetic and G factor laying out specifics about QORTAL and where the project currently resides. As this is a fully decentralized project, this is simply the perspective from two of its cofounders. Nothing is dogma with this project, all is currently discussed on the project Discord channel which can be found here.
Today is a MOMENTUS DAY for Qortal!
Today we have LTC in the Trade Portal and a BRAND NEW completely unregulated and completely decentralized market with LTC!
on top of that, as you can see below – THREE local wallets are now supported in the Qortal UI… BTC, LTC, and QORT!
We have removed BTC from the Trade Portal and replaced it with LTC at the moment, we will re-enable the BTC market in a future update.
This is a MASSIVE update for Qortal, and will finally bring us a truly liquid, cross-chain market with LTC!
Along with the Trade Portal update, is PRESENCE transactions – These transactions allow only online sells to be listed on the Trade Portal – preventing 90%+ of the needs for a refund to take place, if the seller places an order then shuts their node down. PRESENCE transactions take place every 30 minutes, from every sell on the Trade Portal. Any seller that has NOT responded to the last round of PRESENCE transactions, will not show up on the Trade Portal sell list.
This means that any trade live on the portal, should be able to complete, and not need a refund… but even if a refund IS necessary, the LTC chain should refund within 1 hour (as opposed to 7 days on BTC market prior.)
Here’s to the future of Qortal!
go to https://qortal.org – download the 1.4.0 core and UI, and check out the new additions!
Update to Qortal has been pushed.
Core Version 1.3.9
The Qortal Core will auto-update if you are sync’d and do not have auto-updates disabled in your settings.json.
- Qortal core version 1.3.9 is a preparation and small bugfix release meant to prepare the network for the next version that will have LTC and PRESENCE support in the LTC Trade Portal.
- Every node should automatically update unless they have auto-updates disabled.
UI Version 1.3.2
The Qortal UI will auto-update for Windows users.
- The Qortal UI in this release has the BTC Trade Portal Disabled, and a ‘cancel all’ feature for users to cancel all existing BTC trading ATs on the chain.
- Please CANCEL ALL orders on the BTC Trade Portal in preparation for the switch in the next version to LTC in the Trade Portal. Thank you!
Mac and Linux users will need to download the UI update installer and run it. Download links below.
Linux (debian/ubuntu) – https://github.com/Qortal/qortal-ui/releases/download/v1.3.2/qortal-ui_1.3.2_amd64.deb
Please Update and remove all orders from the existing Trade Portal to prepare for the switch to LTC in the next release (very soon!)
New – LTC and ‘PRESENCE’
Right now, on the testnet of Qortal, and Litecoin… we are testing the newest additions to the Qortal Blockchain Platform…
The new additions are Litecoin (full, local wallet and addition to the Trade Portal, with Litecoin) and PRESENCE (our term for the new tx type that verifies a user who listed a sell, has an online node with tradebot, to execute the multiple stages in each cross-chain trade.)
Litecoin provides a much FASTER blockchain, with 2.5 min block times. This will allow a cross-chain trade to complete in around 7 min on the Trade Portal in the Qortal UI. Litecoin also provides a cheap network in comparison to Bitcoin, wherein trades will cost a tiny fraction of what they did on the BTC network. This will allow trades of small amounts of QORT, to also make sense.
As you can see in the above picture, BTC will still be supported in the wallet of Qortal, so that people can still use their BTC which they had in their wallet from previous releases.
PRESENCE – This addition will provide a method for the UI to display a red dot next to sell orders that have an offline seller tied to them.
The way PRESENCE works, is every 30 minutes, the person who placed a sell’s tradebot, will send a PRESENCE transaction to the network. The UI will check for these transactions for each AT on the sell list, and list the last reply of the seller’s bot.
Any seller who didn’t reply in the last PRESENCE tx, will show up with a red DOT (see picture below) denoting the fact that their PRESENCE tx was not submitted last round, and it is possible that the user’s bot is offline.
The availability for the community to HELP US TEST this on the LTC and Qortal testnet, will be provided later today in both the Qortal Discord, and here on this post. (The post will be updated with download links for a completely pre-configured testnet node, and a pre-built testnet-ready UI that can be run with yarn.
Help us test on the LTC and QORT testnet now!
We have now running integrations of the newest features to Qortal (LTC and ‘PRESENCE’ tx) on both the LTC and Qortal Testnets.
Since Qortal is a Community developed and run project, ANY USER may assist the devs in TESTING the newest features BEFORE THEY GO LIVE on the mainnet!
Here are TWO pre-configured downloads for the testnet
Download both of the above zip archives.
To start the core – from terminal – ./start-testnet.sh
This will start the Qortal Core Testnet API on localhost:62391
To start the UI (with node.js installed) from terminal type – node server.js
This will start a UI server running on http://localhost:12388
Access in your browser, and HELP US TEST!
Discord room #ltc-trade-testing is there for discussion of the testing, and anything you may want to bring to the team’s attention.
It seems that lately there has been some ‘confusion’ in regard to what Qortal HAS NOW and what CAN BE DONE with it.
Therefore, this blog post has become a necessity.
In this post, I will explain the use cases for The Qortal Network in its CURRENT STATE, and what can be accomplished with the already existing core functionality.
– Qortal 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.) I.E. ‘login’ (which technically isn’t correct, as there is nothing actually being ‘logged in’ to in Qortal… when ‘log in’ is clicked in Qortal, all the user is doing is proving they have the rights necessary to carry out the creation and authorization of transactions on The Qortal Network.)
The Authorization system in Qortal requires NO centralized database, and sends NO private information that could be utilized to gain authorization over an account 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 utilized on most every service on the internet.
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 username/password for each individual provider (like we have with the Internet currently.)
– Future options (applications and UI plugins)
The options below could be built now to be utilized on the 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 period of 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 an ‘app store’ available. (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, etc.
– 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. If done, the application could be built without the need for registration, storage, and verification by centralized means.
I will post more posts like these with more that can be done with the current Qortal network as time goes on.