# Architecture

Before we begin discussing about how the architecture will evolve to accomodate our vision, let's first discuss state of current architecture

## Current Dapp Architecture

<figure><img src="https://3393572756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfhcwA8wPqFtnIiTJD6II%2Fuploads%2Fqxc8lUCwgVXapOm5fDM3%2FCurrent-architecture.png?alt=media&#x26;token=97712cb1-cc96-4daf-93b4-b4f803f5bca4" alt="" width="375"><figcaption><p>Current Architecture of Desights (LIVE)</p></figcaption></figure>

## Upcoming Protocol Architecture

<figure><img src="https://3393572756-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfhcwA8wPqFtnIiTJD6II%2Fuploads%2F5aqAV4chlkxNdFwWoKAD%2Fprotocol-architecture.png?alt=media&#x26;token=6adce8f8-5f25-4d3b-b6c4-f8180564077c" alt=""><figcaption><p>New Protocol Architecture</p></figcaption></figure>

The architecture above show interactions between various components of Desights Protocol. Lets expand a bit more on this .

### **User Profile**&#x20;

Any individual (human or bot) operating within Desights Protocol needs to have an Account. Each Account has a Profile that contains human readable metadata of that account. Collectively we call this account + profile metadata as Profile.&#x20;

User Profile at the core is a [Universal Profile](https://docs.lukso.tech/standards/universal-profile/introduction) managed by a [Key Manager](https://docs.lukso.tech/standards/universal-profile/lsp6-key-manager) that manages usage permissions. You can think of User Profile as the onchain digital twin or any human or bot. All assets created and co-owned by the user are managed by  this User Profile. Within Desights Protocol, both [Solvers](https://docs.desights.ai/core-components/solvers) and [Funders](https://docs.desights.ai/core-components/funders) can be considered Users and are represented onchain by their User Profiles.\ <br>

### Team Profile

Just like User Profile, there is Team Profile. Key difference between User Profile and Team Profile is, Team Profile is co-owned and managed by multiple User Profiles. Although the underlying structure remains same, Team Profiles are much more powerful. They allow multiple owners and manages their [Ownership structure](https://docs.desights.ai/core-components/ownership-split) within a [Team](https://docs.desights.ai/core-components/teams). All [Assets](https://docs.desights.ai/core-components/asset) created by this Team shares the same Ownership Structure as defined within Team Profile. Team Profile establishes the [Collaborative](https://docs.desights.ai/concepts/collaborate) aspect of Desights Protocol.&#x20;

### Registry

Registry component is better explained [here](https://docs.desights.ai/core-components/registry)

### Challenge

Challenge is better explained [here](https://docs.desights.ai/core-components/challenge)

### Asset

Assets are better explained [here](https://docs.desights.ai/core-components/asset)