If you want to add peer IP addresses, there are 3 ways:

1. add them via the GUI by:
File menu,
Settings menu entry,
Known Peers tab,
type in the IP address in the entry box to the right of Add new address:,
click Add button,
click Apply button

2. add them to knownpeers entry in peers.json:

3. add them to knownpeers entry in settings.json:

If you are running Qora on Windows then you should find your peers.json and settings.json files in %APPDATA%\Qora\
One easy way of getting to this folder is to just open the Run dialog (Windows Key + R) and type %appdata% in the “Open” box, and click OK.
After that, navigate to the Qora folder.

If you download the latest release (v0.26.11) from github then it will come ready-configured with up-to-date peers list.

I'm pretty sure I followed up with this but just in case anyone doesn't know:

Poloniex got back to me on 11th Sept with this:


So if you've have a pending withdrawal ticket before the 11th, or you withdrew but the funds 'disappeared', then it might be a good idea to open a fresh ticket with Polo to withdraw your Qora to your wallet.
Don't forget to use the latest release v0.26.11 instead of the old v0.26.0 (or worse) as there have been tons of bugs fixed since then.

If anyone does open a fresh withdrawal ticket, please report back with success or otherwise.

In other news, on Friday we had a Qora v2 node synced up to date with blocks fed from a v0.26.11 node. The main hurdle to this milestone was the [re]implementation of CIYAM AT library.
The previous CIYAM AT code was too tightly integrated with Qora and MapDB to re-use. The new library is built to be coin-independent so can be imported into other coins, which allows more atomic cross-chain transfers (ACCT).

BTC-Qora ACCTs have been demonstrated but we still need a user-friendly way of building them, maybe a website, maybe a Qora2 plug-in.

v0.26.11 is out with fixes/improvements to do with peers and synchronization, shutdown issues, MapDB issues, hanging...

https://github.com/Qoracoin/Qora/releases

Work continues on v2, coin-independent CIYAM AT for Qora DEX, new UI...

My initial awareness came from a user on the official Discord channel who said their latest withdrawal arrived in their wallet, but more definitive information is on the block explorer where you can see Poloniex's Qora account making new transactions and forging blocks.

Previously Poloniex's last transaction was 9th April:
http://node2.qora.org:9090/index/blockexplorer.html?tx=2bYmw35XQfPu6kcVq9kEphbto3uTprwzrdYSti6yPq3eHqUAJcpCCy5arAMUC3M9hMA8Q39zCt2atxFaFHxgYg9N
but now you can see very recent transactions from Poloniex's account:
http://node2.qora.org:9090/index/blockexplorer.html?addr=QPVknSmwDryB98Hh8xB7E6U75dGFYwNkJ4 (link takes a while to load as Poloniex have a lot of transactions!)

Good news: looks like Poloniex have fixed their wallet as some Qora holders are reporting successful withdrawals!
Poloniex also seem to be forging blocks and so contributing to keeping the Qora network going.
There's no information on whether they will relist Qora though.

Work is progressing on Qora v2, which has been rewritten from scratch. Right now it's complete enough to be tested with blocks fed from v1 to ensure compliance/backward compatibility.
Some aspects of Qora v2 are blocked waiting for 3rd-parties, e.g. we need BouncyCastle (a security library) devs to implement TLS v1.3 with the corresponding Ed25519/X25519 support for Qora's new networking layer.
New UI still needs a little bit more work before showtime.
Other new features are also being built and of course the "lack of exchanges" issue is being addressed.
I don't want to hype features that aren't complete but when they are I'm sure you'll all hear about it a lot!

Several database-related issues have been found and fixed. Current Qora is stuck with old v1 MapDB due to missing functionality in MapDB v2/3 and the [sole] maintainer of MapDB doesn't back-port fixes to v1 MapDB. Most of these issues are thread-related, like interrupt issues, dangling references for locks, etc. and so mitigations have been written into Qora. Some of the MapDB v3 "fixes" have been manually back-ported into a Qora-unique version of MapDB. Some v1 MapDB issues won't ever get fixed though, like rare race-conditions to do with BTrees.

Hence why Qora v2 uses a different, mature, SQL-based engine with an abstraction layer between that library and the core code making is far easier to replace in the future if similar issues develop.

In relation to Poloniex, I did contact them offering advice, suggestions and my availability for fixing withdrawals. Their last response to me was "I will pass this along to a member of my team and they will reach out if they are interested."

If your client doesn't find any connections after 5 minutes then it should download the peers list from the internet.
You should see a line like this in your logs:

Or if the client tried but something went wrong (e.g. you have firewall issues):


Some peer IP addresses that might help you:

192.34.108.212
148.163.20.188
92.222.182.121

You can add these by going to "File" menu, selecting "Settings" menu entry then "Known Peers" tab.
Type in the IP address into the box to the right of "Add new address:" then click "Add" button.
Finally click "Apply" button below then restart Qora client.

Poloniex responded to my support ticket saying they have passed my message on to the relevant team so hopefully withdrawal issues will be resolved soon.
Will update here with any future developments!

65% would put you at around block 299,000 which is way before the troublesome block 445844.

If you're still having trouble, join the Qora Discord server for active help via: https://discord.gg/rx9UUk

I've just now created a new support ticket with Poloniex regarding withdrawals, reaching out to them with an offer of assistance in resolving the issues people are having receiving their funds.
In the first instance I'm asking them for log files, latest block info, peer node info, etc. and given how long it takes Poloniex to respond, it might be a while before I can post an update here.
After that I'll need to somehow resolve the issue which will take a little longer so please be patient, even though you have all waited quite a while already!
But I will keep this thread informed as/when I have news!

According to a Qora block explorer, on a node at height 452384, Poloniex's last transaction was on 9th April 2018 at block 446780:

http://node.qora.tech:9090/index/blockexplorer.html?tx=2bYmw35XQfPu6kcVq9kEphbto3uTprwzrdYSti6yPq3eHqUAJcpCCy5arAMUC3M9hMA8Q39zCt2atxFaFHxgYg9N

I don't know which version they're using but they should really upgrade to the latest v0.26.9 which deals with recent synchronization issues.
Maybe they are sending out transactions only for them to expire as they don't make it onto the majority chain.

Newer versions of Qora synchronize way faster so they could even do a fresh install just to be sure. I hope they have a backup of their wallet seed though!
There are still people out there using v0.26.0 which does suffer from database issues/crashing that causes resynchronization...

The same seed will always produce the same addresses. If you change the seed, e.g. removing the last digit, then you'll end up with a different set of addresses.
If the seed isn't producing your original addresses then it's not the correct seed.
I'm still not sure how your 12-word phrase comes into play though.
Do you have a copy of your original wallet files? If so, might it be easier to try to guess your old wallet password instead?

I can't see any code in the history at github that ever created a word-based seed and I can't even find a word list.
Maybe these 12 words are your wallet password? If you still have a copy of your original wallet files you could try that?

12 words using BIP39, not that Bitcoin's BIP39 would apply here, would generate 512 bits/64 bytes of data but the Qora client generates 256 bit/32 byte seeds.

If you want to try converting your 12 words to base58 (via hexadecimal) you could use:
Online BIP39 mnemonic converter
then
Online hex to base58 converter

As far as I can tell, neither of the above tool make network requests to process the data, i.e. they are client-side javascript tools. You may wish to make your own assessment of this and other security concerns of pasting in what is potentially your wallet seed.

The same seed should produce the same set of addresses.
Your wallet password is only related to the encryption of your wallet dat files.

If you copy wallet files then you'll still need the same wallet password to unlock them.
If you create a new wallet using seed for recovery then you should get access to your old addresses (and set a new wallet password).

The latest release v0.26.7 should generate the same addresses as at least v0.26.0, maybe even older versions.
I prefer to use the term "wallet" to mean "the set of addresses, etc. as generated from your seed" as opposed to the software itself!
(Maybe we could call the software the "client")

I created github issue #91 for this "ClosedByInterruptException" and just released v0.26.7 which should have a fix (and also for issue #69 which is similar).

Please download v0.26.7 for great stability and let me know if all is good!

For more support, visit the official Discord channel

Enema,

It's probably best you join the Discord channel so we can help more interactively.
I'd certainly need more of your logs to get more of an idea of the context leading up the text you pasted.
It would help to know if you're running Qora on Windows (32 or 64bit?) or something else.

https://discord.gg/8reZ3

The latest release, v0.26.5, is way more stable than v0.26.1 or older releases.
You can download it from https://github.com/Qoracoin/Qora/
Work on v0.26.x is primarily about stability, bug-fixes, performance, etc. with some minor enhancements.
Fixing missing features that should already exist are likely to appear in v0.27+

The Qora client has a built-in block explorer which you can access using your browser at http://127.0.0.1:9090/index/blockexplorer.html
(Or open the client, go to the File menu then select Built-in BlockExplorer)

v0.26.4 released which should fix the JSONObject cast error pop-up that's stopping some people from starting their QORA client.

Available (as always) via github at:

https://github.com/Qoracoin/Qora/releases/tag/0.26.4

Feedback appreciated! Hopefully two more bugs squashed.

I can't find any details on any "mabowl" exploit and Google searches only throw up mentions of it being a "generic" exploit which leads me to think it's a false positive by some of the 3rd-party virus scanners used by VirusTotal.

In increasing level of paranoia/work involved:

• You can compare the MD5/SHA1/SHA256 of your downloaded ZIP with the ones at github to make sure your copy hasn't been tampered with.
• You can compile your own JAR from the sources downloaded directly from github(*)
• You can look through the sources at github for code that resembles "mabowl"

(*) If you have Eclipse IDE installed then you can follow the instructions at http://docs.qora.org/#import-source-code-to-eclipse

Lots of programs that contain networking/downloading code trigger false positives.

Hope this helps!