The only thing you can do is resend them.
I am not going to hardcode them into the client.
If people suffered huge losses because of this it is best to contact me.

What happened is one entity controlled more then 50% of all the generating balance in the network and created a longer fork. (unintentionally)
This fork orphaned transactions which had been confirmed for more then 24hours causing them to become invalid.
An unconfirmed transaction automaticly becomes invalid after 24 hours and gets deleted.
The only way to make sure that this does not happen again is to use your Qora to generate blocks.

If you still get forks on version 8 and it does not want to synchronize to the longest chain please pm me your data files.

It's best to keep an eye on the blockexplorer.
http://coinia.net/qora/blockexplorer.php

As you can see QPVknSmwDryB98Hh8xB7E6U75dGFYwNkJ4 is controlling the chain.
If they keep controlling it I will start forging with the shares that have not been claimed yet.

An offer option could be useful.
I should create some voting system in the client so we can see what the community wants the most.

It is hard to say when these unexpected problems keep happening.
When your application forks and does not want to synchronize anymore it is best to send me your data files to give me a better idea what goes wrong.

Version 8 is now available.

https://mega.co.nz/#!7xRGEZgS!V4oC3BxnH4NovkF1TXpoKjJj7ld58im5kHl0Pj7DmoI
Please download the application from this post and not from a quote.

MD5: 0a858afe59c8eaedc290f9b6ea51b5db
SHA-1: f71f487a974f450485f3d02a6fe66a43ec61c2a7

This version contains some fixes for the network and synchronization.
I have noticed that when the connection is unstable it can take the application up to an hour to get back to the latest block.
A ping message will be implemented in the next version to reduce this time.

Also most of the issues with the exchanges are client related.
They can't help it if their transactions get somehow orphaned and lost.

Version 7 fix is now available!

It seems version 7 has once again problems with synchronization.
I got a new version that might fix it not 100% sure.
I will investigate it more in detail tomorrow.

https://mega.co.nz/#!z5YDRJ6Y!ZZceYIVtn5J4vph21p7nxWYTaBdV-jMYyZJNi8HUdeA

If this doesn't fix it switch back to version 6.

Was the amount of confirmations on those transaction the same as the height of the last block?

Version 7 is now available.

https://mega.co.nz/#!zpI1TSTZ!2jAswTTrA107poOfvRGnsnpFC38Ink-8Cg6FTPtsdq0

Changes:
- Fixed some database corruption errors. When closing the application incorrectly it should no longer create a fork.
- You can no longer send transactions while synchronizing or while having no connections.
- You can no longer create multiple transactions by spamming the button.
- Fixed some network related errors more specificly "received message with wrong magic".
- While synchronizing blocks are now being preloaded. This speeds up synchronization.
- The application should no longer freeze when trying to close it while it is downloading the blockchain.
- When orphaning blocks the transactions will now be resend properly through the network.
- Made some changes to the calculation of the unconfirmed balance.

Normally I was going to release a new version today fixing most of the database related errors and corruption issues.

Instead I started working on making synchronization faster so the next version will be released tomorrow.

It sucks that things like that appear now and not during the beta.
If you are fast you can indeed click the send button multiple times before it shows the dialog.
All those transactions are valid btw and not double spended.

Currently I am working on the database issues which seems to be the cause of most of the problems right now.

Changed a few details like the title colors and the lists because they don't seem to center well.

It can't really harm you.
The only thing I see is that those 103.21.143.* IP's do not work properly.

It should be able to synchronize 200 blocks a second and we are still far from that point.
From a fast server it only seems to process about 10-20 blocks a second now.

Version 6 is now available.

https://mega.co.nz/#!T4hDVICC!fPGglOmk4pYQ2jAm4Pin_7dWfLd0CZdUysSa-ri9hAs

Changes:
- Some fixes to synchronization problems.
- Synchronization should be slightly faster now.
- New API commands to sign/verify messages. (Check the documentation POST addresses/sign/{address} & POST addresses/verify/{address})
- Pressing cancel while unlocking the wallet will no longer unlock the wallet when the password was correct.
- Sorting on balances will now sort correctly.

Possible but very risky when we have almost no nodes at the moment. This is only possible once there are many nodes and the currency has been more divided between users.
Using something like that this early would be a big security risk for the network.

When someone has access to your computer and you are generating blocks he can get the seeds. There is no workaround for that.
If you are generating blocks your seed needs to be available in your memory.
If you are scared that people will access your API even though only your pc can access it you can always disable it using -disablerpc.
What I can do is give you the option to disable these API calls.

Biggest issues right now are database corruption and better handling of connections.
To everyone who is running public nodes If you want me to add your node to the next release please pm me.
This would really help the network.


I hope they are processing payments manually.

For the main window I only want to show the data that is directly related to the user.

The most annoying are those that you can't really reproduce but I will check every error.


I am thinking about adding this to the client this weekend.
There will definetly be a new version this weekend with fixes.
Hopefully I will be able to solve a lot of the problems people are having.