At Dusk people realized they needed to have a two-layer architecture. This was because of world problems. People who were trying to combine blockchain with finance kept running into issues. They had to make sure the system was private so that important information was safe but open enough for regulators to check.When they tried to make everything work together it made these problems even worse. If they tried to make the system faster more reliable or better, at keeping things private it would affect the network in unexpected ways. The blockchain system was not working smoothly.
Every time they tried something with the blockchain system they had to watch it very closely and take things one step at a time.The early development of this thing was really tough. It was full of uncertainty. We had to try a lot of things to get it right. We had to balance the privacy features with what we had to do to comply with the rules.They also had to make sure that we kept things secret when we needed to but be open when that was necessary. The conversations about this were really hard. We had to have them over and over again. We had to trust that the basic plan was good and that we could make changes without messing it up. We made progress slowly. We learned a lot from the times we failed as well as the times we succeeded. The development of this thing was, about privacy features and performance improvements and security and compliance expectations and innovation and stability and confidentiality and transparency.
The new design has two layers.The first layer is like the base of the system. It makes sure everyone agrees that data is available and that things get settled. This layer is steady and predictable it does not change much. The second layer is on top. It handles private transactions showing some information to certain people and following rules. This lets the system be flexible, without causing problems. The two layers work together like parts of a body: they work together. Are separate and each one does its own job without hurting the whole system. The two layers, the layer and the execution layer work well together like this.For institutions it is really important to have rules. When things are separated into parts it is easier to see what can go wrong. Auditors can understand how private information is protected. Developers can safely. Improve the way things are done.
When different systems need to work especially for things like artificial intelligence or dealing with real world assets it becomes easier to manage because the connections, between them are clear and straightforward. The system does not remove all uncertainty it just makes it easier to see and understand what might happen with institutions and their systems, institutions. Institutions need to be able to see what is going on.
The signs that people were using the system were not very obvious. They were always there. The test programs kept going even when people were watching them closely. When the system was connected to things it made sure everything was correct even if it took a little longer. The people who built the system did not have to spend much time fixing things to make sure they followed the rules. In the workflows that use Artificial Intelligence, where the results need to be kept secret and in the RWA applications, where people need to be responsible for what they do the system worked well with what people needed to do every day. People started using the system without making a deal, about it because it was reliable and trustworthy.
There is still uncertainty about this. Other companies are looking into ideas for privacy that can be added to in pieces and some of them can make changes faster or have more things that work together. When you have systems with layers it can be hard to get them to work together and you have to trust that each layer will do its job. Even if you build bridges between systems very carefully they can still be a big risk. Dusks plan does not guarantee that people will start using it. It gives us a framework, for privacy that makes sense is easy to defend and can withstand problems. Dusks architecture is a starting point because Dusks design is easy to understand and Dusks system is resilient.@Dusk #Dusk $DUSK
