Realmente parece um projeto com caracteristicas de projeto morto, não aparecem noticias e a comunidade é praticamente inexistente :/
Aos que procuram uma boa moeda descentralizada brasileira, recomendo que pesquisem sobre o Criptoreal.
É um projeto sensacional desenvolvido por brasileiros que visa destruir os intermediários(famosos middlemen) como bancos e operadoras de credit card em favor dos usuarios e comerciantes,que estão sempre pagando taxas absurdas e sempre sendo prejudicados..

Eu acredito que esse tokem EReal já era morreu, onde está os devs e projetos do tokem? Não valeu apena segurar essa moeda, sem projetos e sem comércio ,  alguém pode responder se ainda está em desenvolvimento o EReal?

Why not use the Zerocoin protocol?

Why not use the Zerocoin protocol?

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

Currently we haven't really dig the distribution process, it's not the top priority as of today. We have to define the supply, the part given to the contributors, the team and through faucet.

It should look like that:

Nada contra a língua inglesa, mas aqui é fórum Local Português, evitem postar em outra língua, pois a moderação pode advertí-los.

abs

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.jpg

On 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.
You’ll 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 wouldn’t work anymore .

Yes, you are right and that’s 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 don’t 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, you’ll 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), you’ll get back a lot of the fees you pay for you private transactions. Remember, it’s  still free and instant to send or receive Azulik with your public wallet.



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


The 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.

Let’s 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 it’s 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.

https://a.radikal.ru/a41/1801/5b/12da6f81b645.jpg

I want to present you a new revolutionary technology located at the junction of Iot and AI. It's just a concept, but I'm already actively working on it.
The essence of it is that you would monetize the efforts and the time when you spend every day sitting in the toilet.Everyone to whom have the toilet bowl at home, can hold a master node.
And in the same place to be engaged in the mining of this promising currency.Each time you press the flush button, the results of your tight calculations will immediately be sent to the blockchain.
It should also be noted that the currency is absolutely private, even until you open the door.If you still have questions, you can find answers to them in white paper that is already in your toilet.
You, of course, are interested in how you can join this amazing project. It's very simple - send a little ETH or BTC to the address below and within a day you will find at your home a little piece of shit.
All received funds will be directed to the development of a special synchronizer, which will synchronize your toilet bowl with a blockchain.
Well, the data recorded in the blockchain will be analyzed by an artificial intelligence to find out who is the coolest shitass.
I want to note that we are already billions, but this is not the limit, in a number of countries, people still use a hole in the floor.But as our project develops, they will install a toilet bowl and connect to our network.
So the prospects for this project are grandiose!

ETH - 0xEb298C02f8E1f95B12dba57d0e84996504cE7888
BTC - 15CLzKxg36zaA5NNz5kL4wEsyn2vGHqKDA

To be honest i wonder if a good captcha can be solved automatically, i have seen this video about XRB, but the weakness was the unlimited number of try. I'm not sure a bot could solve a capcha at the first time, especially if it's a dynamic one (Once with image, once song, once number) for each fail you wait 1 hour.

However i have to say i really like the approach you propose. It's a very good idea.

What is AZULIK ?

Azulik aims to be Raiblocks with privacy.
We may make some changes to the Raiblocks protocol, but in the end, we want to offer a decentralised, fee-less, anonymous, and instant cryptocurrency.

At this stage we confirm that Colin's words were right, it's not possible to apply privacy to XRB as we kown it today ( zkSNARKs).

Adding the privacy feature is harder than it may look, simply applying a ZK-SNARKs protocol (the underlying protocol of Zcash) would make the transaction time increase a lot.

That why we are currently working on two approaches:

• Having an optional privacy feature, allowing to have instant transaction or privacy
    
• WPI (witness-indistinguishable proof ) or recursive zkSNARKs approach which for us would be the best way to have both instant transaction and privacy

See below and our whitepaper for details.

Who are we ?

We are two colleagues, two engineers working at a famous tech company. One of our friends in the company will join us in the near future to work on the project management, marketing, and exchange listings.

Here’s a little bit about us:

There is nothing really sexy about it. We are rather young guys who graduated from very good universities. The skinny one is better at C++ than he is with girls and the fat one doesn't remember the last time he played a sport.

You won't know more about us than that, though, because our company's compliance rules don't allow outside of business activities. Hence, we wouldn't take the risk of being fired.

We have been in the blockchain and crypto world for years. We followed the development of XRB and we have been fascinated with Colin's work. Especially this epic thread that none of us understand…Don't worry, we are joking!

Why Azulik ?

We like Colin, he is certainly super smart, but we have read somewhere (and they were reported words) that adding privacy to Raiblocks wasn't possible.

When we saw that, we thought: “Challenge accepted!”

We started to work on it. We dug a bit into the problem and we would like to offer a potential solution we found.

Yes, we aim to build a decentralized, fee-less, and instant cryptocurrency.

But, most of all, we believe that privacy is an amazing touch to add to it.

Give us more details !

In a nutshell we show that applying Zero Knowledge proof (ZK-SNARKs) to DAG is something feasible. At this stage we believe that the privacy feature and instant transaction aren't compatible, however we think about making private transaction an option allowing to handle instant transaction or full privacy. But for sure it's a more complex problem than just apply SNARKs to Raiblocks, our next direction is to check the feasability to apply witness-indistinguishable proof.

(wikipedia)

We believe that applying WIP to Raiblocks could be the solution to have both instant and fee-less transaction. Furthermore given to Witness-Indistinguishability Against Quantum Adversaries it would also be possible to make Azulik quantum resistant, which is currently not our priority.

For more details check our whitepaper first draft by clicking here. We know it's still very light as we have been mainly working on the privacy feature for the moment but expect updates frequently.


Here’s what’s next:

• Finishing a proper whitepaper
• Discussing other potential solutions or improvements with you guys
• In the meantime, working on the coding
• Sharing advancements with you on Github
• Working a bit on the marketing (website, logo, etc.)
• A functional wallet

Distribution:

It's very early to speak about the distribution as we expect months of work ahead, especially because we are busy with our daily work at the office, but we would like to find a very fun, fair, and new way to distribute Azulik. Any ideas?


Can i help ?

Of course you can, we are always interested in people having expertise and wanting to share, do not hesitate to contact us and give us your toughs, concerns, comments or complaints. If you have no expertise in this field hence you can motivate us if you are as excited by the project as we are.  

Donation:

If you guys are excited, liked the small piece of work we offer you today, and want to see more, or if you can't wait for the release of Azulik and you want us to reveal our identity and leave our job to work full-time on it, do not hesitate to donate.

We will update the list (or tell us for remaining anonymous), all donation will be very appreciated and we will remember it when we finally release Azulik! (and we secretly expect to leave our job and work full time on Azulik as it's much more interesting) .

• Bitcoin: 1E6HaTHMwdWsQEPHyMoiNHyxTjKzAXC8sU
• Litecoin: LQcsBj8e9jHHdFyG6cZLCzPpzC5ydnJQKj
• Ethereum: 0x21D0241bf0aB261D52c10767c89Bc9F764472167
• Monero: 44MyZttQH891CTTA8Gg71Cdh68zfUs28WGGynFzcpePiLuE2weVenAVRGfFzjzcusKe2qYUYCGqXk31 mNjG3QqkLKMdm7UU
• Raiblocks: xrb_1dtmp1g9rfkusja6ogpktazgt846kj4ett6afwowpu8xz6wq8kimergzkrug

Thanks for reading.

Azulik Project

Why RaiBlocks is not secure.

In this article I will try to explain why RaiBlocks is not secure and why its technology is any better neither comparable than the Bitcoin technology.

1. Decentralized payments
Decentralized payment networks are, in opposite of centralized payment network like banks, a way to secure your money without having the risk that a central authority could steal your money or manipulate the money in the market. Decentralized payment networks use asymmetric cryptography to ensure that you are the only one who can spend your money.
When you create a cryptocurrency wallet you are given a public key and a private key. The public key allows other people to send you money, while the private key allows you to spend them. 

But how other users know how many money do you have?
To accomplish this, every user of a decentralized payment network must download the entire transaction database which is replicated on the entire network. When you send a payment over the network, it is received by all the users connected on the network allowing them to know your updated wallet balance and allowing them to discard that payment if you don’t own enough funds.

2. Double Spending
The main problem that afflicts decentralized payment networks is double spending: the ability of an user to spend his money multiple times. In the real world, when you pay someone you give him the real cash. In a centralized payment network, like VISA, the central database is updated every time you make a payment, and they will not allow you to spend more money than your balance.
In a decentralized payment network what happens if you send the same amount of money on two users of the network in the same time? Since their database takes time to update for a small amount of time they both will receive the payment and accept it. In a later moment, when the network tells them that you double spent your money, they will cancel the payment, this is possible because every payment is broadcasted to the entire network, not only the receiver.
Without any other security layer, if a malicious user double spends his money and succeeds to block a payment receiver to know that he sent the same money to someone else (or even better, to another wallet of his own), the payment receiver will accept the payment and ship the good. This is so bad, since even a network connection problem could temporarily lead a payment receiver to undetect double spendings.

3. The Bitcoin Solution
To solve this problem, Bitcoin relays on the fact that after you receive a payment you need to wait a confirmation block, the confirmation block tells you that the payment you have received has been accepted by the entire network and you are allowed to spend it. To create a confirmation block, the miners create a list of all the pending unconfirmed transactions and solve a very difficult mathematical puzzle. The miner who solves the puzzle first, sends the block he found with all the list of confirmed transaction and the solved puzzle to the network, the users of the network will check if the puzzle solution is valid and then reward him with some free coins plus the sum of all the payment fees of each transaction in the block. The miners must create a valid list of payments to be accepted by the network, so double spend attempts are just discarded.

In Bitcoin an attacker,  to make a succesful double spending, should not just stop you from receiving a double spend attempt message, but he should also solve the puzzle to create a confirmation block in a reasonable time frame. Currently solving that puzzle with a single computer would take years; at writing time to solve that puzzle a network of thousands dedicated hardware is used, an attacker would require a billionaire investment to replicate that network. Moreover, it would not only need to create one confirmation block but six of them (6 confirmation blocks are required in the Bitcoin network to trust a payment).

Critics of Bitcoin say that all the computation power used to make the Bitcoin network secure is just a waste of energy because there are other reliable and better technologies. Is that true?

4. What is RaiBlocks?
RaiBlocks is a crypto currency that advertises itself as a fast, fee-less and secure currency, unlikely Bitcoin which is currently slow and high-fee (usually requires 1 hour to a full payment confirmation).
But the key point is that Bitcoin has been made that way to guarantee his users a certain amount of security to prevent double spendings.
 
RaiBlocks completely ignores the Bitcoin technology and relies on a special version of the Proof Of Stake concept.
When you receive a payment in the RaiBlocks network you have to wait a certain amount of time to be sure that a double spending has not been attempted (and remember the first problem, if an attacker stops you from receiving the double spend you would never know!)
When a double spent is detected, the RaiBlocks network starts a vote. Every peer connected to the network vote to accept the payment A or payment B; every user vote is weighted with the amount of his balance. Usually each peer votes for the first transaction he receives. The transaction which the sum of votes reaches the 51% of online amount of currency wins. The winning transaction is accepted by the network and the other one is discarded. (Reference https://github.com/clemahieu/RaiBlocks/wiki/Double-spending-and-confirmation)

The payment receiver, if his network has not been compromised, will then know if he can trust the payment or not, and will ship the good accordingly. This system leads to an unsolvable problem.

5. The Man in the Middle attack.

If an attacker succeeds to put himself between a merchant and the RaiBlocks network he can just filter the double spending payment packets, and the merchant will never know that he is receiving a double spending. The Raiblocks network will discard that payment while the merchant will accept it.

https://s18.postimg.org/7pnm6yweh/doublespend.png

6. Solutions proposed by the RaiBlocks team

a) The merchant should ask a vote for each payment he receives and wait for the confirmation.
The problem is that the attacker could manipulate the vote by telling the merchant that only his peers are connected to the network thus he will win the vote by filtering only his votes. Plus, asking a vote for each payment would cause a huge increment of bandwidth usage that many peers could not handle.

b) The merchant should have a remote node verifying the payment.
The attacker could just attack that network too.

c) The merchant should ask the RaiBlocks.net website if the payment has been accepted.
The attacker can hack the RaiBlocks.net website. Also if you have to rely on a website you can no longer consider RaiBlocks a decentralized network.

Other solutions

1) A payment to be accepted should require a vote with a minimum weight quorum.
It's difficult to establish a correct quorum, and if that quorum is offline no payments will be processed.

2) A payment need to be accepted by some trusted representatives.
This will stop the network on being decentralized. Also, if those representatives are offline the payments are not processed.

7. Why Bitcoin is not vulnerable to this type of attack
Simply because an attacker, to be trusted by a merchant, would require to solve a very difficult puzzle for six times. An attacker cannot alter the difficulty of that puzzle.

8. Other observations

a) RaiBlocks is just Bitcoins without the Bitcoin securing algorithm. The creator of Bitcoin, Satoshi Nakamoto, describes the double spending problem in the original Bitcoin paper: https://Bitcoin.org/Bitcoin.pdf. The developer of RaiBlocks just thinks to solve the problem by ignoring the problem.

b) The official representatives of the RaiBlocks network own more than 52% of total voting weight, allowing the developer to manipulate every vote on his will.
Source: https://dev.RaiBlocks.net/page/representatives.php


9. References
https://RaiBlocks.net/media/RaiBlocks_Whitepaper__English.pdf
https://github.com/clemahieu/RaiBlocks/wiki/Double-spending-and-confirmation