Comprehensive Guide on Certified NFT/Asset Management/RWA (Real World Assets) #5496
Description
[DOC] Request for Comprehensive Guide on Certified NFT/Asset Management/RWA (Real World Assets)
Problem Statement:
The current Hyperledger Iroha V2 documentation, while extensive on data models and CLI commands, lacks a concrete, step-by-step, workflow-oriented guide for managing Non-Fungible Tokens (NFTs) and Real-World Assets (RWAs) as certified digital assets.
This gap makes it challenging for non-developers and new users to understand the practical application of Iroha's asset functionalities for complex RWA tokenization scenarios.
Specifically, there is a need for guidance on:
- Defining asset types for unique, certified RWAs.
- Minting RWA NFTs with rich metadata (including external links, hashes, financial parameters).
- Managing asset ownership transfers.
- Tracking financial components like commissions and royalties (including internal splits).
- Integrating with external proofs of authenticity and public blockchain activities (e.g., Tezos, Arweave).
Proposed Solution/Contribution:
We have drafted a conceptual guide, based on our real-world application of Iroha V2 for certified NFTs and broader RWA management. We just finished an intensive stress test with the Iroha Compose update (bug fix on 7th July 2025).
Following draft aims to fill the identified documentation gap by providing a practical, workflow-based approach using the Iroha CLI and illustrating robust metadata structures.
Our Draft Guide here @ Github :
Link to our 1st NFT Guide
Context of Our Use Case:
We are using Iroha V2 as a core internal asset management ledger for high-value certified NFTs and other Real World Assets (e.g., advertising capacities, loans, pre-production values, art NFTs and more). Our approach includes external elements like Tezos Blockchain (minting for public NFT presence), objkt.com (marketplace), and Arweave/ARDrive (decentralized storage for immutable proof documents), with our Iroha chain serving as the authoritative internal record of certified ownership and financial flows.
Call to Action/Discussion:
We are keen to engage with the Iroha V2 development team and community to:
- Validate the correctness and best practices outlined in our conceptual guide.
- Discuss potential official integration of such a guide into the main Iroha documentation.
- Identify any required changes or optimizations for a robust and scalable solution.
We believe an official guide covering such scenarios would significantly lower the barrier to entry for enterprises looking to leverage Iroha V2 for sophisticated RWA tokenization.
The DiCl Team