Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Proposal for Standardizing Universal Location Format (ULF) #52

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

asiniscalchi
Copy link

@asiniscalchi asiniscalchi commented Jan 30, 2024

This Pull Request introduces a comprehensive proposal for the implementation and standardization of the Universal Location Format (ULF). The ULF aims to facilitate seamless interoperability and efficient asset referencing across various blockchain ecosystems, including Ethereum, Polkadot, Kusama, and others. The proposed format is designed to provide a uniform, unambiguous method for decentralized applications (dApps) to identify and interact with assets, significantly enhancing the current asset management processes.
This proposal outlines the structure of the ULF, examples of its usage, security considerations, and the potential impact and benefits it brings to the blockchain community. The initial discussions and the conceptual basis of this proposal were formulated in the GitHub issue freeverseio/laos/issues/177. We invite the community to review, discuss, and contribute to refining and adopting this standard for a more interconnected and efficient future in blockchain interoperability.

@asiniscalchi asiniscalchi changed the title Proposal for Standardizing Universal Location Format (ULF) Across Blockchains RFC: Proposal for Standardizing Universal Location Format (ULF) Across Blockchains Jan 30, 2024
@asiniscalchi asiniscalchi changed the title RFC: Proposal for Standardizing Universal Location Format (ULF) Across Blockchains RFC: Proposal for Standardizing Universal Location Format (ULF) Jan 30, 2024
@pandres95
Copy link

This is so much needed. 🙌

The current need for multiple relative locations for identifying certain entities (for example pluralities, especially when converted to AccountIds) is confusing and bad for developers and end users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants