Relationships
Relationships is a new RWA standard that solves the legislation challenges that are not being solved by current standards which neither are reliable protocol on-chain.
About
The problem it solves Rugs made by the owners by 'impossible to detect' practices for standard users who invests a every day and no direct relation on chain between token and the RWA, Jhon Smith should believe in the resolving and metadata content. User Interaction and Data Flow VAULT OF REAL ESTATE NEW YORK, 0x... VAULT OF JHON SMITH INVESTOR, 0x.... Name: 64 Central Park W Name: 64 Central Park W Description: Central Park Building Deeds ------> Description: Central Park Building Deeds Deeds File: ipfs://.... Deeds File: ipfs://.... Hash: 0x.... Hash: 0x..... ON-CHAIN UNIQUE RELATIONSHIPS VAULT1, 0x... VAULT2, 0x... RWA1,hash1,metadata1 RWA4,hash4,metadata4 RWA2,hash2,metadata2 RWA4,hash5,metadata5 RWA3,hash3,metadata3 RWA4,hash6,metadata6 The project architecture and development process Solidity standard to create this tokenization protocol, different from NFTs but compatible by adapters (to enhance them) that has a: 1. Handshake to communicate with other CA that are part of the standard. 2. Locking to avoid spam or non-desired pushs. 3. Usess more than mappings to create relations, not resolvers. 4. A hash that corelates to the RWA on-chain. 5. A transfer function that burns and mints the token in the remote smart contract that gives real ownership to the current owner. Product Integrations This is a native solution that will become an EIP proposal called Relationships Protocol. We use NEXTJS/REACT for the dApp and Solidity for the code, U2U as the first EVM compatible deployment. Key differentiators and uniqueness of the project This simple solution really solves every aspect of the RWA legislation challenges that are not being solved by a standard and neither a reliable protocol on-chain. Trade-offs and shortcuts while building We had to deal with a lot of problems trying to implement extra librearies from partners so we decided to keep it as simplest as possible, the result is great. We have 3 versiones, so we made challenges solving, PoCs and funcitonal dApp at the end. This to avoid getting out because of PoC not resolved problems in our dev side. Additional Features We plan to add a lot of future functonallities and UX recommendations for a world wide adoption.