Architecture
Let's dive deep into Desights Protocol architecture
Last updated
Was this helpful?
Let's dive deep into Desights Protocol architecture
Last updated
Was this helpful?
Before we begin discussing about how the architecture will evolve to accomodate our vision, let's first discuss state of current architecture
The architecture above show interactions between various components of Desights Protocol. Lets expand a bit more on this .
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.
User Profile at the core is a managed by a 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 and can be considered Users and are represented onchain by their User Profiles.
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 within a . All created by this Team shares the same Ownership Structure as defined within Team Profile. Team Profile establishes the aspect of Desights Protocol.
Registry component is better explained
Challenge is better explained
Assets are better explained
