Linked Wearables Redesign

by 0x87956abc4078a0cc3b89b419928b857b8af826ed (Nacho)

Linked Pre-Proposal

Should we restructure the Linked Wearables Category?

Summary

Proposed is an enhanced architecture and design for LinkedWearables to address client performance issues caused by low-performing API Resolvers and a simplification process for new third parties, from inception to maintenance of collections

Abstract

After initially considering shutting down Linked Wearables due to performance drawbacks, it has become evident that the functionality is highly valued by the community and has a significant potential for expansion and adoption. However, the current model also presents bureaucratic challenges and can be cumbersome for content creators.

Motivation

To foster greater adoption and streamline the cost and maintenance of LinkedWearables, it is necessary to implement a new process and architecture capable of adapting to the demand while preventing any potential performance issues for the client. This new model can also help improve the user experience when managing LinkedWearables in-world.

Specification

We propose the following changes to the current Linked Wearables implementation:

• Remove the ThirdParties API dependency:
  • Enhance the URN already used for third-party wearables to provide enough information about the NFT item with a Linked Wearable associated.
  • Validate NFT Ownerships on-chain using a RPC Provider and the corresponding Smart Contracts.
  • Creating a new UI on top of the builder to manage Linked Wearable Collections
  • Fetching all Linked Wearables for the backpack using a new service that will feed from the builder.
• Allow third parties to “Pay” directly to the DAO rather than going through a 4M MANA threshold voting process.
• Create a migration plan for existing thirdparties.

Conclusion

Removing third-party APIs and implementing changes to the URN will ensure all NFT item ownership validation occurs on-chain, enhancing reliability. This model simplifies the onboarding process for new third parties by eliminating API development and maintenance costs. On the other hand, it establishes a mechanism to boost adoption among third parties and facilitates more efficient wearables management within the client interface.

This proposal is summarized due to technical limitations. To view it complete and vote on it, visit the DCL DAO Governance dApp