Standards and Schemas
There is a new Hedera Improvement Proposal (HIP) that has been proposed as of Friday July 13th, that I think deserves some discussion. This HIP has been written and championed by a good friend of mine and Developer Advocate Justin Atwell at Swirlds Labs.
The title of this new HIP is HIP-994: New Native Schema Registry Service. As the name implies, it proposes a new native service on Hedera, taking place alongside other native services such as the Hedera Consensus Service (HCS) and the Hedera Token Service (HTS).
Justin first introduced this idea to me in May at the Consensus 2024 conference this year, though he’s been working on it for a while.
The Schema Registry Service proposed in HIP-994 addresses a crucial need in the enterprise world, while also offering significant benefits to the broader Hedera ecosystem. At its core, this service leverages Hedera's unique capabilities to provide a secure, transparent, and efficient way to manage and share data structures across various applications and industries.
What are Schemas, and Why Do They Matter?
For those unfamiliar with the concept, schemas are essentially blueprints or templates that define the structure and format of data. They're like the rules of a language, ensuring that everyone speaks and understands the same dialect when it comes to data. In the business world, schemas are used extensively to standardize data across different systems, making it easier to share, validate, and process information.
Currently, many companies maintain their own schema registries internally or rely on centralized services. However, this approach can lead to inconsistencies, lack of transparency, and difficulties in cross-organization collaboration. The proposed Schema Registry Service on Hedera aims to address these challenges by providing a decentralized, immutable, and easily accessible platform for schema management.
The Hedera Schema Registry Service would serve as a single source of truth for structured data. Companies would be able to leverage it for data discoverability, auditability and other benefits that are laid out in the HIP. For a DLT that focuses on catering to enterprise needs, this hits a critical pain point for many of their clientele, a sign of Hedera’s continued focus on this key part of their strategy.
Why Should Hedera Retail Users Care?
You might be thinking, "This sounds great for big enterprises, but what does it mean for me as a retail user?" Well, the truth is, we're already using schemas in the Hedera ecosystem, perhaps without you even realizing it.
Remember HIP-412? That's the standard that defines the metadata structure for NFTs on Hedera. I had the privilege of authoring this HIP and worked on it along with our vibrant community back in 2021. Every NFT you interact with on Hedera follows this schema, ensuring consistency and interoperability across different marketplaces and applications.
The proposed Schema Registry Service would take this a step further. It would provide a formal, on-chain home for schemas like HIP-412, making them easier to adopt, extend, and utilize. This could lead to more sophisticated NFTs, improved interoperability between dApps, and new innovative use cases we haven't even thought of yet.
Moreover, standardized schemas could pave the way for more complex decentralized applications. Imagine decentralized social networks where data portability is a breeze, or DeFi protocols that can easily share and validate complex financial instruments across different platforms.
The Bigger Picture
The Schema Registry Service is just one example of how Swirlds Labs is leveraging insights from enterprise clients to build infrastructure that benefits the entire Hedera ecosystem. While these developments might be driven by enterprise needs, they often trickle down to create new opportunities for retail users and developers.
For instance, standardized schemas could make it easier for developers to create interoperable dApps, potentially leading to a more vibrant and diverse ecosystem of applications for retail users. It could also simplify the process of bringing real-world assets onto the blockchain, opening up new investment opportunities.
A Personal Note
As someone deeply interested in standardized data and processes, I'm excited about the potential of this Schema Registry Service. My team at HashPack is already brainstorming ways we could leverage this to enhance our wallet's functionality and improve the user experience.
Could we use it to provide more detailed and standardized information about tokens and NFTs? Could it help us create more sophisticated features for managing digital assets? The possibilities are intriguing, and we're just scratching the surface.
In conclusion, while HIP-994 might seem technical at first glance, it has the potential to significantly impact how we interact with data on Hedera. It's a testament to how enterprise-focused developments can create ripple effects that benefit the entire ecosystem. As always, I encourage everyone in our community to read the HIP, share your thoughts, and get involved in shaping the future of Hedera.
What are your thoughts on this proposed service? How do you think it could benefit you as a user or developer in the Hedera ecosystem? Let's continue this discussion in the comments below!
May Chan
CEO and Co-Founder, HashPack
Where is the insurance industry on Hedera. They are the most obvious use case for proof of insurance, etc.