> For the complete documentation index, see [llms.txt](https://docs.demodyfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.demodyfi.com/project-overview/technical-architecture/unified-account-experience.md).
# Unified Account Experience
One of the primary advantages of building and focussing on Polkadot is to consolidate its unique parachain based architecture to achieve interoperability with different protocols, both public and permissioned chain, which opens up potential sources of liquidity to Demodyfi. It potentially allows separate and isolated blockchains to be networked together, creating an “internet of blockchains”, where private chains can be firewalled from public chains like Ethereum, but still be able to communicate with each other via pre-defined state-transition and functions, similar to the internet handshake protocols used today to establish networking.
The first step is to begin implementing on Polkadot and achieving interoperability with other compatible parachains.
## **Unified Account Experience**
Moonbeam’s focus is to create a fully Ethereum-compatible environment on Polkadot with the best user experience possible. With Unified Accounts, a user will only need a single H160 address, with its corresponding private key, to do everything we mentioned above including both EVM and Substrate functions. Consequently, the user does not need to move balances between 2 different accounts and is able to access all the features with a single account and private key. Demodyfi is making this possible for the end-user by implementing efficient cross-chain swapping between wallets like Metamask and Polkadot.js
## Import an H160 Account
Let’s see how we can import our already existing MetaMask account to Polkadot JS Apps. First, navigate to the accounts section, and click in the add account button.
**Non-custodial service**\
Demodyfi is a decentralized, non-custodial protocol; assets are controlled by the users themselves and not stored on the platform. We empower the user to keep storage of their own private keys and cryptocurrency assets, while the team is working in the backend, optimizing yield for the users without compromising security
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.demodyfi.com/project-overview/technical-architecture/unified-account-experience.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.