First of all, thank you for all of your messages. They are really documented and very interesting. We will give further details below:
Here are the main results of our simulations. We will try to keep it clear and easy for everyone. Please feel free to ask for further details. The idea here is to test three approaches: ZK-Snarks, recursive-ZK-Snakrs (linearisation), and WPI.
As a benchmark, we used a simple DAG. We then simulated transactions/nodes and calculated the time needed.
https://image.noelshack.com/fichiers/2018/03/6/1516471445-finalresultsazulik.jpgOn the left, you can see that (among the three approaches) one allows to have transaction time really close to the simple DAG (without privacy). We can confirm these results with the figure on the right where we plotted the difference against the benchmark.
So, here we are, we have selected the Privacy protocol we will apply. We still have some analysis to do, but we are very confident with this approach.
Azulik will be the first Freemium cryptocurrency.
Youll be able to realise instant, fee-less transactions, and adding privacy will only requiere a very small fee. Read below because what we have to show you is amazing.
First, we need to understand the issue, Raiblocks uses DPOS (delegated proof of stake), hence having complete privacy would hide users balances and break the whole DPOS system. The idea is to have two wallets: one public and one private.
So, you are wondering: If I have the choice, I could put all my Azulik in the private wallet and the DPOS wouldnt work anymore .
Yes, you are right and thats why we need an intencive to make people stay in the public wallet and participate in the DPOS. All the fees collected through private transactions will be sent back to the user depending on their Azulik balance.
It means that keeping your Azulik in your public wallet, even if you dont do transactions, will return you a percentage of the daily fees spent on the private network. One percent of the transaction fees will be split between the nodes, hence you will get paid to run the node. The other 99% will be redistributed to the network. Assuming that the portfolio weight is distributed like a Gaussian law and that the number of transactions is equal or higher to the number of users, we can say that, on average, youll get 99% of your fees back.
So even if the fee is very low (and probably dynamic depending on the number of nodes on the network), youll get back a lot of the fees you pay for you private transactions. Remember, its still free and instant to send or receive Azulik with your public wallet.
https://image.noelshack.com/fichiers/2018/03/7/1516527377-azulikproject.jpgThe main upside is that we will have a natural anti-spam protocol for private transactions, hence we can remove the POW to sending or receiving. It also means that it will make transactions even faster so they can be used in the mobile wallet.
Lets take an example: You reveive your salary in your public wallet, then you send a part of your salary to your private wallet that you call Shopping Wallet.
Usually with Raiblocks, when you pay for a coffee, the bar can check your balance, where the money came from, and so on. Here, you can use you private wallet to pay and nothing will appear. Your transaction will be shown on the public wallet, but there is no link between the public and private wallet so its impossible to know who owns any given public wallet.
We believe this is the most elegant way to apply privacy on a DAG DPOS protocol
Do not hesitate to ask all the questions or concerns you may have, we would be happy to provide further details.
To summarise:
- We have designed and tested our privacy protocol
- Azulik will be more decentralized than Raiblocks
- It will be as fast as raiblocks for both private and public transactions
- Engage loyal users with daily rewards
- Very small fee for private transactions
- On average: private transactions are almost free
What next:
Here, you have everything you need to understand Azulik. We know you want a proper whitepaper and to see some code.
We can say that we will be able to deliver a proper whitepaper in about a month. Regarding the code, we will have to find a secure way to show you. As you know, there are other projects aiming to do the same thing and, in months, they proposed/delivered nothing new besides "We will merge Zk-Snarks and Raiblocks. We like open source projects but we don't want our hard work to be stolen. So, in a bit of time, I think we will have a clearer picture about these two other projects and we will be able to deliver code. However, on our side, we will start implementing Azulik. To be honest, we can't expect the first test to be done before two or three months.
