# Open Alias #### The Basics The Monero Core Team released a standard called OpenAlias which permits much more human-readable addresses and "squares" the Zooko's triangle. OpenAlias can be used for any cryptocurrency and is already implemented in Haven, Bitcoin (in latest Electrum versions) and HyperStake. OpenAlias seeks to provide a way to simplify aliasing amidst a rapidly shifting technology climate. Users are trying to cross the bridge to private and cryptographically secure infrastructure and systems, but many of them have just barely started remembering the email addresses of their friends and family. As part of the ongoing development of the Haven cryptocurrency project, we asked ourselves: how can we simplify payments for users unfamiliar with cryptocurrency? Haven stealth addresses are at least 95 characters long - memorizing them is not an option, and asking someone to send a payment to is only going to lead to confusion. At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified domain name). By combining this with DNS-related technologies we have created an aliasing standard that is extensible for developers, intuitive and familiar for users, and can interoperate with both centralized and decentralized domain systems. A standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. or donate.gethaven.org. More information can be found on the [OpenAlias page](https://app.gitbook.com/the-haven-project/) or on the [OpenAlias website](https://openalias.org) --- # Agent Instructions: 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: ``` GET https://wiki.havenprotocol.org/overview/open-alias.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.