Anoma DOS: Privacy Everywhere
Nothing is loaded from YouTube until you press play, and then without tracking cookies.
About this video
One of the current limitations in many intent-based systems is the absence of native privacy at the protocol layer. The Anoma DOS introduces privacy primitives that can extend intent-based architectures across chains.
NEAR is the unified commerce layer for assets and agents.
Website: near.org NEAR AI: near.ai Intents: near.org/intents Chain Abstraction: proximity.dev Sharding: nearone.org
For the devs GitHub: github.com/near Dev Docs: docs.near.org Devhub: devhub.near.page @NEARDevHub
Connect with socials Twitter: / nearprotocol Blog: near.org/blog Medium: / nearprotocol #NEAR #nearprotocol #NEARAI
Transcript
1,923 wordsCaptions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.
- 0:10
three very brief minutes. Thank you everyone for coming. Um I'll talk about the Anomma Dawson, the Anomala decentralized operating system or distributed operating system and how it allows you to get privacy everywhere. Um and specifically it does one thing that most other systems don't do which is it gives you both data as well as function privacy i.e. the data that that you're operating on is private but also the functions that are being invoked are
- 0:35
private. Um so but maybe let's start with a sort of brief interlude of why privacy actually matters. And I think this is something that we don't spend enough time on to actually explain to normal people because we I think a lot of normal people always raise privacy as something like oh you would like to do tax avoidance for example. Um but I would actually argue that everyone in this room should spend a lot more time
- 1:00
explaining to why privacy matters. And I think we should focus roughly on especially the first and the last p point point which is privacy is really fundamentally it's about national community defense and I say community defense here because not everything is around national borders but I think this is a very important phrasing because so I live in Switzerland. I'm not originally from Switzerland, but one of
- 1:24
the like big realizations that you have to have as a small country is you will never be able to defend your financial system against like large scale nation state attacks, right? And so privacy is not actually the point that uh you're trying to hide from your own government, but more that you're trying to build a financial system that's resilient enough even if you're a small place so that you can withstand larger nation state attacks. And I like think about the
- 1:49
easiest way to get Ethereum banned tomorrow is to essentially move all of US commerce onto public Ethereum because like at day T plus two the NSA will go this seems to be like a bad idea to like open source all our financial commerce data to North Korea right so like privacy it's not so much as like you want to hide something from your local community or your local government rather you want to build resilient communities resilient nations and this is why you need privacy.
- 2:16
The other one is fungeability of assets i.e. you don't want to allow people to discriminate against you based on certain transaction patterns essentially. This is actually why Ze and these kind of assets are quite nice because you get full trans um asset fungeibility because you can have privacy with them. And the last one is actually for everyday usage and I've done this experiment with my parents.
- 2:38
normal people will never use these systems if they can expect that the neighbors will see how much money they're making whether they've just been to the doctor. It's like and I think we should this is really the phrasing that I'd like everyone to take away from this of like this is how we should start speaking about privacy to normal people because it's a much more positive phrasing of why this matters in practice.
- 3:00
Um I'll just quickly skip over this. So what is the anoms? Um and at the very high level it's a distributed operating system. You can think of it as Windows 95. It runs wherever you would like it to run. So for example 3 days ago we deployed the store Aurora. So it runs on Aurora now.
- 3:19
So like it comes to all new assets. It also runs in arbitum optimism Ethereum pretty much wherever you can implement the operating system anoma the DOSs will run. Um and then on top of this decentralized operating system or distributed operating system, you can actually build applications. Um and again, these applications can be as private as you want them to be or as transparent as you want them to be. Um because in the end, it's just one large risk zero circuit.
- 3:45
Uh like it's a large risk recursive risk zero circuit that implements the ANOMA DOS. Um and the nice thing that it does it abstracts blockchains away into one unified interface. So rather than because like one of the big problems that I always had with sort of having many chains is that I had to keep using new applications wherever I went and with the anoms we can just have the same application and runs wherever you'd like it to run like if your local government wants to run a blockchain based system
- 4:16
like if your local government like runs the EVM on a single server we can deploy the anoms to that single server and now all the applications that also work on Ethereum or on also run on your local government instance. Um, it's kind of like the nice thing about passports and SIM cards was always that like I could buy a SIM card in Switzerland and it would still work in the US. This is kind of the same thing here where it's like applications become very portable. The
- 4:42
ANOMA distributed operating system. It's an interface, not an intermediary. And I think that's very important to understand and make the distinction. Um, it does not change the trust model. If you use the Anomma DOSs on NIA, you only trust NIA. There's no anoma chain you must interact with in order to like get access to the applications. Your trust model is fundamentally just wherever the operating system runs. You can really think of this like you pick the
- 5:07
underlying hardware that you would like to run Windows 95 on and then you can go and install Word on your local locally running version of Windows 95. Um yeah, it provides a level abstraction that's compatible with existing chain chains and VMs. It changes the state model quite a bit. Um, and it does so in order to be a ZK compatible um, and b make applications way more scalable. So, Anoma actually uses a system um, called the resource.
- 5:36
That's kind of the the bridge between the account model that we sort of know from NIA and the EVM um, and the UTXO model that we know from Bitcoin. And fundamentally, it enables a new paradigm of intentric applications. uh roughly this is the application layer stack um that you can think of here. So you have underlying hardware, you have some way of all these things get connected and then you build applications on top.
- 6:02
Um yeah and so how do we get actually privacy on near here? Um, and I would preface this with privacy using ZK RA using zero knowledge proofs rather than TES, which uh I think we can have a long debate over TES versus ZK, but I'm a much bigger fan of ZK because it provides much better long-term privacy guarantees. Um, so yeah, Anoma, we deployed this to Aurora three or four days ago. So now we have the operating system on Aurora. Um, now we can start deploying applications to it. And so the first application that we're going to
- 6:34
deploy is the ANOMA is ANOMA pay. It's a specific application. It's a specific DAP um that is now capable of running on the DOSS on um and the really cool thing is it gives you fully asset agnostic privacy uh for any sort of transfers.
- 6:48
It's so you have viewing keys, you have discovery keys. Um you can take any asset that exists on and use um a normal pay here in order to like transfer this around privately. So where are the next steps sort of like where are we going from here? And maybe I can actually speak a little bit more about how this practically works is that you um so when you deposit funds into a normal pay here on NIA, you can deposit some NI for example and then they appear in your Merkel tree and essentially when you
- 7:22
then want to spend them, you would create the take this resource um reveal the null file that is attached to this resource and then generate output resources. For example, I could then send part of my resource to you. So for example, if I started with 10 near, I'd send like five to you and then I'd return five as the sort of as a change output to myself. If you're coming from Bitcoin land or like the U2XO model,
- 7:44
this is very familiar to you. uh we've done some interesting things to make the application very nice to use because it also includes a thing called a discovery key which I think most people underestimate actually the importance of because once you have private state the question how you build user interfaces actually becomes very challenging because well no one really has the data and really in order to figure out whether for example you have some money
- 8:09
on a system you have to decrypt every single system in the re every single resource in the system in order to figure out which resources belong belong to you. What we do with our norm though is that there is a discovery key that you upload to any indexing service. That discovery key will only allow you the indexing service to figure out which resources belong to you but not able to decrypt the resources. So as a result
- 8:32
then the indexing service can just stream encrypted resources to you and you locally decrypt this. Um, I thought this was a very neat hack because or not hack but like a very neat feature because it allows you to actually build very good user interfaces which has historically been an incredibly big challenge given these private systems.
- 8:50
Um, so what's the next steps though? So now we have private transfer simply working. Um, and the nice thing is like it's very easy to scale this out. Um like if you want to now run a localized system in your home country or your home county wherever you are you can just take exactly the same stack. The user interface doesn't change. Um it's the same interface but now you change your
- 9:14
trust model. But from here we can even go further. We can do fully private trading because we have near intents now right. And so you can use an OM pay to drive the crosschain intents as well as the crosschain trades so that um you just get fully private trading out of the box pretty much probably in the next three or four weeks. And I think everyone currently keeps talking about sort of
- 9:38
this super app thesis on like oh everything is going to be the single big crypto application. And really fundamentally I think this is sort of the first step towards it because I think for any technology here to get sort of large scale traction it's going to require privacy and privacy is very difficult to put in as sort of an afterthought. It it it's essentially impossible to put in as an afterthought.
- 10:01
Um yeah this was the very brief introduction to the normal distributed operating system um and how it brings privacy everywhere. If you'd like to learn more, you can connect with me and us over here. And you can also come to me afterwards. Thank you very much.