If I had to venture a guess, I'd say it was because it was there. Base58 is what Qora addresses are encoded in and the address creation system borrowed heavily from the Bitcoin address creation algo.
Why implement another base conversion mechanism when you already have one in your codebase, and other developers would also have in their codebase if they wrote their own client?
Right  Good point!  So I've got a question for you since you're here, rlh. I'd like to create several applications based on Arbitrary Transaction, so I need to reserve a range of Service ID numbers, let's say 1 thru 5. I don't think it's possible but I'm just checking - is there any way for me to restrict others from using my Service ID for their own personal use? For instance, I want Service Port 1 for Qora Messaging, I don't want others to use it for other purpose. Can I restrict it somehow? (Maybe I just make an announcement?) PS: Before you leave, I wish to share my secret idea with you.. I'll post it here, please don't leave yet! I think the only way to achieve that is within the posted data |
|
|
|
We have three important milestones ahead : - Full source code is going to be released
- Automated Transactions will go live on Qora
- Atomic Cross Chain Transfer will occur
I don't know the exact time of the above or even the exact order (except the fact that ACCT will perform after the release of the AT), so, due to that we cannot have at the moment a proper roadmap.But this will be seized on time. Beyond these milestones, there are also other things that needed to be arranged. I suggest that we should start looking at the documentation which is actually missing. We do have the below : Qora FAQQora AssetsQora API V13I think we could start discussing and collaborating on the documentation i.e. what we need to have, what can be easily done etc. and start working on this. Of course Wiki is missing but content is also missing and I believe is preferred to have the content ready for the Wiki and not the Wiki ready for the content. We can use PiratePad for example to start collaborating on documentation. Also, about the documentation, my opinion is to use (i.e. for the API and Tutorials) Markdown and especially MkDocs to convert text to HTML.Then the whole documentation can be hosted on Github and users can contribute to the documentation by making pull requests.This will achieve a better presentation of the whole documentation.Besides that, Github can be used to serve a Wiki as well. As for the future development of Qora, I do believe that we should get focused more on the front end and kept the core as it is, from the moment that the forthcoming upgrades take's place.My thought is to keep the existing wallet as it is and deliver also to the public an alternative HTML based wallet that will be fully compatible with the API and will serve Qora in a more flexible front end.As I don't have further information on the existing wallet and I don't know how feasible is to serve HTML content from within (I guess that it is) that's why I had made that thought, to proceed with an alternate wallet. Another thing that I would like to mention at the moment is about the governance and how open source communities govern themselves. This is really crucial so I would like to drill it down to the basics by sharing with you the below useful links Governance ModelsEssential Tools For Running A Community-Led ProjectIf you don't have the time to read the above then please read this short article that describes The Eclipse Model. Then, as a community, I believe that we need to establish something like the below.  But in order to have this established we do need activity from the members. Of course there are other things that are needed to be discussed and established as well, like marketing activities, business development etc, but let's first set our first goals. |
|
|
|
I just want to throw this out there but... Should we consider a rebranding? Almost as of this were a new coin? I don't know if I'm on board but since this is the next stage of Qora's evolution and since the pool of followers is rather small, a rebranding could provide an image that things have changed and that the coin has turned a new leaf.
Thoughts?
I had thought of that the truth is but I have concluded that as we are approaching the wallet version 20 with AT live we can say that we have arrived Qora 2.0.Keeping the name, introducing crypto 2.0 I guess this is all about marketing after all. |
|
|
|
did Qora explain the absense and if he is continuing with this project?
If he explained or not the reason of his absence to me I would not share it as this is something personal. Regarding the project, he continues with the full release of the source code. So first, let's wait for that and then we will see. If he decided to leave with the full source code delivery, I guess he is free to leave. If he decided to stay then he might stay around somehow. So, either he stays or leaves, there are still many things that are needed to be done. As he said... |
|
|
|
Too Happy!!!!! You really made my day!
BTW, who is going to handle the next Wallet release?
AT Team or Qora dev himself?
AT team will proceed as normally with the integration of AT, create a new wallet version, test it first on a testnet and then release it. If in the meanwhile, full source code get released, AT team will probably revised their integration to fit to the latest code and Qora will decide if he is going to compile a new wallet version at that specific moment. If the source code released after the wallet provided by AT team, then again, it will be merged. Sorry, but I'm confused about this statement. A little clarification is needed. I thought we were voting on a fork of Qora (created by AT team). Does that mean it's not going to happen? Or are you implying there will be two versions of Qora wallet? One developed by AT team and one from Qora himself? Sorry, just confused about what the situation is... Let's say it with an example The one scenario is...On Monday AT team releases the wallet version made by them, then, on Friday Qora releases the full source code.Changes will be merged and a new wallet version will be released again. The other scenario is....Qora releases the full source code on Monday and AT team hasn't finished their integration.Then AT team will revise their integration to fit to the latest source code.At that time Qora decides if he is going to compile a new wallet version or not. |
|
|
|
Too Happy!!!!! You really made my day!
BTW, who is going to handle the next Wallet release?
AT Team or Qora dev himself?
AT team will proceed as normally with the integration of AT, create a new wallet version, test it first on a testnet and then release it. If in the meanwhile, full source code get released, AT team will probably revised their integration to fit to the latest code and Qora will decide if he is going to compile a new wallet version at that specific moment. If the source code released after the wallet provided by AT team, then again, it will be merged. |
|
|
|
Does that mean Qora has contacted you...
Yes ...and has agreed to release GUI source and open up the native libraries??? The complete and latest source code will be released. |
|
|
|
|
Let's break the silence.
We will finally go full open source
|
|
|
|
BTW, in case you haven't been following our conversation -- the V18 Qora Client is totally stable on a 64-bit system (64-bit JVM) but will most likely crash on a 32-bit system due to a database issue. It's not a bug, it's just that some codes need to be restructured/refactored so the file stream doesn't close unexpectedly while the application is still expected to do additional I/O. We're waiting for someone to dig into the code and provide a workaround for it, but in the mean time, Qora is 64-bit only.  I have tested the wallet in a low end virtual machine (32 bit Linux), loaded 100 addresses and the wallet haven't faced any issues except the time that it was needed to load which was around 5 minutes. |
|
|
|
Seem like you got everything out you could  Thanks for the info! I am not able to read and understand the POS from the source code. If anyone is capable enough it would be great to have a review. |
|
|
|
I'd like to know about the mechanics / incentives structures of the Qora POS. Any documentation about it?
A Proof-of-Stake algorithm that is different from anything that is described here https://en.bitcoin.it/wiki/Proof_of_Stake. The algorithm will allow accounts to start generating blocks after only 10 confirmations. Each account will also know at exactly which point they will generate the next block. That is a little little Is there not more information? Below are quoted all that I have found from the dev about POS Also a short review from a core dev of NXT Qora is used on the Forging Simulation Tool created for the Consensus research. |
|
|
|
mmapFileEnable() - Enables Memory Mapped Files, much faster storage option. However on 32bit JVM this mode could corrupt your DB thanks to 4GB memory addressing limit.You genius! I think you actually solved the mystery! Very good job, DeMap! PS: I've been running Qora on 64-bit windows (64-bit JVM), and I can attest that my Qora client never once encountered any problem (No exception thrown)... I'm pretty sure it's a JVM problem. ---------------- PS 2: If this is the case, what Poloniex needs to do is to compile a new Qora wallet with memory map file always enabled, and switch to 64-bit JVM. I think someone needs to contact Poloniex or Tristen and let them know about the solution. Indeed, this seems to be a workaround that solves this problem https://groups.google.com/d/msg/mapdb/9MBNRFbX3g4/otD5fYEQBM0JClosedChannelException happens if one of the threads is interrupted while doing IO. The FileChannel gets closed on interruption and all future IOs will throw CCE. There is workaround to use memory-mapped files (mmapFileEnable()), but they only work on 64bit systems.
So either enable mmap or investigate what is interrupting your threads. https://github.com/jankotek/MapDB/issues/352#issuecomment-48128816 Some threads are interrupted while reading/writing from FileChannel. As result FC is closed and always throws ClosedByInterruptException. That is documented behavior of FileChannel, and there is not much I can do without sacrificing performance.
So my suggestion is to stop interrupting threads while they are reading/writing.
Other solution is to use memory mapped files (mmapFileEnable()). Perhaps they are not affected by this https://github.com/jankotek/MapDB/issues/384#issuecomment-68485183 I would recommend to use mmap files as
alternative to prevent this.
Also make sure that no thread is being
interrupted while doing IO. That would close
FileChannel mmapFileEnable public DBMakerT mmapFileEnable()
Enables Memory Mapped Files, much faster storage option. However on 32bit JVM this mode could corrupt your DB thanks to 4GB memory addressing limit.
You may experience java.lang.OutOfMemoryError: Map failed exception on 32bit JVM, if you enable this mode. mmapFileEnableIfSupportedpublic DBMakerT mmapFileEnableIfSupported()
Enable Memory Mapped Files only if current JVM supports it (is 64bit) I have also asked MapDB founder about that and he told me to check MapDB Code for thread interrupts. Also a new version of MapDB has been released |
|
|
|
I'd like to know about the mechanics / incentives structures of the Qora POS. Any documentation about it?
A Proof-of-Stake algorithm that is different from anything that is described here https://en.bitcoin.it/wiki/Proof_of_Stake. The algorithm will allow accounts to start generating blocks after only 10 confirmations. Each account will also know at exactly which point they will generate the next block. |
|
|
|
Yes, poloniex had tested their wallet recently but still crashes.
Are they running the precompiled V18 version that Qora released or are they using a compiled version of the released source code? Are they using a 64 bit Java-VM or a 32 bit Java-VM? I have reached out poloniex to let them know that there will be a new wallet version and it might be possible to work also on their wallet issue, but I noted that there is not any guarantees that it will be fixed.Once the new wallet version is ready we will try to simulate the problem into a testnet to see if it can be re produced.Then we might work on it and try to solve it.Your questions (hopefully among others) will be passed to poloniex once we reach that level. If you can contribute to this then please do it.We've got slack that hosting our discussions, we recently launched an IRC channel and there is a skype room as well between me, vbcs and skerberus.Also here as well is a place to host those questions. |
|
|
|
According to Smart Property page on Bitcoin Wiki currently there are no implementations of the idea of Smart Contracts. I have asked the author to review Automated Transactions and update the Contracts wiki or advice otherwise. EDIT (to avoid misunderstandings): As it says on Proof of Stake ... Implementation
There are currently a few distinct proposals on how to implement PoS ...AT is a Smart Contract implementation proposal. |
|
|
|
ok thank you guys. and what about poloniex ? they have still qora deposit and withdraw problem?
Yes, poloniex had tested their wallet recently but still crashes. |
|
|
|
By the way, Vrontis, speaking of web-based wallet for Qora, I believe ASIC-8Tile had a working web wallet for Qora a long time ago. It was fully working with nice-looking interface.
Indeed, ASIC-8Tile has worked in the past on a web-based wallet  Post linkAnd here are the details about it I'll send a PM to ASIC-8Tile |
|
|
|
Speaking of GUI, I asked Qora Dev a question concerning GUI a long time ago (when we had weekly 'features' votes... One of the things was "Wallet Upgrades")... He told me GUI would eventually go OS. But looks like he forgot to OS certain things before he left.. Hi Qora Dev, I have an idea for the wallet upgrade option today. I was thinking, what if we have a custom plugins and skin/theme system for Qora wallet? So 3rd party developer can create different plugins to expand the features of Qora wallet (and artists can create custom themes). To accomplish that, I'm thinking you will probably need a scripting engine (maybe based on Lua). For instance, there is a folder called "Plugins" and another folder called "Theme" inside wallet folder. At the startup, the wallet will load all the plugins and skin/theme inside those folders. Do you think it's something that can be added to the Wallet Upgrade option in voting list?  If you don't like my idea, just ignore it. No worries. Another thing, could you tell me how much time (approximate) is needed to do wallet upgrades? I think it should take no more 1 week. Am I wrong in assuming this? Thank you! PS: You're the best! This could be done easily when the GUI is opensource. It already uses a system to change to the OS theme. About the wallet and the graphical user interface, Qora told me that he was wanted the wallet's design to follow these rules Also, about the wallet. I am working on how we will have an HTML based wallet.It will be achieved by making API calls, it will be based on node.js and the design rules that Qora preferred will be followed. So far I have managed to create a standalone cross platform application based on node.js and follows those design rules...I need to get now deep into the API to make this app an actual wallet. Last.. another leak of what Qora was planning about the wallet.  |
|
|
|
If this is achieved then AT would end up being the "standard" method to do such ACCT transfers and a marketplace could evolve in each supporting blockchain.
Wow!! Very encouraging news! It'd certainly be awesome to see AT becomes the de facto standard for ACCT transfers! Do we have a candidate already? It will be a major win for AT system if we can convince one of the two big guys (Litecoin or Dodgecoin) to incorporate AT into its core and serve as base currency in the AT system. But before that can happen, I'm sure we need to get a smaller coin onboard first (to show that we have a viable and stable working system). Happy with the direction AT is going! Glad to have you here, CIYAM! Here is a 20 BTC bounty for this! Spread it, may someone finds it interesting |
|
|
|
|
Show Posts
