@crowetic, you are welcome!
Do you have a acess to the official twitter / facebook account from Qora?
(It would be great if you post your recent updates there, many guys are thinking qora is a dead coin... )
https://twitter.com/qoracoin
https://www.facebook.com/qoracoin
It's time to wake up the huge sleeping Qora community!
Most people don't realised anything about our futur plans for Qora!
thank you crowetic and
best wishes!
Exactly. We need to spread out the word about Qora from within any form of social media, to help increase its awareness and trading volume. To help keep us up to date, it would be best if new updates related to Qora would be announced over social networks, or even by email newsletter suscriptions.
Nevertheless, I'm looking for something huge to happen in Qora soon, to see its price reach new heights. The official release of Quoth will be a game changer here, and I bet that next year will be a bright one for the Qora platform. Just my opinion.
Don't worry. I have access to this twitter and will be putting one of my closest people on it very soon.
As for the qouth mainnet release, this has already been accomplished in prototype phases - (you can get to it with any QORA node http://127.0.0.1:9090/quothprototype or through my QORA node http://qora.host:9090/quothprototype)
As for the database and crashing issues... I've had a temporary qora.jar file compiled, and after some testing I've not had any chain db corruption issues, even upon closing incorrectly. However, I did have 1 corruption of the wallet db upon crashing the computer on purpose, but I restored the wallet by deleting the wallet folder contents, and restoring by seed. Then everything was fine.
I'm currently also testing on Linux.
If anyone else would like to test the new jar file, which is 64 BIT ONLY (this means you must install 64bit java, from oracle, on whichever system you'd like to use it on) and like I said I have had wallet corruption issues upon a full on power-down of the system, though it did NOT crash the blockchain db, and picked up right where it left off. So this is an improvement, also I was able to restore the wallet from seed very quickly. So make sure if you're going to test this version, BACKUP YOUR SEED!
you can backup your seed from your running wallet by running this command in the console...
get wallet/seed
and/or when you created your wallet, you should have backed up your seed.
------------------------------------------------------------------------------------------------------here is the new version I'm testing now with a few modifications that didn't crash the blockchain db even on forced crash of the system, hard power off...
https://cloud.crowetic.com/s/IIcNcRq03nRzEVf
you can download this with linux by .... (the following are ubuntu server commands, other OS's may vary)
(then you will have to rename the file from download to Qora.jar (capital Q) )
then you can set permissions
then run...
***please note, this is not an 'official' release of QORA, simply a modified jar file that I've been using myself, that seems to have solved the chain corruption issues in the db. It is 64 BIT ONLY compatible, thus you must download the necessary version of java from oracle...
http://www.oracle.com/technetwork/java/javase/downloads/index-jsp-138363.html
Here are ubuntu server instructions for 64 bit java installation...
login as root...
sudo -i
download java from here... http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
^^to download from multiverse copy
^^ to rename from cloud download to correct file name
sudo mv -v jre1.8.0_112 /opt/java/64
sudo update-alternatives --install "/usr/bin/java" "java" "/opt/java/64/jre1.8.0_112/bin/java" 1
sudo update-alternatives --set java /opt/java/64/jre1.8.0_112/bin/java
The new dev working on the db said he will start the work on Wednesday, and has a full week to dedicate to this, hopefully it can be fully finished in this time, I have a lot of faith in this developer, he's VERY good.
"Don't worry. I have access to this twitter and will be putting one of my closest people on it very soon."
that's good!
"very soon" is a little inaccurate