To our donators,

A member asked us in PM about the fund withdrawal.
We have been deeply shocked to see that the funds are not in our donation wallet anymore.
All the donations were sent to our cold wallets. These paper wallets were only stored in an encrypted USB key and we backup our seeds in an encrypted .rar file. We sent this file to our-self through email.
The USB key being still with us, we tried to connect to our email account and the following message appeared:

https://image.ibb.co/nRx3oS/hackproof.jpg

Our private keys have been stolen from our email account.
It seems unbelievable that we stored such sensible information online, but this email address doesn't exist for other people. We used it to create our account here and store our seeds backup, nothing else.  No-one should know about this email address.
Few days after someone on the forum asked us if we reply to email sent to this address, we realized that it was actually made public. However we didn't realized at the moment that it could lead to the hack of our email account and we just hide our email address on our profile.

We feel so bad, destroyed, we will do our best to sent back all donations with our own funds and funds of the coin ICO, however it will take time for some of you.


Regarding Azulik's future, we need to have a break from the project and step back as we feel really ashamed toward our donators. We know the best way to restore confidence is to continue the work on the project but we currently lost the willingness to work on it. We don't feel strong enough at the moment to support all the pressure and fight against the scam accusation. We will finish the work on this project, not immediately. At the moment we won't enjoy working on it.  Furthermore we will have to change the name, and redo many things to make a clean start. After that,  we will launch a proper ICO distribution and we will have the opportunity to gift our current donators with free coin, once everything is ready and hopefully forget this nightmare.

We don't ask you to believe us and we understand your doubts, we would feel the same, we will do everything we can to fix it.

The code release date has been announced already.

We will reply to your PM, sorry about that we get so many everyday.

The timeline is indeed optimistic and just a draft for the mockup of the website, the next point is the 16th of march. Then we will adapt the timeline if needed.
We confirm we moved a portion of the donation from the nano wallet, it has been discussed directly with the donator who prefer to remain anonymous.

Dear community be ready for the website very soon,
thank you for your trust and support.

Can you give us more details about the two coins, why do you think it would be better ? Do not hesitate to tell us which point isn't clear.




No we don't please send us private message.

A very interesting question - thank you for bringing it to our attention.

Firstly, to understand it better we must delve into all that is represented by the Delegate Proof of Stake (DPOS). Simply put it is a protocol where all the users (owning coin) delegate their vote to a representative. The vote is then weighted by the balance of the wallet. In the end the representatives, which act like the minors to maintain the network, will validate the transaction whereas at least 51% of the network must validate a transaction for it to proceed. The 51% is determined using the entire portfolio of wallet balances.
Hence having a private wallet means that the balance will not  be displayed. The DPOS will therefore not function. To bypass this issue we have develloped a public wallet and an alias private wallet. The public wallet delegates his voting rights to a representative as the balance is public. Take into consideration we now have a public and a private wallet.

Let’s say there are no fees. It’s clear all users would prefer to enjoy the privacy feature and in turn keep their coin shares in the private wallet- yet this would lead to the issue of running the DPOS off track as the representative would no longer  be legitimate as they would represent a very small part of the network. Therefore the fees in place are an incentive to make people keep their coin in their public wallet and run node.

Furthermore, 1% of the fees will be used to remunerate the nodes, and 99% of the fees will be paid back to the network depending of their number of shares in coin. Hence, in average, if the number of transactions are higher than the number of user, each user will get back 99% of the fees paid. The 1% remaining will allow a more decentralized network for both public and private transactions. On top of that, public transactions remain free of charge, and the fee for private transactions will be very very low.

I would be more than happy to clarify your query for you. In the interim, you are more than welcome to browse online to dig deeper into all that high frequency trading encompasses. Telecommunication is a key part of the HFT as milliseconds, which in retrospect translates to millions. Therefore, within this technology, fibers and microwaves are used to transfer information. Some companies are specialising solely in building infrastructures- which essentially consists of telecommunication- as a means to beat their competitor and do trades faster than anyone else. Call it as you will, but indeed it is still within the realm of telecommunication. With regards to the PHD inquiry, please check online yourself for further information, but in laments terms, the cause of big  data and machine learning clearly implies data analysis.

The protocol is explained at high level in the front page, we are done with the research part, and we are currently working on the implementation itself, we haven't faced any particular difficulty as of now, it's on going and we do our best to be on time.
The number 666 is basically 5 times the Nano supply, yes it may be unpleasant for some people, but we are sure it's less obvious if we say the supply will be: 666,241,445 Azulik.
We will do our best to have the testnet ready asap, our main work is currently on the code as we want everything to be working on our side to share it with you by the 16th of march. It's a very short deadline, and we do our best, we work almost every evening and every weekends on it.

Yes we confirm,
as the decision to not cash out our dev wallet till we need it for the marketing (...)  is our decision we don't want to impact the donators.
Hence we will value max of the price between the donation date and the day we cash out, hence what you said is correct.

It's a good question we should make it clear it will be max(X,Y).

Exactly our thought, in another hand we have to think about the distribution. How to distribute many coins through faucet ? It's not easy, if we find an optimal way to distribute hence we will increase the supply.

Yes that's it, 5 times the nano supply.

You are right, it's actually ongoing, we are working on the logo.

It's not currently planned as XRB is free to transfer as well, however if there is demand we will set it.

Edit: added on the front page: rUSG7uEQ9A4PpWd3TvqWwvEiNjvD18QRpR

thanks to our community, so impressed by this first version of the website mock-up:

https://image.ibb.co/gJoyWS/AZL_mockup_v1.png

Indeed it's a good point, DPOS and privacy are two things which seem to be not compatible. Howerver we proposed this protocol that we are currently implementing :


https://image.noelshack.com/fichiers/2018/03/7/1516527377-azulikproject.jpg

it allows to have two layers a full anonymous coin, as well as a DPOS.


Yes indeed, the Zk-snarks is a well known process, stable and easier to use and implement given the low difference with WPI we decided to use the linearisation.

You are right indeed, it's just that the image is well know from our community as it's on the front page:


We should have provided more details, thank you for asking.

As you can see on the image below we actually didn't chose the WIP approach, we used a recursive-ZK-Snakrs  which is basically a linearisation of the ZK-Snakrs  making it much faster, however it require more computation power but our simulations and testes revealed that it's actually widely feasible.
 
https://image.noelshack.com/fichiers/2018/03/6/1516471445-finalresultsazulik.jpg


For the hash used, we will stay with Blake2, after reading JP Aumasson books it would convince everyone that it's currently one of the most efficient hash function. For Azulik the hash algorithm isn't used for proof of work and the hash chosen doesn't really bring upside whereas using hash based signature XMSS  would bring complexity and probably instability. (To be honest we aren't very familiar with XMSS).

Our point is that what Manta and Stone say they will do isn't feasible.

Their way to see things is too simple, and i have never seen one of them address the DPOS with privacy issue, nor being challenged with their approach. Feel free to ask as many technical questions as you want for Azulik, we are very comfortable with our protocol.

The list of donators is updated.
We should very soon have a website, thanks to all of you, what a great community.