Latest posts of: qora

Qora feature vote #1

It is time to vote for the next feature of Qora.
You can find the correct poll in the client with these details:
Name: qora feature vote #1
Creator: QMk21ZLpcdeAicFb4zxnJJPtcMGPAWeSoK
Please make sure the creator of the poll is correct.

This is an experiment.
If everything goes well the vote will end on Friday 4 July 6PM GMT.
Exchanges should not vote. I will ignore votes from the exchanges.

The descriptions of the options can be found here.
https://docs.google.com/document/d/1u8_Bf7NBfgsadIjIg72dJW23kabkcZC9lP10Db6_MUM/edit?usp=sharing

You can only vote for one option with one address.
The votes an address provides is calculated realtime using it's confirmed balance.
When you revote for another option your previous vote will disappear.

Tomorrow the poll for the next feature will be created.

Please check this document for the current ideas.
https://docs.google.com/document/d/1u8_Bf7NBfgsadIjIg72dJW23kabkcZC9lP10Db6_MUM/edit

Any feedback is appreciated.

Version 10 is now available.

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

MD5: 417E6618222C3E4F68BA1ED5F6E681B0
SHA-1: 7A50C149C6737BFB447A6B0C97B9286ED4E3F404

This version contains the API changes described here:
https://docs.google.com/document/d/1rqBS8-w090DbDa9ptNg0xvlRjafKEuZzx71aTFSeoUU/edit?usp=sharing

If you use the API please make sure to check if the changes don't break your application.

In addition here are the current ideas for the next feature vote:
https://docs.google.com/document/d/1u8_Bf7NBfgsadIjIg72dJW23kabkcZC9lP10Db6_MUM/edit?usp=sharing

The API changes which will be included in V10 can be found here:
https://docs.google.com/document/d/1rqBS8-w090DbDa9ptNg0xvlRjafKEuZzx71aTFSeoUU/edit

Everyone who has ideas for the vote can post them here.
I will then create a document so everyone knows what they can vote for.

Version 9 is now available.

https://mega.co.nz/#!jtIWnYSZ!2LfxcdK2aWaV9rTNH_0H2XwZ_DjwnTLBGz1QP0WLrhE
Please download the application from this post and not from a quote.

MD5: d94f783b73c80a4d24283a7eb4c64ca4
SHA-1: 009756aa1c531c0cfdcd074d55c85109df7dfc46

This version contains the voting system which will be activated on 25 June 5PM GMT.
A new ping network message has been added which will be used in the future to detect closed connections faster.
Also contains some small fixes to the database and network that you probably won't even notice.
This version does not contains the API for the voting system. This will be added in an update before the release.

Not upgrading to this version before 25 June 5PM GMT will make your client fork.

Most of the voting system has been completed.
Some GUI related stuff and the API still needs to be done.
After this is done and while we wait for the voting to be activated and for the next feature to be voted on, I will completely focus on resolving issues and small requests.

Quote from: agran on June 14, 2014, 09:10:21 PM

@qora, please take the opportunity to send coins by name.

The focus is currently on getting voting ready but what would be the best way to do this.
A name could have multiple purposes. (url, name, email, etc)
Should the value of a name follow a certain JSON structure?

Quote from: Vrontis on June 11, 2014, 09:28:43 PM

Quote from: Vrontis on June 10, 2014, 11:48:15 PM

I have figured out what was wrong with the Win 7 64bit machine.It was held the wallet into the sandbox.
I will try to see if I can dig a little deeper in that to find what exactly it has been put into the sandbox.

Thanks

The below files went into the sandbox and have blocked the sync.
run.bat
Qora.jar

I have dismissed them.

Also one question regarding the restoring addresses proceed (restore seed).Is there an option to restore only addresses with balance !=0 ?
And is there a maximum number of address per seed?

Thanks

There is no option to only recover addresses with a balance.
The amount of addresses per wallet seed is limited to 2 147 483 647 .

Quote from: QoraKnight on June 11, 2014, 09:16:39 PM

I have one question about the voting system feature.

When you said "1 Qora = 1 Vote," did you mean that if we wants to cast a vote, we need to pay 1 Qora as fee?

Or you meant that the Qora inside our wallet is seen as our votes?

For example, if I have 1 million qora in my wallet, does that mean I have 1 million votes?

How does it work? Could you elaborate?

I haven't really worked out every detail yet but this is my first idea on how to do it.
Basicly there is a poll with certain options.
You create a transaction which allows you to back a certain option with your address.
If the address has 5000 Qora you provide 5000 votes for that option.
If you send 1000 Qora to another address you will provide 4000 votes for that option after the transaction.

Voting will be included in an update at the end of this week with an additional week before you can use it so everyone has the time to update.

The next thing that will be implemented will be a voting system.
The main purpose of this system will be to decide in which order features will be implemented.
I will provide a list of possible features and the community will decide which one they want first.
The system could also be used by the community to make certain decisions.
1 Qora will equal 1 vote.

In the meantime I have been working on the database.
Once those changes are finished the client will no longer be limited by only showing the last 50 transactions/blocks in your wallet.
Instead you will be able to see everything.

Quote from: agran on June 08, 2014, 09:44:38 PM

@qora, Already a week passed since the release of 8 version. When can we expect a new version?

When some problems are actually fixed.
Might be tomorrow, might be the day after tomorrow.

Quote from: Vrontis on June 08, 2014, 08:45:31 PM

Thanks agran

Unfortunately didn't worked.
I went into a second machine, make a new instance of qoracoin wallet (with the default knownpeers) and successfully retrieved my wallet addresses with the seed i had.Now is "Oke".

The differences between those two machines are :
The one that didn't worked is Win7 x 64 bit
The one that worked is Win 7 x 32 bit

By the way the faucet coins are now appeared into one address (the address i made the request to receive them).

Is there any other things that i need to look into my 64bit machine in order to connect into a peer ?

Could you check if the TCP port 9084 is not blocked by your firewall.
Running 2 instances behind the same IP has some problems.

Quote from: smaragda on June 07, 2014, 08:46:35 PM

Do you want us to send the data files if we have sync problems even when we don't see changes in the transactions list? Undecided

Yes.
The problem seems to happen to parts of the network at the same time.

Quote from: Mrrr on June 07, 2014, 08:26:27 PM

Quote from: poncho32 on June 07, 2014, 08:01:23 PM

When the dev first distributed the coins he advised everyone not to trade until he was certain Qora was bug free. Even now he cannot be certain it's bug free. Everyone will probably blame him if he OK's trading and we get another fork incident.

Testing a completely new code base is harder than testing a shit coin whose dev copied bitcoin's source code and just changed the name of the coin. Perhaps we should stop trying to push the dev into OK'ing trading and let him decide when it's ready without pressure from us.

Yes. Better to check endlessly than to be sorry in the end. So qora take your time by all means. Meanwhile, the reason why the fork occurred in the first place wasn't because of a bug in the code. It was because we didn't have enough people staking. So unlock those wallets

There is still a bug in the code that causes synchonization problems.
This happens maybe 1 time a week now and it is hard to see what is wrong when I am not experiencing it.
This is why I am asking people who are on a fork to send me their data files.

It is safe to send payments to people you trust.
It is not safe to run an automated exchange 24/7.

Quote from: agran on June 06, 2014, 08:43:59 PM

Quote from: fsonex on June 06, 2014, 08:32:44 PM

Based on what the nodeviewer is showing, it looks like my node may be on that fork (it shows my node on block 5407). I'll send you the data files, then restart the node.

nodeviewer may show incorrect data about height.

Because one peer will be the fastest one to deliver the new block only his height gets updated.
The application only handles a message with a certain block one time and ignores the others.

Quote from: agran on June 06, 2014, 07:54:48 PM

Quote from: 91porn on June 06, 2014, 07:17:05 PM

http://coinia.net/qora/blockexplorer.php
last processed block: 5426 (2014-06-06 17:19:07 utc, 1h 57m ago)

I have some problem. Sad

I fixed it.

Anyone who was on that fork, managed to close the application and still has the data files.
Please send them to me.
It would help me a lot.

Please send me the data files of the fork if anyone has them.

I think it is better to follow the sharecoin thread until there is absolute certainty that the exchange has disappeared.
https://bitcointalk.org/index.php?topic=587051.8000
I find it strange that an exchange would disappear within 2 months.
If they indeed had the intention to scam I think they would atleast have waited a few more months for bigger profits.

Quote from: Exergy on June 03, 2014, 09:26:40 PM

How do you know if you are on a fork?

Check the blocks at debug and look at how long ago it got the last block.

I would advise people to only trade with parties they really trust.

If you are on a fork and it does not want to synchronize anymore please send me your data files before deleting them.
This helps me with finding the problems faster.